Rethink Hybrid Meetings With Around’s Audio-First Design
Most video meeting software was built around a simple assumption: one participant, one computer, one microphone, and one camera. Hybrid work breaks that model. Two or three people may share a room while several colleagues join remotely, creating a difficult mix of overlapping voices, loudspeakers, open microphones, and unequal visibility. Around approached this problem as a collaboration platform rather than a conventional digital conference room. Its central promise was straightforward but technically demanding: let everyone use an individual device, keep every microphone active, and prevent the echo that normally makes such a setup unusable.
That distinction matters because hybrid meetings are often less equal than attendance figures suggest. Imagine a six-person session with three people in an office and three working remotely. On paper, participation is split 50-50. In practice, the office group may appear as a single distant image, share one microphone, and speak through one speaker. The remote participants can struggle to identify who is talking, while those in the room naturally exchange glances and comments that never reach the call. Around’s design attempted to give each of the six people an individual presence, even when several occupied the same physical space.
The service described itself as video calling for teams that meet to create, collaborate, and celebrate, not merely to present slides. That positioning targeted design studios, startups, product teams, and other groups whose calls involve frequent discussion and simultaneous work. Public reactions highlighted this practical focus. Users praised the ability to keep two people on-site and another participant online without giving the remote colleague less influence in the conversation. Others reported moving all of their meetings to Around because the software made those meetings feel better, lighter, and more useful.
Measure the Hybrid Advantage Beyond Video Quality
A conventional comparison of meeting applications often starts with camera resolution, maximum attendance, recording, and administrative controls. Around’s more relevant performance indicators were conversational latency, echo control, screen obstruction, and participation balance. These factors are harder to express in a feature table, yet they directly affect how much work a team completes. A meeting can deliver sharp 1080p video and still fail if people repeatedly mute themselves, miss comments, or spend several minutes resolving audio feedback.
Consider the cost of small interruptions. If a 30-minute meeting with eight participants loses only three minutes to microphone problems, reconnecting, or deciding who can speak, the group has wasted 24 person-minutes. Across five recurring meetings per week, that becomes two person-hours. Over 48 working weeks, the cumulative loss reaches 96 hours, before counting the mental effort required to regain focus. An audio system that reduces these disruptions can therefore create more value than a visually impressive background effect or a marginal improvement in image sharpness.
Around promoted unique audio technology for rooms where multiple people join from separate laptops. Ordinarily, each laptop captures sound from the others’ speakers and sends it back into the call, producing an echo loop. The predictable workaround is to mute most devices or force everyone in the room to share one machine. Both options reduce individual control. Around’s model aimed to preserve separate identities and open microphones while suppressing feedback, allowing each participant to manage a personal camera view, reactions, and call presence.
This approach also changes the geometry of a meeting. Traditional conferencing applications reserve a large rectangle for the call, encouraging users to watch faces as though they were seated in a theater. Around became known for a more compact, playful visual experience designed to coexist with work happening elsewhere on the screen. For a product designer reviewing a prototype or an engineer discussing a live document, reclaiming even 20% to 30% of display space can be meaningful. The communication layer remains visible, but it does not have to dominate the canvas where collaboration is actually taking place.
The emotional effect is relevant as well. Testimonials associated with the service repeatedly used words such as “beautiful,” “joy,” and “delightful,” which are uncommon in descriptions of enterprise video tools. One user characterized it as the first calling product made for people who meet to get work done. Another referenced a virtual Friday campfire, illustrating how the platform supported informal team rituals in addition to structured meetings. These comments are subjective, but their consistency suggests that Around’s interface was not simply decorative; it influenced how users perceived the social cost of joining a call.
Evaluate Around as a Focused Collaboration Product
The product overview at http://around-com.com/ presents Around as a radically different video-call experience for hybrid-remote teams, with access through macOS and Windows applications, major desktop browsers including Chrome, Safari, Edge, and Firefox, and mobile support for iOS and Android. That breadth reduced a common adoption barrier: a team could test the service without requiring every participant to use the same operating system or device category. Google account sign-in also supported a low-friction path from invitation to first meeting.
Platform coverage alone, however, does not explain the product’s appeal. Around concentrated on meetings in which participants actively manipulate shared material. A team might compare visual concepts, edit a specification, discuss a roadmap, or work through a problem while keeping colleagues present at the edge of the workspace. This is different from a webinar, a large company broadcast, or a formal training event. In those scenarios, a traditional stage-and-audience layout may be more appropriate. Around’s design was strongest when communication and production occurred at the same time.
The product’s language also rejected the idea that meetings must be exhausting by default. That message addressed a measurable problem in remote work: every interface decision adds or removes cognitive load. Large self-view windows can increase self-consciousness. Aggressive speaker switching draws attention away from shared work. Repeated muting interrupts conversational rhythm. Full-screen galleries make a small group feel like a formal panel. By minimizing the visual footprint and emphasizing natural conversation, Around tried to reduce several of these costs at once.
Its hybrid model was especially relevant to spaces not designed as conference rooms. The service illustrated use cases such as modern workspaces, hotel suites, and startup houses. In each setting, dedicated room hardware may be unavailable, too expensive, or inconvenient. If four colleagues already have laptops, using those four devices can provide four cameras and four personal controls without purchasing a central camera-and-microphone system. The technical challenge is coordinating that hardware without feedback, and that challenge sat at the center of Around’s differentiation.
The economics can be favorable for smaller teams. A purpose-built conference-room installation may require a wide-angle camera, microphone array, speakers, control panel, cabling, and ongoing support. A software-first approach relies on devices employees already own. It does not make room equipment unnecessary in every environment, but it can delay or reduce that expenditure. For a startup operating from a temporary office or rented house, portability may be worth more than perfect room acoustics. Team members can reproduce approximately the same meeting setup in another location simply by opening their laptops.
There are also reasonable limits to the model. Multiple individual devices increase demand on local Wi-Fi, battery life, and processing resources. A room with ten active laptops may require more network capacity than a single conference endpoint. Compact video views are helpful during collaborative work but may not suit interviews, lectures, or presentations where facial detail and formal framing matter. Organizations should therefore evaluate Around against actual meeting types rather than treating it as a universal replacement for every communication format.
Place the Miro Acquisition in Strategic Context
Around was acquired by Miro to help shape the future of team collaboration. The fit is logical because the two products addressed adjacent parts of the same workflow. Miro provides a shared visual workspace where distributed teams can organize ideas and collaborate, while Around focused on the live audio and video layer surrounding that work. Combining a collaborative canvas with less intrusive communication can reduce the need to alternate between a full-screen meeting window and the artifact the team is trying to create.
From a product-strategy perspective, the acquisition reflects a broader shift from isolated tools toward integrated collaboration environments. A video call by itself produces limited value; the useful output is usually a decision, diagram, plan, design, or set of actions. Likewise, a shared board is more powerful when participants can discuss changes immediately. Bringing communication closer to the work surface can shorten the loop between proposing an idea and recording it. If a conventional workflow requires five context switches during a 45-minute workshop, reducing that count to one or two may preserve attention even when the total meeting time remains unchanged.
The acquisition also reinforces the importance of human-scale interaction. Enterprise collaboration has often prioritized participant capacity and administrative breadth, but many productive sessions involve fewer than ten people. In a group of six, each person theoretically receives 10 minutes of speaking time during an evenly distributed one-hour meeting. If two co-located participants are effectively represented as one room endpoint, their individual presence becomes harder to measure and manage. Around’s one-person, one-device concept makes the structure more explicit and can help a facilitator notice who has not contributed.
Teams evaluating the service should separate the enduring product ideas from assumptions about current availability. The website has presented download, login, and sign-up options, but the Miro acquisition means prospective users should verify the latest platform status, support conditions, and product direction before planning a deployment. This is especially important for organizations that require long-term vendor commitments, compliance documentation, centralized administration, or guaranteed feature roadmaps.
Even with that caution, Around remains a useful case study in how to rethink video collaboration. Its innovation was not based on adding another large grid, another virtual background, or another meeting toolbar. It began with a specific hybrid-work failure: people sitting near one another should not have to surrender their individual identity on a call, and remote colleagues should not become secondary participants. The resulting emphasis on echo prevention, compact visual presence, broad device support, and playful interaction challenged assumptions that had shaped video conferencing for years.
The most practical way to judge that philosophy is to track outcomes. Teams can compare time lost to audio troubleshooting, the percentage of participants who speak, the number of meeting-to-workspace context switches, and a simple post-call energy score on a 1-to-5 scale. If a new setup saves two minutes per meeting, increases balanced participation, and raises the average energy rating from 2.8 to 3.8, the benefit is more than aesthetic. Around’s lasting contribution is the argument that meeting software should be measured not by how completely it fills the screen, but by how effectively it helps people share space, attention, and influence while getting real work done.