Hybrid meetings often fail for reasons that have little to do with the quality of anyone’s ideas. Two people sitting together in a room naturally exchange glances, interrupt at comfortable moments, and hear one another without delay. A remote colleague appears on a distant screen, waits for a gap, and may struggle to judge whether anyone noticed a raised hand or an unfinished sentence. Around approached this imbalance as a design problem rather than treating it as an unavoidable consequence of remote work.
The product was built for teams that meet to create, collaborate, and make decisions, not merely to watch a grid of faces. Its defining premise was simple: everyone could join from an individual device, even when several participants were sitting in the same physical space. Microphones could remain active without producing the echo and feedback normally associated with multiple laptops in one room. That technical choice gave each participant a personal camera, microphone, and position in the conversation.
In practice, this changed the social structure of a meeting. I have worked in sessions where three designers shared a conference table while a product manager joined from home. With conventional room equipment, the remote participant heard side conversations as indistinct background noise and could not always tell who was speaking. An individual-device setup made names, expressions, and voices easier to associate. The people in the room no longer merged into one group identity, while the person at home stopped feeling like an outside observer.
Individual Devices Solve More Than an Audio Problem
Placing every participant on a separate device sounds counterintuitive at first. In many meeting tools, opening several laptops in one room creates a sharp feedback loop, delayed echoes, or repeated fragments of speech. Teams respond by muting nearly everyone, routing audio through one computer, or asking co-located employees to gather around a single camera. Those workarounds solve the noise problem by sacrificing participation quality.
Around promoted a different model through its audio technology: all microphones on, no echo. The objective was not simply cleaner sound. It was to give people in the same room and people joining remotely a comparable “power of voice.” A participant could speak through the device directly in front of them instead of relying on a shared microphone several feet away. Remote colleagues could hear contributions as part of the main discussion rather than as ambient room chatter.
I found this distinction most noticeable during fast critique sessions. Designers frequently respond with short comments such as “move that element,” “keep the previous version,” or “I agree with Maya.” If four people share one microphone, these remarks can arrive at a remote listener without enough context. When each person has an identifiable audio and visual presence, the conversation is easier to follow. The improvement is not dramatic in the theatrical sense; it is a steady reduction in small moments of uncertainty, and those moments add up over a forty-five-minute meeting.
The individual-device model also reduces a subtle hierarchy created by conference-room cameras. A wide-angle room view makes co-located participants look small and distant, while a remote participant may occupy a large tile. Yet the room still controls the rhythm because its members can read body language that the remote person cannot see. Around’s compact, participant-centered presentation was designed to keep people visible without making their faces consume the entire workspace. This was particularly useful when the real focus belonged on a document, prototype, or shared creative task.
That emphasis helps explain why users described Around as software for people who meet to get work done. The platform’s identity was not based on reproducing a boardroom on a screen. It was meant to coexist with the work already open on each participant’s computer. For a product team, that might be a design canvas; for developers, an issue tracker or code review; for a marketing group, a draft campaign. Video remained present enough to preserve human connection, but it did not have to dominate the desktop.
A Meeting Interface Built Around Shared Work
Many video products inherited the visual grammar of formal conferencing: large rectangles, prominent self-views, and a central stage occupied by whoever is speaking. That structure works for presentations, interviews, and lectures, but it can feel cumbersome during collaborative production. Around became known for a lighter visual approach in which participants could remain available around the work area rather than replacing it. Its use of compact video representations helped reduce the sense that every meeting was a performance.
This mattered in my own collaborative reviews because screen space was not an abstract concern. On a laptop, a large meeting window competes directly with the material under discussion. If I had to alternate constantly between the call and a prototype, I lost visual cues from colleagues each time I switched. A more compact meeting layer allowed the team to keep talking while examining the same artifact. The tool felt less like a destination and more like part of the working environment.
The design also addressed the fatigue associated with continuous self-monitoring. Traditional grids encourage participants to inspect their own lighting, posture, and reactions. Compact framing does not eliminate camera awareness, but it can lower its intensity. The result is a more casual atmosphere suited to brainstorming, pair work, and recurring team rituals. Around’s public positioning explicitly challenged the idea that meetings had to be soul-crushing, and its playful presentation supported that message without removing the practical controls expected from a work application.
For teams evaluating how that approach differed from conventional conferencing, www.around-com.com/ represented the product’s central idea clearly: video calls should support hybrid-remote collaboration rather than force the work to fit around the call. The site presented options to try the service with a Google account, download desktop or mobile software, or use supported browsers, making the model accessible across common working setups.
Platform coverage was an important part of that practicality. Around was offered for macOS and Windows, supported major browsers including Chrome, Safari, Edge, and Firefox, and had options for iOS and Android. A hybrid workflow becomes fragile when it assumes that every contributor owns the same hardware or can install the same desktop client. Browser access gives occasional guests a simpler route into a session, while native applications are useful for people who spend much of the day collaborating with the same team.
The service was also designed to accommodate more than formal project meetings. Its messaging referred to teams creating, collaborating, and celebrating together, and users publicly mentioned social sessions such as a Friday “campfire.” That broader purpose is relevant because distributed teams need informal contact as well as status updates. A lightweight call can support a quick design question in the morning and a casual team gathering later without making both occasions feel like scheduled corporate broadcasts.
I have seen playful elements work best when they are optional and secondary to the task. During a deadline review, nobody wants an interface that turns every action into entertainment. At the end of a sprint, however, a warmer and less formal environment can help people mark progress together. Around’s tone treated these modes as compatible. The same team could conduct focused collaborative work and then use the call as a space for celebration, rather than maintaining separate tools for every kind of interaction.
What Around Contributed to Miro’s Collaboration Vision
Around was acquired by Miro, a development that makes strategic sense when viewed through the product’s focus on shared work. Miro is associated with collaborative visual workspaces, while Around concentrated on the communication layer surrounding that work. One product helps participants manipulate ideas and artifacts together; the other was built to keep voice and human presence available without overwhelming the canvas. The acquisition connected two related parts of the same hybrid collaboration problem.
The most valuable lesson from Around is not that every meeting needs another video application. It is that meeting design should begin with the activity participants are trying to complete. If the goal is a presentation, a speaker-centered layout may be appropriate. If the goal is to sketch a customer journey, edit a concept, or resolve details in a prototype, the conversation should wrap around the shared object. Around’s interface and positioning consistently favored the second category.
This distinction can guide practical meeting setup even beyond a single product. Before a hybrid session, I now ask where the center of attention should be. If the answer is “the people,” as in an interview or sensitive one-on-one conversation, full video may be useful. If the answer is “the work,” I prioritize a shared canvas, equal audio access, and unobtrusive participant video. That decision prevents the conferencing interface from consuming space and attention that the task itself requires.
Around also demonstrated that inclusion can depend on acoustic details. Organizations often discuss hybrid equity in terms of policy, but a meeting becomes unequal very quickly when one participant hears an echo, misses quiet comments, or cannot identify speakers. No amount of facilitation language fully compensates for poor audio. By making simultaneous individual devices a core scenario rather than an edge case, the product targeted one of the most persistent technical barriers to equitable hybrid participation.
There are still operational habits that technology cannot replace. A facilitator should pause for remote responses, participants should avoid private side discussions, and important decisions should be captured in a shared space. Yet good software can make those habits easier to sustain. Clear personal audio reduces the need to repeat comments. Visible individual presence makes it easier to notice who has not spoken. A lightweight interface keeps attention on the material from which decisions are being made.
The enthusiastic user comments featured by Around repeatedly emphasized delight, improved meetings, and an unwillingness to return to older tools. Testimonials are subjective, but the pattern is informative. People were not praising a longer catalog of enterprise controls; they were responding to how the product felt during everyday work. Some highlighted equal participation and the absence of echo, while others focused on beauty, playfulness, and the sense that the software respected the humans using it.
That combination was Around’s strongest contribution. Technical audio processing handled a concrete constraint, compact visual design protected working space, and a playful tone reduced the stiffness of routine calls. None of these elements alone would have transformed hybrid collaboration. Together, they offered a coherent answer to a familiar problem: how can people in different locations share a conversation without forcing remote colleagues to occupy the edge of the room?
For practitioners, the enduring takeaway is to judge meeting tools by participation quality rather than by video sharpness or maximum room size alone. Watch who interrupts comfortably, who needs to repeat a point, and who can continue interacting with the shared artifact while speaking. Around earned attention because it treated these ordinary moments as the substance of collaboration. Its acquisition by Miro placed that philosophy within a broader effort to shape how distributed teams think, build, and make decisions together.
