Most hybrid-meeting setups begin with a familiar assumption: everyone in the office should share one conference-room camera and microphone. Around challenged that model by encouraging each participant to join from an individual computer, even when several people were sitting in the same room. Its audio technology was designed to keep all microphones active without producing the disruptive echo normally associated with nearby devices.
That difference explains the central idea behind Around, the video-calling product presented through around-com.com. The service was not positioned as another conventional platform for placing a large speaker window at the center of your screen. It focused on helping hybrid and remote teams create, collaborate, and celebrate while reducing the fatigue, hierarchy, and technical friction that can make online meetings unpleasant.
The approach attracted teams that wanted video communication to feel like part of their workspace rather than a separate digital ceremony. Around offered access through macOS and Windows applications, major desktop browsers including Chrome, Safari, Edge, and Firefox, and mobile devices running iOS or Android. The project was later acquired by Miro, connecting its meeting philosophy with a broader vision for collaborative work.
Why Around Treated Hybrid Audio as an Inclusion Problem
A standard hybrid meeting usually creates two very different experiences. People in the room can exchange glances, hear side comments, and speak naturally. Remote participants see a wide shot of the room, struggle to identify speakers, and may have to interrupt more forcefully to enter the discussion. Even when the technology works as intended, the meeting can give the people gathered physically more influence than those joining from elsewhere.
Around’s device-per-person model addressed this imbalance. When every participant joins from a laptop, each person receives an individual presence in the call. A remote colleague is no longer represented by one large screen at the end of a conference table while the office group blends into a distant background. The meeting interface can present participants more consistently, which supports a more equal sense of presence.
Ordinarily, opening several microphones in the same room causes feedback, duplicated voices, or delayed echoes. The practical response is often to mute most devices and rely on a shared room microphone. Around promoted unique audio technology intended to make simultaneous local devices usable with their microphones on and without echo. That capability was especially relevant in startup houses, modern shared workspaces, hotel suites, and other locations that lacked a purpose-built conference room.
This design choice matters because inclusion depends on more than giving everyone permission to speak. Participants also need comparable access to the conversation. If an office employee can talk naturally while a remote employee must search for the unmute button, wait for a pause, and compete with room noise, the nominally equal meeting still contains a structural disadvantage. Around attempted to reduce that disadvantage at the technical layer.
The product’s public reception reflected this practical appeal. Users described moving their meetings to Around, praised its suitability for people who meet to complete real work, and highlighted situations in which on-site and online participants had a similar experience. Other reactions emphasized the software’s visual quality and sense of play. Those comments are useful signals because they point to two connected goals: reliable collaboration and a meeting environment that does not feel emotionally draining.
You should nevertheless evaluate the audio model in the context of your own workspace. A quiet design studio, an open office, and a temporary hotel work area create different acoustic conditions. Device quality, network stability, room size, and participant behavior can still affect a call. Echo management can remove a major obstacle, but it cannot compensate for every source of noise or an unreliable internet connection.
How to Evaluate Around for Real Teamwork
The best way to assess this product is not to compare feature tables in isolation. Run the types of sessions your team actually holds: design critiques, planning meetings, daily coordination, remote workshops, and informal celebrations. Around was explicitly presented as a tool for teams that create and collaborate together, so your test should measure whether it improves active work rather than merely delivering acceptable video.
When you review around-com.com, pay particular attention to the project’s hybrid-first assumptions, supported platforms, download options, and stated acquisition by Miro. These details help you distinguish the original Around experience from generic video conferencing and understand how its collaboration ideas may relate to Miro’s evolving product ecosystem.
A disciplined pilot can reveal whether the device-per-person approach fits your team. Use a mixed group rather than testing only with fully remote participants. Include at least two people in the same physical room, one or more remote colleagues, and a facilitator responsible for observing participation. Then repeat the session with your existing meeting setup so that you have a meaningful comparison.
- Choose a collaborative task. Ask the group to make a decision, review visual work, or solve a concrete problem. A passive presentation will not adequately test whether participants can enter the conversation and work together.
- Have everyone join individually. Let colocated participants use their own computers and microphones as the product intends. Avoid falling back immediately to one shared conference-room device, because that would remove the central benefit you are evaluating.
- Test supported environments. Include the macOS or Windows application where appropriate, but also check the browsers your organization permits. Around listed support for Chrome, Safari, Edge, and Firefox, while iOS and Android options covered mobile participation.
- Observe the room acoustics. Listen for echo, duplicated speech, clipping, and changes in volume as different people talk. Also note whether participants feel comfortable leaving their microphones active rather than repeatedly muting and unmuting.
- Measure participation balance. Record whether remote colleagues speak as often as colocated participants, whether interruptions decrease, and whether the facilitator needs to invite remote attendees into the discussion.
- Evaluate workspace impact. Determine whether the interface stays out of the way of the documents, boards, or creative tools being used. Around’s value proposition centered on getting work done, so the call should support the task instead of dominating the screen.
- Collect emotional as well as technical feedback. Ask whether the meeting felt tiring, formal, playful, focused, or inclusive. The product deliberately emphasized that meetings should not crush morale, making comfort a relevant performance criterion rather than a superficial preference.
You should also separate novelty from sustained value. A visually distinctive interface can improve first impressions, but your decision should depend on repeated sessions. Run the pilot over several weeks and include meetings of different lengths. If participants remain engaged, remote employees report stronger access to discussion, and the team experiences fewer audio problems, the design is producing an operational benefit rather than a temporary sense of freshness.
For security-conscious organizations, platform fit is only one part of the assessment. You should review the current service terms, identity and login options, administrative controls, data-handling practices, and any policies required by your company before broad deployment. The site presented a free trial path and continuation through a Google account, but authentication convenience should be considered alongside your organization’s governance requirements.
What the Miro Acquisition Means for Prospective Users
Around’s acquisition by Miro is significant because both products revolve around distributed collaboration, although they began from different interaction layers. Around concentrated on the live human presence of a meeting: seeing teammates, speaking naturally, and maintaining inclusion across physical locations. Miro became known for a shared visual workspace in which teams can plan, map ideas, facilitate workshops, and organize project information.
Bringing those perspectives together suggests a direction in which conversation and collaborative content become less fragmented. In many remote workflows, participants constantly switch between a video-call window and the canvas, document, or application where the work is happening. Around’s less dominant approach to video was compatible with the idea that the shared work should remain central. Miro’s acquisition therefore makes strategic sense as an effort to shape the future of team collaboration rather than treating video as an isolated utility.
However, an acquisition can change packaging, availability, support, and product roadmaps. You should not assume that every feature, platform option, or standalone workflow described during Around’s earlier life will remain unchanged indefinitely. Confirm the current download path and service status before establishing a long-term internal standard, especially if your processes depend on a specific desktop application or browser behavior.
For existing users, the most valuable lesson may be broader than the fate of one application. Around demonstrated that hybrid meetings do not have to copy the conference-room model. A team can instead design participation around individuals, allow people in the same location to retain separate digital identities, and use audio processing to prevent proximity from becoming a technical problem.
If you are responsible for collaboration strategy, apply that principle to every meeting tool you assess. Ask whether the product gives remote and colocated employees comparable visibility, speaking power, and access to shared materials. Examine whether video supports the work or competes with it. Finally, consider whether the experience encourages people to collaborate naturally enough that they can focus on decisions and creative output instead of managing the call.
Around’s strongest contribution was not simply another way to make a video call. It was a concrete response to a recurring hybrid-work contradiction: people may occupy different physical environments, yet they still need to feel equally present in one working session. By combining individual-device participation, echo-resistant audio, broad platform access, and a more playful product character, Around offered an alternative to meeting software built primarily around formal presentations and conference rooms.
That makes the project relevant even as it enters the next stage under Miro. You should evaluate it through the outcomes it was designed to improve: balanced participation, comfortable communication, reduced audio friction, and the ability to keep collaborative work at the center of the screen. Those criteria provide a practical standard for deciding whether Around’s distinctive meeting model belongs in your team’s workflow.