Around was a video collaboration platform designed for remote-first work. Its central idea was straightforward: make it easier for small groups to talk, work on shared materials, and stay visually connected without allowing the video interface to dominate the desktop. The service was built for practical collaboration rather than for large public broadcasts, with use cases including one-to-one meetings, team syncs, design sessions, document editing, and code reviews.
The project is no longer an independent service in the same form. According to the information published on its website, Around was acquired by Miro to help shape the future of team collaboration. That status is important for anyone researching the product today, because descriptions of its applications and features refer primarily to the platform as it operated before the acquisition. Even so, the product offers a clear example of how remote meeting software can be designed around focused work instead of treating every call as a conventional conference.
What Around Was Designed To Be
Around described itself as video collaboration reimagined for the remote-first era. Its design emphasized a lean interface and proprietary technology intended to support sessions with a small number of participants. The service was especially relevant when a meeting happened alongside another task: reviewing a document, discussing a design, examining code, or making a decision while working in a separate application.
This approach differs from a meeting tool used only for presenting slides to a large audience. Around was positioned closer to the shared desktop and the active work process. Participants could remain in contact while continuing to use the applications needed for the session. The goal was to preserve the human element of a video call while reducing the amount of screen space and attention consumed by the meeting itself.
That focus also explains why the platform recommended collaboration sessions with only a few other participants. Smaller groups generally allow people to exchange ideas, ask questions, and respond to changes in a document or codebase without the formal structure required by a large event. Around could therefore fit into recurring team habits such as a short project check-in, a pair review, or an informal working session.
For someone encountering the phrase , the relevant subject is Around: a video collaboration service built to keep remote colleagues connected while they worked on the same task. The name should therefore be understood in the context of remote teamwork, not as a general-purpose messaging product or a standalone document editor.
Typical Workflows And Participants
Around’s most suitable workflows were collaborative and interactive. A team could use it when members needed to look at the same material, make decisions in real time, or discuss progress without leaving their normal work environment. The platform’s own examples included document editing, design sessions, and code reviews, all of which depend on conversation as well as visual reference.
In a document-editing session, participants might discuss wording, structure, or an open issue while one person made changes. In a design session, the group could review an interface, compare alternatives, and respond to feedback as the work developed. During a code review, the call could provide a place to explain implementation choices, examine a change, and resolve questions that would be inefficient to handle through written comments alone.
The same model applied to one-to-one meetings and team syncs. A manager and employee could use the service for a focused conversation, while a small project group could use it to coordinate work. The product was not presented as a replacement for every communication channel. Rather, its value came from combining live video with the context of the task being discussed.
- One-to-one meetings: useful for focused conversations between two remote colleagues.
- Team syncs: suitable for short coordination sessions involving a small working group.
- Document collaboration: supports discussion while participants edit or review material together.
- Design sessions: helps teams discuss visual work and decisions in real time.
- Code reviews: provides a live setting for explaining changes and resolving technical questions.
- On-the-fly sessions: allows colleagues to start a conversation when written messages are not enough.
The platform supported up to 50 participants in a meeting. That limit placed it between a private conversation tool and a large-scale webinar system. It could accommodate a substantial internal meeting, but its stated recommendations still centered on smaller groups where active participation was expected.
Desktop, Browser, And Mobile Access
Around offered native applications for Mac and Windows as well as a web application. The minimum desktop requirements listed in its frequently asked questions were macOS Mojave or later for Mac computers and Windows 10 for Windows computers. For browser access, the service supported Google Chrome and the latest versions of Safari, Firefox, and Microsoft Edge.
A participant did not necessarily need to install the desktop application. Someone who had the app could share a room link with a guest, and that guest could join through the web app using a supported browser. This arrangement was practical for occasional participants, clients, interview candidates, or colleagues who did not regularly use Around. It reduced the setup required before a meeting and separated the host’s preferred workflow from the guest’s access method.
The browser experience was not identical to the native desktop experience. As explained in the overview labeled around adalah, the web app had limited functionality compared with the Mac and Windows applications. The most notable difference was the absence of Floating Mode. In the desktop application, Floating Mode placed the video interface on top of other applications, allowing participants to maintain visual contact while working elsewhere on the computer. The service recommended the native application for regular users and the web app for guests who did not have Around installed.
Around also provided mobile applications for iOS and Android. The mobile apps were intended to keep team members connected away from their computers and supported both starting and joining a call. Users could hand off a session from computer to phone and back again, which was useful when moving between work locations or when a computer was no longer the most convenient device.
Mobile features included chat messages, GIFs, and emojis for responding to conversations, along with the ability to share images from the camera roll. Users could also view high-resolution screen shares. These capabilities made the mobile application more than a simple audio fallback, although the desktop environment remained the more natural setting for workflows involving documents, design files, or source code.
Recording, Slack, And Meeting Continuity
Around included a Recording feature identified as being in beta. It allowed a meeting to be recorded for later viewing and offered an immersive playback experience intended to make the viewer feel involved in the original meeting. That presentation was relevant to distributed teams working across time zones, because a person who could not attend live could review the session afterward rather than relying only on a brief written summary.
Recording also had practical limits. A recorded meeting is not automatically equivalent to a transcript, a task list, or a decision log. Teams still need to identify the important outcomes of a session and record them in the systems they use for project management or documentation. Around’s recording capability addressed access to the meeting itself; it did not replace the broader process of turning discussion into accountable work.
The service also offered a Slack integration. After connecting Slack with Around, users could type /around in a Slack message to start the related workflow from the team’s communication environment. This reduced the need to switch manually between applications when a written conversation needed to become a live discussion. It also reflected the product’s broader position: video was treated as one part of a remote team’s working system rather than an isolated destination.
These integrations mattered because remote collaboration often breaks down at the transition points between tools. A team may begin with a text message, move to a call to resolve ambiguity, and then return to a document or code review. The combination of room links, browser access, desktop Floating Mode, mobile handoff, recording, and Slack initiation was designed to make those transitions less disruptive.
How To Assess Around In Its Historical Context
A useful way to understand Around is to separate its product principles from its current availability. The service’s published information described a video platform focused on remote-first collaboration, small-group work, and a lightweight interface. It supported up to 50 participants, invited guests through browser links, and provided Mac, Windows, iOS, Android, and browser access with different feature sets across those environments.
Its strongest fit was a team that needed to talk while doing something else. A conventional meeting platform can be effective when every participant is expected to watch the same presentation or remain inside one meeting window. Around addressed a different situation: colleagues who needed conversation but also needed to keep working in documents, design tools, development environments, or other applications.
The distinction between native and browser access was central to that model. Guests could join without installing the app, which simplified participation. Regular users were encouraged to use the desktop applications, where Floating Mode and the fuller feature set were available. Mobile applications extended access to calls and supported device handoff, while recording and Slack integration addressed continuity before and after the live session.
Because Around was acquired by Miro, readers should treat historical feature descriptions as documentation of the product’s operation during its independent period, not as a promise that every function remains available today. The acquisition nevertheless explains why the service is relevant to the broader development of collaborative work software. Around’s product direction concentrated on reducing friction between video communication and the applications where remote teams actually perform their work.
In practical terms, Around was best understood as a focused collaboration layer for remote teams: a way to hold a conversation, preserve visual contact, invite people through a room link, move between devices, and continue working without making the meeting window the only place where work happened. That definition captures both the service’s intended audience and the specific features that distinguished it from a generic video call.