Around was designed around a specific objection to conventional video conferencing: meetings should support the work instead of becoming the work. Its product messaging focused on video calls for hybrid and remote teams that need to create, collaborate, and celebrate together. That positioning matters because Around was not merely presented as another application for putting ten rectangular camera feeds into a grid. It attempted to reduce the visual weight, audio friction, and emotional fatigue associated with spending hours in online meetings.
The service attracted particular interest from startups, design groups, and distributed product teams. Public user comments praised it as software built for people who meet to accomplish a task, rather than for people whose main activity is attending a meeting. Other customers emphasized its playful character and said they had moved all of their meetings to the platform. Those reactions help explain the product’s appeal, but they should not be mistaken for controlled performance data. Testimonials are evidence of enthusiasm, not proof that every organization will obtain the same result.
There is also an important business fact to consider before evaluating Around as an independent long-term platform: the company was acquired by Miro. Around’s site states that the acquisition is intended to help shape the future of team collaboration. That creates a potentially strong strategic fit because Miro centers on collaborative visual work, while Around approached the communication layer surrounding that work. At the same time, an acquisition can affect product direction, account policies, integrations, support, and the availability of standalone applications. A team considering adoption should therefore verify the current product status rather than assuming that every historical feature or download remains unchanged.
The Product Was Built for Hybrid Participation
Around’s clearest differentiator was its treatment of hybrid meetings in which several people share one physical room while one or more colleagues join remotely. This is a harder problem than an entirely remote call. If three coworkers sit near one another with three laptops, ordinary conferencing software can produce feedback, echoes, and duplicated voices. The common workaround is to keep only one microphone active, but that turns one person’s laptop into the room’s audio gateway and often makes remote participants feel as though they are watching a group from the outside.
Around promoted a different model: everyone could remain on an individual device, with microphones on, without the echo normally expected from colocated laptops. Its messaging described unique audio technology intended to make hybrid participation more inclusive. In practical terms, separate devices can give each participant a distinct identity and a more equal presence in the conversation. A remote colleague does not have to address an indistinct conference-room group, while people in the room do not have to crowd around one computer.
The claimed benefit can be expressed numerically. In a six-person meeting with four people in one room and two working remotely, a one-laptop room setup may expose the remote participants to only three visible endpoints: two individuals and one combined group. If all six people can use their own devices successfully, the meeting instead has six identifiable endpoints. That does not automatically create equality, but it improves the structural conditions for equal turn-taking, reactions, and direct eye contact.
Audio performance should still be tested in the actual workplace. A hotel suite, startup house, modern open office, and acoustically treated meeting room present very different conditions. Distance between laptops, hard surfaces, speaker volume, network quality, and operating-system audio handling can all influence the result. Around’s no-echo proposition addresses a major source of hybrid friction, but no responsible buyer should infer that room acoustics and hardware quality cease to matter.
A useful pilot would include at least three scenarios: a fully remote call, a hybrid call with multiple laptops in one room, and a longer working session involving frequent conversation. A team can then measure reconnection incidents, noticeable echo events, requests to repeat speech, and the percentage of participants who speak. If a 45-minute conventional meeting produces eight audio interruptions and the Around test produces two, that is a 75% reduction. Even a simple count is more informative than choosing a platform solely because its interface feels fresh.
A Lighter Meeting Interface Can Change Work Behavior
Around framed itself as a tool for collaboration rather than a virtual boardroom. That distinction is more than branding. Traditional full-screen video grids compete with the document, design, codebase, or planning board that participants are supposed to examine. A communication layer that occupies less visual space can help the shared work remain central. This is especially relevant to product teams, which may need to inspect prototypes, write notes, or make decisions while continuing to see and hear one another.
The project page at https://www.around-com.com/ presents the service as radically different video calling for hybrid and remote teams, with an emphasis on creating together rather than simply appearing on camera. The available access options included desktop downloads for macOS and Windows, browser support for Chrome, Safari, Edge, and Firefox, and mobile availability for iOS and Android. The site also offered account access through Google and promoted a free way to try the product.
That platform coverage was broad enough to address many mixed-device teams. Counting the explicitly named options yields two desktop operating systems, four major browsers, and two mobile operating systems. However, eight named environments do not necessarily mean identical functionality in all eight. Browser permissions, mobile background behavior, screen sharing, microphone selection, and update schedules can vary. Before standardizing on the service, a company should test the exact combinations its employees use instead of treating a platform logo as a guarantee of feature parity.
The interface philosophy may also reduce one kind of meeting fatigue while introducing tradeoffs elsewhere. Lower visual prominence can be valuable during collaborative production, but some conversations depend on larger facial images. Interviews, sensitive employee discussions, customer research, and presentations to unfamiliar audiences may benefit from a more conventional view. The relevant question is not whether a lighter interface is universally better. It is whether the interface matches the dominant meeting type.
A quantitative assessment can make that judgment clearer. Suppose a product group spends 12 hours per employee each month in collaborative calls. If reducing meeting friction saves only three minutes per hour, the gain is 36 minutes per employee per month. Across 40 employees, that equals 24 staff-hours. The estimate does not prove that Around will create those savings, but it shows why small usability differences can matter at scale. Conversely, if employees lose five minutes per week dealing with compatibility issues, some of the benefit disappears. Both sides should be measured.
The public reactions quoted by the company consistently emphasized delight, beauty, and the difficulty of returning to other meeting tools after using Around. One hybrid user specifically highlighted equal conversational power for two people on site and one online, along with the absence of echo. Another described Friday team gatherings conducted through the product. These examples suggest that Around supported both task-oriented sessions and social rituals. They also reveal its intended emotional effect: calls were supposed to feel less formal and less draining.
Check Product Continuity, Fit, and Measurable Outcomes
The Miro acquisition is the most important context for a present-day decision. Strategically, the combination makes sense. A visual collaboration platform benefits from integrated conversation, and a video tool benefits from being close to the canvas where teams organize ideas. Yet buyers should distinguish strategic potential from currently documented service terms. Before moving recurring meetings, they should confirm whether new accounts can be created, which applications are actively maintained, how authentication works, and whether Around functions as a standalone product, an integrated experience, or a technology being absorbed into a broader platform.
Pricing also requires current verification. The historical site encouraged users to try the service for free, but that statement alone does not establish today’s plan limits, enterprise terms, participant caps, retention policies, or administrative controls. A free entry point is useful for a pilot, not a substitute for procurement review. Organizations handling customer information or regulated material should additionally examine security documentation, data-processing terms, recording behavior, account management, and employee offboarding procedures before operational use.
A focused trial is more valuable than a broad but vague rollout. For two weeks, a team could compare Around with its existing platform across 15 to 20 meetings. Useful measurements include average join time, audio incidents per call, percentage of participants who contribute verbally, participant ratings after the meeting, and the time spent switching between the call and the work surface. Separating hybrid sessions from fully remote sessions is essential because Around’s audio proposition is most distinctive when several active devices occupy the same room.
Teams should also define a stopping rule in advance. For example, adoption might require at least a 25% reduction in reported audio problems, no critical incompatibility for more than 5% of users, and an average experience score at least one point higher on a ten-point scale. These thresholds are illustrative, but preselecting them prevents novelty from dominating the decision. Playful design can improve morale, yet reliable access and clear product continuity remain nonnegotiable.
Around’s central idea remains compelling: hybrid meetings should not force colocated people to merge into one room endpoint while remote colleagues appear as separate individuals. Giving everyone a personal device, an active microphone, and a comparable presence attacks a genuine inclusion problem. The product also recognized that video should sit beside collaborative work rather than overwhelm it. Those principles explain why extraordinary teams responded so positively to the service.
The final decision, however, should rest on present facts and measured performance. Around deserves attention for its unconventional interface, hybrid-audio approach, wide stated platform coverage, and connection to Miro’s collaboration strategy. It should not be selected only because historical users loved it or because its design feels more human than a standard video grid. Verify current availability, run realistic colocated tests, compare quantified outcomes, and confirm that the post-acquisition product direction fits the organization’s time horizon. That is the difference between appreciating an inventive meeting experience and depending on it responsibly.
Comentarios recientes