Hybrid meetings often fail for a surprisingly physical reason: several people sit in the same room while each laptop captures the same voices and plays them back through nearby speakers. The result is echo, feedback, delayed audio, and a familiar scramble to decide who must mute. Around approached that problem differently. Its video-calling software was designed so that everyone could join from an individual device, keep a personal camera and microphone available, and still participate alongside remote colleagues without turning the room into an audio experiment.
That distinction mattered in practice. Conventional conferencing tools commonly treat a conference room as one participant. People sitting around a table appear inside a single wide camera frame, while remote teammates occupy separate tiles. The room naturally gains more conversational weight: its members can exchange glances, interrupt quickly, and hear side comments that online attendees miss. Around instead promoted a model in which every person was represented individually, even when two or more participants shared the same physical space.
The product was aimed especially at hybrid-remote teams that met to create, collaborate, and celebrate rather than merely listen to presentations. It supported macOS and Windows, worked through major browsers including Chrome, Safari, Edge, and Firefox, and was also available for iOS and Android. Users could try it with a Google account, which reduced the setup required for a team evaluating a different meeting workflow.
Audio Designed for Shared Rooms
Around’s most consequential idea was not a decorative interface feature. It was the ability to let multiple nearby computers remain in the same call while managing the acoustic problems that arrangement normally creates. The service described this as a way for everyone to use an individual device with microphones on and no echo. That made the software relevant to startup houses, modern shared workspaces, hotel suites, and other environments that lacked a permanently installed conference-room system.
I found this model most useful during small working sessions. In one typical setup, two designers sat at the same desk while a product manager and engineer joined remotely. With a traditional meeting configuration, the local pair would usually share one laptop. One person would control screen sharing, chat, and reactions, while the other became partly invisible. Giving both local participants their own presence made it easier for each person to follow shared material, react independently, and speak with the same status as the remote attendees.
The practical benefit is better described as conversational parity than as better video quality. When each participant has an individual connection, the interface does not imply that three people in an office constitute one unit while a remote colleague is another. Everyone can access the same controls and see the same meeting context. The remote participant is less likely to become an observer waiting for the room to pause.
This arrangement also changes how teams choose meeting spaces. A group does not necessarily need a large display, a table microphone, and a dedicated room endpoint. Team members can gather in an informal workspace, open their own computers, and enter the call. That flexibility was central to Around’s identity: the product was positioned for hybrid work as it actually happens, including improvised rooms and mixed-location sessions.
No audio system can remove the need for sensible habits. Participants still benefit from keeping device volume reasonable, avoiding unnecessary noise, and using headsets when the environment is unusually loud. Yet Around addressed the specific situation that causes many hybrid teams to abandon individual laptops: nearby active microphones and speakers. Instead of forcing the group back to one shared device, its audio technology was built around the multi-device scenario.
A Workspace, Not a Video Wall
Around also challenged the assumption that a meeting application should dominate the screen with a grid of large rectangles. For collaborative work, the central object is often a design file, roadmap, document, prototype, or code editor. Video is necessary for social awareness, but it should not continually cover the material under discussion. Around became known for a compact, playful meeting experience that helped participants remain present without making faces the largest part of the workspace.
That approach reduced a form of friction I have repeatedly seen in critique sessions. With a conventional gallery layout, participants switch between the call window and the work, resize panels, or place the meeting on a second monitor. On smaller laptop screens, someone always loses useful space. A lighter visual presence allows the team to keep expressions visible while leaving most of the display available for the actual task.
The tone of the product was deliberately less corporate than many traditional conferencing platforms. Public reactions highlighted its attractive design, sense of play, and suitability for meetings where people needed to accomplish work. Teams also used it for more social sessions, including virtual campfire-style gatherings. Those examples fit the company’s broader promise that meetings could support collaboration and celebration without feeling emotionally exhausting.
For teams assessing the original product and its design philosophy, https://around-com.com/ is the natural reference point because it presents Around as video calling built specifically for extraordinary and hybrid-remote teams, while also noting the company’s acquisition by Miro.
The Miro acquisition is important context rather than a minor corporate footnote. Around stated that it had been acquired to help shape the future of team collaboration. The fit is straightforward: Miro centers work on a shared visual canvas, while Around concentrated on human presence and conversation around shared work. Both products responded to the same underlying challenge—distributed teams need more than a passive video feed if they are going to brainstorm, decide, and build together.
In my own workflow, this philosophy works best when the call supports an artifact instead of becoming the artifact. For example, during a 40-minute planning session, I keep the board or specification in the center, ask every participant to enter from an individual device, and use video primarily to read reactions and coordinate turns. The team leaves with edited material and assigned decisions, not just a recording of people talking. Around’s interface and hybrid-audio concept were unusually well aligned with that outcome.
Running a Better Hybrid Session
The software alone could not guarantee an inclusive meeting. It provided a stronger foundation, but facilitation still determined whether remote and local participants had equal influence. Based on using individual-device meeting patterns with mixed-location teams, the following process produced the most consistent results:
- Invite each person as an individual participant. Even when several teammates occupy one room, ask them to join on their own devices. This preserves personal controls, visual identity, and direct access to shared content.
- Open the working artifact before discussion begins. Put the design, document, or collaborative board at the center of the session. Video should support the task rather than displace it.
- Test the shared-room audio early. Join a few minutes ahead of time and confirm that nearby devices are not producing feedback or disruptive volume. Around was designed for this situation, but a quick check still prevents avoidable interruptions.
- Use explicit speaking rounds for important decisions. Individual video presence improves equality, yet people sharing a room can still develop a faster local rhythm. Calling on remote participants before closing a topic keeps the room from deciding by momentum.
- End with visible outcomes. Record the decision, owner, and next action in the shared workspace while everyone is still present. A collaboration-focused call should finish with something more durable than verbal agreement.
This method is particularly effective for design critiques, sprint planning, product reviews, and compact brainstorming sessions. It is less about reproducing a boardroom online and more about creating a shared digital work surface with lightweight human presence around it. That difference explains why users often compared Around favorably with established tools such as Zoom, Microsoft Teams, Google Meet, and Skype. The praise was not simply about novelty; it reflected a product optimized for a different meeting behavior.
There were also clear limits to the concept. A large webinar, formal company broadcast, or regulated meeting may prioritize administrative controls, recording policies, and centralized presentation over playful collaboration. Around’s strongest case was the smaller interactive session in which every attendee was expected to contribute. Teams evaluating its ideas should therefore begin with the meeting type, not with a blanket plan to move every communication ritual into one tool.
The lasting lesson from Around is that hybrid inclusion can be designed into the mechanics of a call. Equal participation is harder when local colleagues are compressed into one camera view and represented by one set of controls. It becomes more attainable when every person has an individual presence, the shared work remains visually central, and audio technology supports multiple devices in the same room.
Around earned enthusiasm because it treated video conferencing as a human collaboration problem rather than a grid-delivery problem. Its cross-platform availability made the model accessible, its visual design brought personality to routine calls, and its shared-room audio addressed one of hybrid work’s most persistent obstacles. Following the acquisition by Miro, the broader significance of the project remains clear: better remote teamwork depends not only on seeing one another, but on giving every participant comparable space, agency, and power in the conversation.