If you have seen the phrase Around in a discussion about remote work, it refers to a video collaboration product built for teams that work together online. Around, associated with around-com.com, was designed for the remote-first era. Its main idea was simple: a video call should support the work on your screen instead of taking over your screen.

That approach made Around different from a conventional full-screen meeting room. The product focused on lightweight, spontaneous collaboration among a small group of people. It was especially well suited to one-on-one conversations, quick team syncs, document editing, design sessions, and code reviews. People could stay visible to one another while continuing to use the tools where the actual work was happening.

Around was later acquired by Miro to help shape the future of team collaboration. That acquisition makes sense when you look at the product’s original purpose. Miro centers on shared visual work, while Around was created to make live conversation feel like a natural layer above collaborative software. They addressed closely related parts of the remote teamwork experience.

What Made Around Different

The key feature was not simply video calling. Plenty of products can place several people in a grid. Around was built around a less intrusive interface and proprietary technology intended to keep collaboration comfortable. The participants remained present, but the call did not need to dominate the desktop.

The clearest example was Floating Mode in the native desktop apps. This mode allowed the video interface to remain on top of other applications. A participant could edit a shared document, inspect a design, review code, or move through a project board without losing visual contact with teammates. Instead of switching repeatedly between the call and the work, the call stayed alongside the work.

That detail matters more than it may sound. In a normal video meeting, screen space is often split between a large meeting window and the application being discussed. The layout encourages people to watch faces or slides rather than contribute directly. Around treated faces as useful context, not as the whole event. The shared task stayed in the foreground.

The product was therefore strongest in active sessions. Think of two designers adjusting a layout together, a developer walking through a pull request, or several teammates rewriting a planning document. These are not passive presentations. Everyone needs to see the shared material, speak when needed, and notice the reactions of other participants. Around was designed for that combination.

It could also support larger meetings, with a stated limit of 50 participants on a call. Still, its own usage guidance emphasized collaboration with a few other people. The distinction is important. Technical capacity tells you how many people may enter a room. Product fit tells you what kind of meeting best matches the interface. Around’s fit was the focused working session rather than the crowded company broadcast.

For readers trying to interpret the mixed-language search phrase , the practical meaning is that Around was a remote video collaboration platform, not merely a generic reference to something nearby or surrounding an object. In this context, Around is the product name. Its identity comes from compact video presence, collaborative sessions, desktop and web access, mobile support, and connections to the tools teams already used.

There was also a low-friction guest experience. A person with the desktop app could share a room link with someone who had not installed it. The guest could join through the web app using Google Chrome or recent versions of Safari, Firefox, and Microsoft Edge. This was useful for client calls, interviews, partner sessions, and other situations where requiring every visitor to install software would slow things down.

The web version did not include all of the native app’s functionality. Most notably, it lacked Floating Mode. That limitation reflected the role of each version. The browser experience was convenient for occasional guests, while the Mac and Windows apps were the better choice for people who planned to use Around regularly and wanted its distinctive desktop workflow.

Setup and Session Checklist

Around was meant to feel lightweight, but a good session still depended on choosing the right version and preparing the room. The following checklist covers the practical points that mattered most.

  1. Confirm that the meeting is collaborative. Around made the most sense when people were going to edit, review, sketch, plan, or solve something together. If the session was only a long presentation to a silent audience, its collaboration-first layout offered less of an advantage.

  2. Choose the native app for regular use. The desktop apps delivered the fuller experience, including Floating Mode. Mac users needed macOS Mojave or later, while Windows users needed Windows 10. Checking the operating system before a scheduled session avoided last-minute installation trouble.

  3. Use the browser option for guests. Someone without the app could enter through a shared room link. Supported browsers included Google Chrome and current versions of Safari, Firefox, and Microsoft Edge. The guest should understand that the web app had fewer features than the desktop software.

  4. Keep the working material ready. Open the document, code, design file, or other shared resource before the conversation begins. Around worked best when the team could move into the task quickly rather than spending the first several minutes searching for files.

  5. Match the group size to the task. Calls could include as many as 50 participants, but a smaller group was usually a better match for hands-on collaboration. Invite the people who will contribute directly. A compact room makes discussion and decision-making easier.

  6. Decide whether recording is appropriate. Around offered a Recording feature in beta. It allowed a meeting to be saved for later viewing and used an immersive playback experience intended to help viewers feel present in the original session. As with any recording tool, participants should know when a session is being captured. around adalah

  7. Plan for device changes. Around also provided mobile apps for iOS and Android. A participant could start or join a call on mobile and hand the session off between a computer and a phone. This helped when someone needed to leave a desk without leaving the conversation.

  8. Use integrations where they reduce friction. Around included a Slack integration. Once connected, a user could start the process from Slack with the slash command provided by the service. That made a quick call easier to launch from an existing team conversation.

