Around was designed around a specific criticism of conventional video meetings: the meeting window often dominates the screen even when participants are supposed to be working together on something else. Instead of treating every call like a formal presentation, the product positioned video as a lightweight collaboration layer for hybrid and remote teams. Its public messaging emphasized calls for people who want to create, discuss, and complete work together rather than spend the entire session watching a grid of faces.
That distinction matters when assessing whether Around fits a team’s habits. It was not presented merely as another way to reproduce a conference room online. The service focused on making video participants feel present without allowing large camera feeds to consume the workspace. This approach was particularly relevant to designers, developers, startup teams, and other groups whose meetings frequently revolve around shared documents, prototypes, whiteboards, or applications.
Around also became part of a larger collaboration strategy after being acquired by Miro. The acquisition was announced as a step toward shaping the future of team collaboration, linking Around’s experience in video communication with Miro’s broader focus on visual and distributed teamwork. Organizations considering the product should therefore understand both its original design principles and its place within Miro’s evolving product environment.
A Video Interface Built to Stay Out of the Work
Traditional video conferencing commonly asks users to choose between a large meeting interface and the materials they are discussing. Around took a different visual approach. Its compact video presentation was intended to preserve screen space, allowing participants to remain visible while continuing to use the software where the actual work was happening. The underlying idea was that video should provide social context and a sense of presence without becoming the central object of attention.
This model can be especially useful during collaborative production sessions. A product team may need to examine a design file, edit a specification, compare implementation details, or brainstorm while maintaining an open conversation. In such situations, an oversized gallery can compete with the content that participants need to see. Around’s interface sought to reduce that competition and make the call feel more like a companion to the work than a separate destination.
The product’s language also reflected a deliberate effort to reduce the emotional weight of online meetings. Around described its calls as a way for hybrid and remote teams to create, collaborate, and celebrate together, and its presentation included playful elements rather than relying exclusively on the restrained visual conventions of enterprise conferencing. Public user comments highlighted this sense of enjoyment, with some teams referring to informal virtual gatherings and others praising the product’s appearance and human-centered feel.
Those qualities do not automatically make the service suitable for every meeting. A compact, informal interface may be well matched to recurring teamwork, peer discussions, and co-working sessions, while a highly structured webinar or large external presentation can require a different set of controls and expectations. Before adoption, a team should identify its dominant meeting types and decide whether it wants video to be the main event or a supporting layer around shared work.
Platform access was broad in the service information published by Around. The product was offered for macOS and Windows, supported use through Chrome, Safari, Edge, and Firefox, and listed mobile availability for iOS and Android. It also provided Google account sign-in and promoted a free way to try the service. That range reduces some installation barriers, but organizations still need to test their actual mix of managed computers, browsers, mobile devices, identity policies, and security restrictions rather than relying only on a platform list.
Hybrid Audio Was Central to the Product’s Practical Case
One of Around’s most distinctive claims concerned hybrid meetings in which several people occupy the same physical room while remote colleagues join online. Conventional setups can create echo and feedback when multiple nearby laptops have active microphones. The usual response is to rely on one room device, but that arrangement can place remote participants at a disadvantage: people in the room share a collective camera and microphone while each remote attendee appears individually and may have less influence over the conversation.
Around promoted a different configuration in which everyone could use an individual device with microphones active, supported by audio technology intended to prevent echo. The goal was to give in-room and remote participants a more consistent experience and a more equal voice. A public user comment cited by the company described a meeting with two people on site and another online in which participants shared the same experience without echo. While such testimonials are not substitutes for technical testing, they illustrate the practical problem Around set out to solve.
The product page at http://around-com.com/ frames this capability as part of a broader effort to make hybrid-remote collaboration more inclusive, not simply as an audio convenience. If each participant joins independently, remote colleagues no longer have to interpret a distant conference-room view or compete with a group gathered around one microphone. Individual participation can make names, reactions, and speaking turns easier to follow, while preserving the social connection between people sharing a location.
Teams should nevertheless test the audio model under realistic conditions before standardizing on it. Room size, laptop placement, operating-system permissions, headset use, background noise, and network quality can all affect a live call. A successful trial should include the same kinds of spaces the organization actually uses, such as an open office, a startup house, a home workspace, or a temporary hotel setup. It should also involve both local and remote participants so that the evaluation does not reflect only the experience inside the room.
The phrase “everyone on their own device” has operational implications as well. Each participant needs a charged and compatible device, adequate connectivity, and permission to use the required microphone and camera. IT administrators may need to consider browser controls, application deployment, update procedures, and support for employees who move between office and remote settings. The concept is simple from a participant’s perspective, but reliable organization-wide use depends on these less visible conditions.
Meeting etiquette remains important even when software addresses echo. Participants still need conventions for interruptions, side conversations, notification sounds, and the use of speakers or headsets. Technology can reduce the imbalance between a room and a remote caller, but it cannot independently ensure that remote attendees are invited into decisions. Teams adopting Around’s model should pair the technical setup with facilitation practices that recognize every participant as an individual rather than treating remote colleagues as observers.
Acquisition, Workflow Fit, and the Questions to Resolve First
Around’s acquisition by Miro is a significant part of its current context. The companies described the move as a way to help shape the future of team collaboration. Strategically, the combination is understandable: Miro centers shared visual work, while Around was built to keep conversation close to the work without covering it. Both products address distributed teams, but from complementary directions—one through a collaborative canvas and the other through compact video and hybrid audio.
For prospective users, an acquisition can also make product planning more important. Features, account structures, integrations, branding, support arrangements, and standalone availability may evolve as technology is incorporated into a larger platform. A team should verify the current download options, service terms, privacy documentation, pricing, and account requirements at the time it plans to deploy. Historical praise for the original application explains its appeal, but deployment decisions should be based on present availability and supported workflows.
The public response collected by Around shows that the product gained a committed following among teams dissatisfied with conventional meeting software. Users described moving all their meetings to the service, praised its design, and emphasized that it felt built for people meeting to get work done. Other comments focused on the absence of echo and the ability to give on-site and online participants comparable influence. These statements indicate where the product resonated most strongly, although they remain individual experiences rather than controlled comparisons.
A useful evaluation should look beyond whether the first call feels novel or visually appealing. Teams should examine call stability, audio behavior, screen-space savings, ease of joining, mobile participation, and the handling of recurring collaboration sessions. They should also assess whether compact video helps concentration or makes certain participants too easy to overlook. The answer can differ by role: a designer working in a shared file may value an unobtrusive call, while a facilitator reading reactions during a sensitive discussion may prefer a more prominent gallery.
Security and governance deserve the same attention applied to any workplace communication tool. Organizations may need clarity about account ownership, employee onboarding and removal, data handling, access from personal devices, and compatibility with internal policies. The convenience of continuing with a Google account can simplify entry for some groups, but companies with centralized identity management should confirm whether the available authentication flow meets their requirements. Regulatory or contractual obligations may call for a formal review before client or confidential work is discussed.
Teams should also determine which existing tool Around would replace, if any. Its strongest use case may be reducing friction in collaborative work sessions, but organizations still need channels for asynchronous updates, formal presentations, customer calls, and documented decisions. Adding another meeting application without defining its role can increase confusion. A clearer approach is to assign it to specific situations—such as design critiques, remote pairing, hybrid stand-ups, or informal team gatherings—and compare the results with the current process.
The most relevant measure is not the number of visual effects or the novelty of the interface. It is whether participants can contribute with less friction while keeping attention on shared work. Around’s compact presence, cross-platform reach, playful tone, and echo-management concept were all directed toward that objective. Its popularity among creative and distributed teams followed from a coherent product argument: video collaboration does not have to imitate either a boardroom or a wall of television screens.
Before committing, organizations should run a representative pilot and document what changes. They should include co-located and remote employees, different operating systems, major supported browsers, and at least one mobile participant. They should observe who speaks, how often technical interruptions occur, whether the working material remains visible, and whether participants feel equally present. That evidence will provide a stronger basis for adoption than brand enthusiasm alone, while still testing the exact qualities that made Around distinctive in the first place.