Around was a video collaboration platform designed specifically for remote-first teamwork. Rather than treating every conversation like a formal conference-room meeting, it emphasized compact video, lightweight interaction, and the ability to keep working in other applications while remaining visually connected. Its own product description positioned the service as a reimagining of video collaboration, with a lean interface and proprietary technology intended for one-on-one conversations, team syncs, and spontaneous working sessions.
That focus matters because Around was not simply another full-screen calling tool. Conventional video platforms often make the call itself the center of attention: participants occupy a large grid, controls consume screen space, and the shared work is pushed into a secondary position. Around reversed that priority. Documents, design files, code, and other work could remain central, while participant video stayed present without dominating the desktop.
The platform was later acquired by Miro, the visual collaboration company. Around’s public FAQ described the acquisition as a step intended to help shape the future of team collaboration. That context provides the clearest answer to questions about the product’s identity: Around was built as a focused collaboration layer for distributed teams, and its ideas became relevant to a broader visual-work ecosystem after the Miro acquisition.
A Collaboration Tool, Not Just Video
Around’s recommended use case was a session with a few other participants actively working on something together. The company cited collaborative document editing, design sessions, and code reviews as representative examples. In each case, the participants need to see both the shared material and one another, but they do not need a large video window occupying half the display.
Consider a code review involving three engineers. On a conventional call, a 1920-by-1080 display may be divided among an editor, a browser, chat, and a substantial meeting window. Even if the meeting application consumes only one-quarter of the screen, that is roughly 518,000 pixels unavailable to the code and supporting materials. A compact interface reduces that visual cost and makes the video layer feel more like ambient team presence than a separate digital room.
The same logic applies to design work. Designers frequently move between a canvas, component library, comments, specifications, and messaging. A full video grid competes with all five. Around’s approach was to preserve visual contact while allowing the applications where work actually happened to retain priority. This distinction made the platform particularly well matched to working meetings, as opposed to webinars, large presentations, or calls where passive attendance was the main activity.
“The work stays central; the meeting stays present.”
That sentence summarizes the design philosophy even though it is not a technical specification. The value proposition depended less on adding another way to make a call and more on changing the spatial relationship between the call and the user’s work. For remote teams spending several hours per day in collaborative software, saving even 10 percent of usable screen space can have a noticeable cumulative effect.
Floating Mode Defined the Desktop Experience
The native Mac and Windows applications offered a capability called Floating Mode. It allowed the video interface to remain above other applications, so participants could continue seeing one another while editing a document, inspecting a design, or reviewing code. This was the most important functional difference between the installed application and the browser version.
The web app provided a lower-friction entry point for guests, but its functionality was more limited and did not include Floating Mode. Around therefore recommended the native application for people who used the platform regularly, while participants without the software could join through a room link in a supported browser. That arrangement balanced two competing goals: a richer recurring-user experience and a simple path for occasional collaborators.
On desktop systems, the published minimum requirements were macOS Mojave or later for Mac users and Windows 10 for Windows users. Browser access supported Google Chrome as well as current versions of Safari, Firefox, and Microsoft Edge. These requirements placed the product within the range of common business hardware rather than demanding specialized equipment.
Room links also reduced onboarding friction. An organizer with the desktop app could invite someone who had never installed Around, and that guest could enter through the web application. In practical terms, this eliminated a common barrier in cross-company meetings: requiring every client, contractor, or interview candidate to download software before participating. The guest might not receive the complete native experience, but the core ability to join remained available.
For someone interpreting the phrase around adalah, the most precise definition is that Around was a compact video collaboration service optimized for active remote work rather than a generic calling utility. Its defining idea was not merely video transmission; it was persistent, unobtrusive presence alongside the tools a team was already using.
The platform allowed as many as 50 participants in a meeting. That figure is substantially higher than the two-to-six-person sessions highlighted by its recommended workflows, yet it remained below the scale associated with mass events. The contrast reveals the product’s priorities. Capacity existed for a department-sized call, but the interface concept was most compelling when a small group needed to collaborate closely and maintain eye contact without surrendering its workspace to a large grid.
Mobile Access, Handoffs, and Conversation
Around also offered mobile applications for both iOS and Android. Users could start or join calls from a phone, remain connected away from a desk, and move an active session between a computer and a mobile device. The instant handoff feature was especially relevant for remote and hybrid workers whose calls might continue while they changed rooms, left a workspace, or switched devices because of battery, camera, or network considerations.
The mobile experience extended beyond passive listening. Participants could react or respond through chat messages, GIFs, and emojis, share images from a camera roll, and view high-resolution screen shares. Those features supported the platform’s broader view of collaboration as a combination of video, content, and lightweight social signals. A reaction can acknowledge a point in less than a second, whereas an audible response may interrupt the speaker or add several seconds of conversational overhead.
At team scale, small savings can accumulate. If eight people each avoid four five-second interruptions during a 30-minute session by using reactions, the meeting avoids more than two and a half minutes of fragmented speaking time. That estimate is illustrative rather than a published Around metric, but it shows why apparently minor interface choices matter. Remote collaboration quality often depends on reducing dozens of tiny coordination costs rather than solving one dramatic problem.
The platform also supported chat-based participation. This gave team members another channel for short responses, references, and informal expression without forcing every contribution into the audio stream. GIFs and emojis may appear secondary to productivity, but they can restore some of the social texture lost when coworkers no longer share a physical room. Around’s feature set treated that texture as part of collaboration rather than as an unrelated add-on.
A Slack integration further connected calls with an existing team workflow. After connecting Slack and Around, users could invoke Around from Slack using the slash command associated with the service. This reduced the number of steps between deciding to talk and opening a shared room. For an unplanned clarification, eliminating even one application search or calendar action can determine whether a team starts a quick call or spends ten minutes exchanging messages.
Recording and the Miro Context
Around’s Recording feature was presented in beta and allowed meetings to be captured for later viewing. The company described its playback experience as immersive, with the goal of helping viewers feel as though they had participated in the original session. This framing differed from treating a recording as a flat archive. It suggested that playback should preserve the conversational context and participant presence that shaped the live meeting.
Recording is particularly valuable for distributed teams operating across time zones. A 45-minute session scheduled for 10:00 a.m. in California occurs at 6:00 p.m. in London and during the night in much of Asia. A recording cannot reproduce real-time participation, but it can reduce pressure to place every employee on the same schedule. It also supports review when a design decision, technical explanation, or action item needs to be checked later.
At the same time, Around’s central proposition was synchronous collaboration rather than video storage. Its strongest differentiators were the compact interface, Floating Mode, accessible room links, device handoff, and integrations that made quick teamwork easier. Recording complemented those capabilities by extending the useful life of a session, but it did not replace the live, visually connected working experience around which the product had been designed.
The Miro acquisition is therefore a logical strategic development. Miro provides a visual workspace in which distributed teams can brainstorm, plan, diagram, and organize information. Around concentrated on maintaining human presence while people worked in digital tools. One product centered the shared canvas; the other centered lightweight communication around shared work. Even without assuming details beyond the companies’ published statements, the conceptual overlap is clear.
From an analytical perspective, Around addressed three measurable constraints of remote collaboration. First, screen area is finite, especially on laptops. Second, joining friction increases with every installation or account requirement. Third, attention is limited, and large meeting interfaces compete directly with the material being discussed. Floating video addressed the first constraint, browser-based guest access addressed the second, and the compact working-session model addressed the third.
Around can consequently be understood as an attempt to make video feel less like an event and more like infrastructure. It supported up to 50 people, ran through native desktop software or major browsers, offered iOS and Android access, enabled cross-device handoffs, integrated with Slack, and provided beta recording. Yet its identity was clearest in small collaborative sessions where participants were editing, designing, or reviewing together. The acquisition by Miro did not erase that identity; it highlighted the continuing value of bringing conversation closer to the place where teams create and decide.

