Around was built for a familiar remote-work problem: a team needs to talk while continuing to work in documents, design files, or code. A conventional video meeting can make the call itself the center of attention, even when the real task is on another part of the screen. Around’s approach was to keep participants visible without requiring the meeting window to dominate their workspace. Its product information describes a video collaboration service for one-on-ones, team check-ins, and short sessions organized around shared work.

That distinction matters when assessing what Around was designed to do. It was not presented simply as a place to gather people on camera. Its recommended uses included editing documents together, holding design sessions, and conducting code reviews. In each case, participants need to see the material they are discussing, speak to one another, and make decisions as the work progresses. The video connection supports that process rather than replacing the working surface.

What Around Was Designed to Keep in View

Around’s defining desktop feature was Floating Mode. According to the product’s FAQ, this mode lets the video interface sit on top of other applications, so participants can maintain visual contact while using the tools where their work lives. Someone reviewing a draft could keep the document open; a designer could stay in a design application; a developer could follow changes in an editor. The call remained present, but it did not have to occupy the main window.

This layout reflects the kind of meeting Around emphasized. A focused discussion among a few colleagues has different screen-space demands from a presentation to a large audience. When the group is actively changing a file or evaluating work in progress, switching repeatedly between a full meeting window and the relevant application adds friction. Floating Mode addressed that specific interaction: seeing colleagues and seeing the work at the same time.

The FAQ recommended Around for collaboration sessions with a few other participants, although it also stated a meeting limit of 50 people. Those figures describe different things. The limit establishes how many people could join a call; the recommendation describes the smaller, working-group sessions the product was intended to serve especially well. A team deciding whether Around fit its routine would therefore look beyond the maximum head count and consider how often its meetings involved joint work on a screen.

Desktop, Browser, and Mobile Access

Around offered native applications for Mac and Windows as well as browser access. The FAQ listed macOS Mojave or later and Windows 10 as the minimum desktop requirements at the time it was published. For the web app, it named Google Chrome and current versions of Safari, Firefox, and Microsoft Edge. These details are useful as a record of the product’s stated compatibility, but software requirements can change; they should not be treated as a current installation guarantee without checking the latest product information.

Browser access had a practical role in invitations. A person with the desktop app could share a room link with someone who had not installed Around, and that guest could join through the web app. The two experiences were not identical. Around said the browser version had more limited functionality, most notably because it lacked Floating Mode. Its guidance was consequently to use the Mac or Windows app for regular participation and the browser option for guests who needed a straightforward way into a meeting.

Mobile participation extended the service beyond the desk. Around listed apps for iOS and Android that could start or join calls. The mobile feature set also included moving an active call between a computer and phone, sending chat messages, GIFs, and emoji reactions, sharing images from a camera roll, and viewing high-resolution screen shares. Those capabilities served a different situation from desktop co-editing: a participant could stay involved while away from a computer, follow what colleagues were showing, and contribute a response or image without returning to a workstation first.

• Native desktop apps: The option Around recommended for frequent use, including access to Floating Mode.
• Web app: A way for invited guests to join from a supported browser without installing the desktop application.
• iOS and Android apps: Options for joining or starting calls, viewing shared screens, and moving between phone and computer.

Why the Phrase “Around Is” Points to a Specific Product

The phrase around adalah asks a direct question about the product’s identity: Around was a video collaboration tool organized around remote teamwork. Its stated purpose was not just to carry audio and video between participants, but to let a small group keep working together during the call. Floating video on desktop, browser-based guest entry, and participation from mobile devices were different parts of that same design. They addressed what happens before a session starts, while people work across applications, and when someone has to change devices.

That description also helps distinguish Around from a general-purpose meeting room. Consider a code review: participants may need to inspect a change, discuss an implementation choice, and keep their development tools visible. In a document session, they may be editing the same material while talking through wording. In a design session, the object under review is likely more useful on screen than a large grid of faces. Around’s recommended scenarios shared this pattern of conversation tied to an active task.

There is an important limit to the description. The available FAQ explains Around’s intended workflow and enumerates features, but it does not establish that every listed feature is still offered today in the same form. It also states that Around was acquired by Miro to help shape the future of team collaboration. That acquisition is part of the product’s history; it should not be read as proof of a particular present-day integration, subscription arrangement, or service status.

How a Typical Collaboration Session Worked

The product information supports a straightforward picture of how a team might use Around. A regular participant could use a native desktop app and invite colleagues to a room. Someone without the app could join through a browser, accepting that the browser experience did not include every desktop feature. Once connected, the group could keep the work itself in view and use the call for discussion. On desktop, Floating Mode was the feature intended to make that arrangement less intrusive.

1. Choose the working surface. The team opens the document, design file, or code it needs to discuss in its usual application.
2. Bring participants into the room. Regular users can join from a desktop app, while invited guests can use a supported browser.
3. Work and talk together. Participants discuss the material while it remains visible; desktop users can use Floating Mode to keep video in sight over other applications.
4. Continue from a phone when necessary. A mobile participant can join or start a call, view a shared screen, send a reaction or message, and use the stated computer-to-phone handoff capability.

These steps describe the roles of Around’s published features, not a required procedure imposed by the service. A one-on-one conversation might need little more than a call. A design review might rely heavily on screen sharing, while a document session might be driven by edits made in another application. The common element is that the meeting exists to support the work taking place alongside it.

Around also listed a Slack integration. Its FAQ said that, after connecting Slack with Around, users could enter an /around command in Slack. The available description does not provide enough detail to characterize every action that command performed, so the narrower point is the relevant one: Around provided an entry point from a communication tool teams might already use. That complemented the room-link invitation model without changing the product’s emphasis on live collaboration.

Recording, Scale, and the Miro Acquisition

Live participation was not the only way Around described a meeting’s value. The FAQ identified a Recording feature in beta that could save a meeting for later viewing. Around described its playback as an immersive experience intended to give a later viewer a sense of taking part in the original session. The beta label is significant: it identifies the feature as a developing capability in that product description, not as an unconditional promise about availability or behavior.

Recording has a distinct use in the kinds of sessions Around highlighted. A colleague who misses a design discussion may need more than a final file; the conversation can explain why a particular choice was made. Someone reviewing a code change later may likewise benefit from hearing the reasoning behind a decision. Around’s recording description points to that continuity between live collaboration and later review, although the FAQ excerpt does not specify details such as storage limits, permissions, or retention policies.

The stated 50-participant meeting limit shows that Around could accommodate more than a pair or a small team, but its recommended examples remain the clearest guide to its intended use. The service was framed around people doing work together in real time, with video arranged to take up less of their attention. Desktop, browser, and mobile access made it possible for participants to enter that conversation from different situations, even though the desktop and web experiences differed.

Around’s acquisition by Miro places that approach in a broader collaboration context. The FAQ says Around was acquired to help shape the future of team collaboration, but it does not spell out what became of each Around feature afterward. The defensible conclusion is more specific: Around developed a video experience centered on keeping shared work visible, with Floating Mode as its clearest expression, and its team and technology later became part of Miro’s collaboration efforts.