The mobile apps were more than simple audio companions. Users could react or reply with chat messages, GIFs, and emojis. They could share images from a camera roll and view high-resolution screen shares. Those capabilities kept a mobile participant involved instead of limiting that person to listening.

The handoff feature was particularly practical for remote workers. Someone might begin a design review at a desk, move the call to a phone when leaving the room, and then return it to the computer later. The point was continuity. Changing devices did not have to mean ending one session and creating another.

Recording served a different need. A live working session may produce decisions that are difficult to capture in written notes alone. A recording preserves the sequence of the discussion, including the context around a change or decision. Around’s beta recording feature also emphasized playback as an experience rather than treating the result as a plain video file. That could help an absent teammate understand how the group reached its conclusion.

Where Around Fit Best

Around’s strongest use case was a small remote team that already spent much of the day inside shared applications. The team did not need another virtual conference room competing for attention. It needed a thin communication layer that stayed available while people worked. Floating Mode directly supported that need.

For document editing, participants could keep the text large and readable while maintaining visual awareness of one another. This made it easier to notice when someone wanted to comment or when a proposed edit caused confusion. The conversation remained connected to the document instead of drifting into a separate meeting space.

In a design session, visual reactions can be useful. A designer can tell whether a teammate understands a layout before that person gives a formal response. At the same time, the design canvas needs room. A compact, persistent video interface balances those needs better than a large gallery view that squeezes the working area.

Code reviews follow a similar pattern. The code should be the main object on screen. Participants may need to navigate files, inspect a specific line, or compare an implementation with a requirement. Video provides social context, but it should not hide the editor or browser. Around’s desktop approach was aligned with that workflow.

Quick syncs were another natural fit. Remote teams often need ten minutes to settle a question that would take much longer in a message thread. Starting a lightweight room from Slack could shorten the path from written discussion to live problem-solving. Once the issue was settled, everyone could return to asynchronous work.

The product was less distinctive when Floating Mode was unavailable. A browser guest could still join and participate, which was valuable, but the browser experience did not fully express the core design. For a one-time visitor, convenience was the priority. For a regular team member, installing the desktop app was the more sensible choice.

The 50-person limit should also be read as a ceiling, not a recommendation for every session. A room with dozens of attendees changes the social dynamic. People become viewers, speaking turns become formal, and direct collaboration becomes harder. Around could technically host that group size, but its best-known strengths appeared in smaller sessions where the participants were actively working.

Its mobile support expanded the product without changing the central idea. The goal was not to force every task onto a phone. It was to keep a person connected when the desktop was temporarily unavailable. Viewing a high-resolution screen share, sending a quick image, responding in chat, or reacting with an emoji can be enough to remain part of the session while moving around.

The acquisition by Miro is an important part of the product’s story. Around had developed a clear point of view about remote collaboration: video should feel integrated with creation, not separate from it. Miro operates in the broader space of visual teamwork and shared digital workspaces. Bringing Around into Miro connected two products concerned with how distributed teams think and build together.

So the short version is straightforward. Around was a video collaboration tool designed for remote-first work, with native apps for Mac and Windows, browser access for guests, mobile apps for iOS and Android, a meeting capacity of 50, beta recording, Slack integration, and a signature Floating Mode in the desktop experience. It was most compelling during small, active sessions such as document editing, design collaboration, code review, and quick team syncs.

If you are evaluating what made the service notable, focus on that workflow rather than on video calling alone. Around’s value was the way it placed conversation beside the task. The people stayed visible, the shared work kept center stage, and joining did not have to become a project of its own. That is the core idea behind the name in a collaboration context and the reason the product stood out in remote-work discussions.