When Small Teams Need Video Without Losing Their Workspace
Some video calls take over the whole screen and, somehow, the whole meeting. Everyone appears in a large grid. The document gets pushed behind another window. The design file disappears. People spend more time arranging apps than working together. Around was created as a different kind of video collaboration tool for remote-first teams.
The idea was simple. A call should stay present without covering the work. Around used a lean interface and its own collaboration technology to support one-on-one conversations, team syncs, and quick sessions that did not need a formal meeting setup. It was especially suited to a few people working inside the same document, design, or codebase.
Around was later acquired by Miro, the visual collaboration platform. That acquisition matters because the two products shared a broad goal: helping distributed teams collaborate in a space that feels less rigid than a traditional conference call. To understand what made Around interesting, it helps to look at how people actually used it rather than treating it as just another video chat app.
What Around Was Designed to Do
Around was not built around the assumption that every participant should sit still and watch a wall of faces. Its main role was to keep people connected while their attention remained on shared work. That difference sounds small, but it changes the feel of a session.
Think about two developers reviewing a pull request. They need to see each other, but the code is the main event. The same goes for designers comparing layouts or coworkers editing a proposal. In those situations, a conventional full-screen meeting can feel oversized. Around aimed to make the human presence visible without turning it into the largest object on the screen.
The service worked well for planned sessions, but it also made sense for spontaneous calls. A teammate could open a room when a written conversation became too slow or confusing. Instead of scheduling a formal meeting, the group could talk, share a screen, resolve the issue, and move on.
“The call should support the work, not become the work.”
That is the easiest way to describe the product philosophy. Around was video collaboration shaped around an active workspace rather than a digital conference room.
Why Floating Mode Was the Standout Feature
The native desktop apps included Floating Mode. This placed the video interface on top of other applications. Participants could remain visible while everyone worked in a browser, design tool, text editor, spreadsheet, or other program.
This was more than a cosmetic trick. Keeping small video windows available helped preserve social cues. You could notice when someone wanted to speak, looked confused, or reacted to a change. At the same time, the shared material stayed large enough to use comfortably.
The web version did not offer the same complete experience. Most notably, it lacked Floating Mode. Guests could still join through a supported browser, which reduced friction for occasional participants. Regular users, however, were encouraged to install the native Mac or Windows app so they could use the product as intended.
That split was practical. A client, contractor, or interview guest did not have to install software before joining. Core team members could use the desktop app and get the persistent overlay that made Around distinct. It balanced easy access with a more capable setup for daily collaboration.
Common Ways Teams Used Around
If you came across the search phrase around adalah, the clearest interpretation is that it refers to Around as a compact video collaboration service for remote teamwork. It was not simply a social calling app, and it was not limited to formal company meetings. Its strongest use cases involved people talking while actively making or reviewing something together.
Based on the product’s own guidance, typical sessions included:
- Collaborative writing: coworkers could edit a document while discussing wording, structure, or feedback in real time.
- Design work: a small group could compare ideas, review visual changes, and make decisions without losing sight of one another.
- Code reviews: developers could examine code together while keeping the conversation close to the technical material.
- One-on-one meetings: managers and teammates could have a direct conversation without setting up a large meeting environment.
- Team syncs: small groups could check progress, identify blockers, and then return to their regular tools.
- On-the-fly sessions: people could shift from chat to a live call when an issue was easier to explain by voice or screen share.
The phrase “small group” is important here. Around supported meetings with up to 50 participants, but its design was particularly appealing when only a few people needed to collaborate closely. A 50-person limit made larger calls possible, yet the product’s compact interface made the most sense for focused working sessions.
This also explains why Around should not be judged only by the number of attendees it allowed. Its real value was in reducing visual and procedural overhead. The goal was not to pack as many people as possible into a room. The goal was to let the right people solve a problem together.
Desktop, Browser, and Mobile Access
Around provided native applications for Mac and Windows. The stated minimum desktop requirements were macOS Mojave or later and Windows 10. For users joining through the web app, the service supported Google Chrome along with current versions of Safari, Firefox, and Microsoft Edge.
Room links made guest access straightforward. Someone with the installed app could share a room link, and invitees without the software could enter through the browser. That was useful for cross-company work because every participant did not need the same local setup.
The browser app had fewer features than the native versions. Floating Mode was the most obvious omission, so people who used Around often had a reason to install the desktop client. The web app was better viewed as a convenient entry point for guests rather than a perfect replacement for the full app.
Around also offered mobile apps for iOS and Android. Users could start or join calls from a phone and hand a session off between a computer and mobile device. That handoff feature was helpful when someone needed to leave a desk without leaving the conversation.
The mobile experience went beyond passive attendance. Participants could send chat messages, GIFs, and emoji reactions. They could share images from the camera roll and view high-resolution screen shares. Those options made the phone app useful for responding to a discussion, checking visual work, or continuing a meeting while moving between locations.
Recording and Slack Support
Around included a meeting recording feature in beta. It allowed teams to save a session and watch it later. The playback experience was described as immersive, with the intention of helping a viewer feel present in the original conversation rather than merely watching a flat archive.
Recording could help when a key teammate missed a review or when a discussion contained decisions worth preserving. It could also reduce the need to repeat a walkthrough for several people. As with any workplace recording tool, teams still needed clear consent and sensible rules about storage, access, and confidential material.
The service also offered a Slack integration. Once a workspace had been connected, users could type the /around command in Slack to begin using Around from a conversation. This matched the product’s emphasis on quick collaboration. A text thread could become a live working session without forcing everyone through a long scheduling process.
That workflow was a good fit for remote teams. Written messages are excellent for updates and questions that do not need an immediate answer. They become less efficient when people exchange many replies to explain a visual detail or diagnose a problem. A lightweight call can resolve that kind of issue faster, especially when screen sharing is involved.
How Around Differed From a Standard Video Meeting
The obvious comparison is with a traditional video conferencing platform. Both let people talk remotely, share screens, and gather in virtual rooms. The difference was the emphasis. Standard meeting software often treats the participant grid as the center of the experience. Around treated the work surface as the center.
That made it a better conceptual match for “working together” than for “presenting to an audience.” A sales presentation, company-wide event, or formal webinar may benefit from prominent speakers and structured audience controls. A pair of designers changing a mockup usually needs something lighter. Around focused on the second situation.
Its compact visual approach could also reduce the strange pressure of staring at large faces for an entire meeting. Participants remained visible, but they were not required to dominate one another’s screens. The interface encouraged people to look at the document or shared screen, which is where their attention would naturally go in an in-person working session.
Still, Around was not a substitute for every communication method. Some topics belonged in an asynchronous message. Some decisions needed a written record. Some large events required tools built for broadcasting and moderation. Around made the most sense when a small number of people needed quick, live coordination around a shared task.
What the Miro Acquisition Means for the Product Story
Around’s acquisition by Miro placed its ideas in a wider collaboration context. Miro is known for visual teamwork, while Around approached video as a layer that could sit beside active work. The pairing was logical: remote teams need both a place to create and a way to communicate while creating.
For anyone researching Around now, this context is essential. The product should be understood not only as a standalone video app, but also as part of the evolution of remote collaboration. Its strongest idea was that video did not have to occupy the whole workspace. It could remain lightweight, visible, and connected to the task at hand.
That idea is still relevant. Remote workers often switch between chat, documents, whiteboards, code editors, and video calls throughout the day. Every switch adds a little friction. Around tried to remove some of that friction through small video windows, simple room access, desktop and mobile apps, browser support for guests, recording, and Slack integration.
So, in practical terms, Around was a remote-first video collaboration platform built for people who wanted to keep working during a call. It supported up to 50 participants, but its personality came through most clearly in small sessions. The native desktop experience, especially Floating Mode, was the defining piece. Everything else served the same basic goal: keep the team connected without hiding the work they came together to do.
