A hybrid meeting can fail before anyone shares a screen. Put two teammates in the same room, add a third person joining remotely, and the people on site may start sharing one laptop to avoid audio feedback. They can hear each other naturally, but the remote teammate gets a distant microphone, a narrow camera view, and fewer chances to enter the conversation. Around was built around that problem. Its pitch was video calls for hybrid-remote teams that need to create, collaborate, and celebrate together, with particular attention to making a room full of people feel like one meeting rather than two separate groups.
The Meeting Problem Around Took On
Conventional video calls often treat each physical room as a single participant. That arrangement is convenient for the people sitting together but can make everyone else work harder. In a project review, someone at the end of a conference table may be hard to hear. A remote designer trying to respond to a quick exchange between two people on site may have to wait until the room pauses. Even when the connection is clear, the distribution of attention is uneven: the room has side conversations and body language, while the remote participant has a small window onto both.
Around’s stated answer was unusually direct: everyone could join from their own device, with all microphones on and no echo. The site described this as unique audio technology intended to make hybrid-remote meetings more inclusive. That is a more specific proposition than simply offering another place to start a video call. It targets the awkward choice teams otherwise face between individual participation and usable audio when several people are sitting close to one another.
Consider a planning session with two product managers in an office and an engineer at home. If the office pair share a device, the engineer hears them through one microphone and appears on one screen. If both managers join a typical call on separate laptops with speakers and microphones active, feedback can disrupt the meeting. Around’s no-echo claim was meant to remove that tradeoff: each person could have an individual presence in the call without forcing the colocated pair into a single seat. That distinction matters most in discussions where each person needs to speak, react, and refer to work on their own computer.
The site used settings such as a modern workspace, a hotel suite, and a startup house to illustrate hybrid participation. Those examples point to a practical reality: a team is not always gathered around purpose-built conference equipment. People may be working side by side at desks, meeting temporarily while traveling, or joining from an informal shared space. Around’s approach addressed those ordinary arrangements, where asking everyone to find a separate room would defeat the point of being together.
Built for Work, Not Just Attendance
Around described its calls as a way for teams to create, collaborate, and celebrate together. That range helps explain its emphasis on the experience of a meeting, not merely the ability to connect. A design critique, for example, has a different rhythm from a status update: people need to compare ideas, ask short questions, and respond while the work is still in view. A team gathering has another rhythm again. In both cases, a call that makes participants conscious of microphone management can pull attention away from the reason they met.
When I structure a hybrid review, I try to give each participant a clear way into the discussion rather than treating the people in the room as a single voice. Around’s device-per-person model fits that goal. It does not, by itself, guarantee an inclusive meeting; a facilitator still has to invite remote colleagues into decisions and stop side conversations from becoming the real discussion. What the product aimed to do was reduce one technical obstacle to that behavior. If colocated teammates can remain individually connected without echo, there is less pressure to sacrifice their separate participation for clean audio.
The public comments featured on Around’s site are useful as examples of how people understood the product, though they are testimonials rather than controlled evidence. One user described two people on site and one online having the same experience and a comparable “power of voice” in the discussion, without echo. Another characterized Around as video calling software for people who meet to get work done. A team also mentioned using it for a Friday campfire. Taken together, those accounts reflect the two sides of Around’s positioning: making mixed-location work sessions more equitable and leaving room for less formal team time.
That distinction is worth keeping in mind when assessing http://around-com.com/: Around’s defining claim was not that it replaced the need to plan a meeting, but that its call experience could better support teams whose members were both together and apart. For a manager deciding whether a tool fits a team, the useful test is therefore concrete. Have two people join from the same space on separate devices, bring in someone remote, and run an actual discussion. Listen for echo, but also watch who can interrupt politely, ask for clarification, and contribute without waiting for the room to hand them the floor.
Where and How Teams Could Join
Around’s site presented several ways to access the service. It listed downloads for macOS and Windows, browser use through Chrome, Safari, Edge, and Firefox, and options for iOS and Android. It also displayed a free-trial invitation, a Google account sign-in option, and navigation for login, sign-up, downloads, an introductory demo video, FAQs, and pricing. Those details matter because a hybrid call often includes people using different devices or joining from a place where their usual desktop setup is unavailable.
For a recurring team meeting, I would treat platform coverage as part of the setup rather than an afterthought. A desktop app may suit someone working all day at a workstation, while a browser option can be useful for a participant joining from another computer. Mobile availability can matter when a teammate is away from a desk. The site’s platform list indicates where Around intended people to join; it does not establish that every platform offered identical behavior, or that current downloads and sign-ins remain available under the same terms. Those are details to verify before making the service part of a team’s routine.
The same caution applies to pricing. The presence of a pricing page and a “try for free” invitation shows that Around offered a route for evaluation, but the supplied site information does not specify plan limits or current rates. A team considering the product for regular use would need to check the applicable terms rather than assume that a trial covers its meeting size, duration, or long-term needs. A short pilot with the actual group is more informative than a feature checklist when the central question is whether colocated and remote people can participate comfortably.
- Test the room arrangement: Put at least two participants near each other, each on a separate device, and include a remote colleague. That is the situation Around’s audio claim was designed to address.
- Use a real agenda: Run a review or decision meeting, not only a microphone check. Clear audio is valuable because it lets people do the work they came to do.
- Ask the remote participant first: Confirm whether they can hear each speaker distinctly and enter the conversation at a natural moment.
- Check each joining method you need: The site listed desktop, browser, and mobile options, but a team should validate its own device mix and current availability.
These checks also separate a product claim from a meeting outcome. “No echo” is something participants can listen for immediately. Equal participation takes longer to judge. In one meeting, the remote person may speak often because the facilitator makes space; in another, the same audio setup may coexist with a room-dominated discussion. Around’s design addressed the technology side of that divide. Teams still have to decide how they share attention, handle decisions, and include someone who is not physically present.
Around’s Place in Team Collaboration
Around’s identity extended beyond the mechanics of calling. Its site framed meetings as something that should not drain the people attending them, and described video calls for teams that make things together. The testimonials it highlighted likewise focused on the feel of using the software as well as the audio: users called it delightful, said they had moved their meetings to it, and described enjoying team time there. Those are subjective reactions, but they help explain why the product stood apart in its own presentation. Around was selling a less strained way to be present with coworkers, especially when “together” meant a mix of locations.
The site also stated that Around had been acquired by Miro to help shape the future of team collaboration. That is an important part of the project’s story, particularly for anyone encountering the Around name today. The acquisition statement connects the video-call product to a broader collaboration company, but it does not, on its own, say which Around features are currently maintained, how they may be incorporated into Miro, or whether an old download or account route still works. Those questions should be answered from current product information before a team changes its workflow.
The practical lesson of Around’s approach remains clear. In hybrid work, the hard part is not simply getting a camera feed from one place to another. It is letting people who share a physical space participate as individuals while giving remote colleagues a fair place in the same conversation. Around made that issue visible through a specific promise: separate devices, open microphones, and no echo. Whether evaluating Around itself or considering how to run a better mixed-location meeting, that is the standard worth testing against the everyday reality of a team at work.
