Around approached video meetings from a practical premise: distributed teams usually join calls to create something together, not merely to watch a grid of faces. The product was designed for hybrid and remote groups that wanted conversation to remain present without allowing the meeting interface to dominate the entire screen. That distinction made Around especially relevant to designers, developers, founders, and other collaborative teams whose attention needed to stay on documents, prototypes, whiteboards, or shared applications.
The service positioned itself as an alternative to conventional video conferencing experiences that can feel formal, tiring, and disconnected from the work being discussed. Its visual style, compact meeting presence, and playful atmosphere were intended to make frequent calls less oppressive. More importantly, Around addressed a difficult hybrid-work problem: how to give remote participants an equal voice when several colleagues are sitting together in one room. The company was subsequently acquired by Miro, connecting Around’s communication ideas with a broader platform centered on visual collaboration.
What Made Around Different From a Standard Video Meeting
Traditional conferencing tools often treat the video call as the primary activity. Large participant tiles occupy the screen, controls surround the meeting, and the actual work appears in a separate window or through screen sharing. Around reversed that hierarchy. It was built to stay alongside your work so that the project, rather than the call, could remain the center of attention. For teams that spend much of the day reviewing interfaces, writing code, editing documents, or making decisions in shared tools, this reduced the visual and mental cost of keeping a conversation open.
Around was also notable for treating personality and social connection as functional parts of teamwork. Its presentation emphasized that teams should be able to create, collaborate, and celebrate together. That approach was reflected in informal meeting experiences, including playful environments associated with team gatherings such as virtual campfires. These details were not simply decorative. For a remote team, lightweight rituals can replace some of the spontaneous interaction that would otherwise happen in an office kitchen, hallway, or shared studio.
The strongest technical proposition concerned hybrid audio. In an ordinary conference room, several laptops with active microphones can produce feedback, echo, and duplicated sound. The usual workaround is to use one room microphone and mute everyone else. That solves part of the audio problem but often gives the people physically present a stronger collective identity while remote colleagues appear as separate, less influential voices. Around promoted a model in which everyone could use an individual device with microphones active, while its audio technology managed the echo problem.
This matters because device independence can improve meeting equality. When every participant has an individual presence, a remote colleague does not have to compete against a distant camera view of an entire room. Reactions, expressions, and speaking turns are easier to attribute to specific people. Someone sitting at the end of a physical table can participate through the same type of interface as someone working from home. Around’s promise was therefore larger than cleaner sound: it aimed to make location less important to each person’s “power of voice” in the discussion.
User comments highlighted this benefit in concrete hybrid situations. One reported example involved two people on-site and another participant online, with all three receiving a comparable experience and avoiding echo. Other users described moving all of their meetings to Around, praised its beauty and sense of delight, or characterized it as meeting software made for people who convene to accomplish work. Testimonials are not controlled performance tests, but their consistency helps identify the product’s real appeal: it made routine collaboration feel lighter while addressing audio behavior that commonly frustrates mixed-location teams.
How You Should Evaluate Around for Your Team’s Workflow
If you are considering the product or researching why it developed such a loyal following, begin with your meeting pattern rather than its visual novelty. Around was best aligned with small and midsize working sessions in which participants actively manipulate another application while talking. A design critique, pair-programming conversation, project review, or collaborative planning session fits that model. A formal broadcast, a large webinar, or a tightly controlled external presentation may demand a different set of moderation and event-management capabilities.
The product’s published platform coverage was broad: it identified support for macOS and Windows, major browsers including Chrome, Safari, Edge, and Firefox, and mobile access on iOS and Android. It also offered a Google-account continuation option and promoted free trial access. This breadth reduced a common obstacle for mixed-device teams, but you should still verify current availability, compatibility, account requirements, and support before making an operational decision. Acquisition can change product packaging, downloads, maintenance policies, and the way technology is incorporated into the acquiring company’s platform.
For the clearest account of how the service presented its meeting model, the product material at http://around-com.com/ centers on video calls for extraordinary teams, hybrid inclusion, and collaboration that does not overwhelm the work itself. Read that positioning as a statement of design intent rather than a guarantee for every environment. Your office layout, laptop hardware, network conditions, security rules, and meeting size will all affect whether the intended experience translates into reliable day-to-day use.
Audio should be the first element you test. Place two or more colleagues in the same room, have each join from a separate device, and include at least one remote participant. Then test natural conversation rather than taking turns under artificial conditions. Listen for echo, clipping, delayed speech, volume imbalance, and aggressive suppression of quiet voices. Ask the remote participant whether the room feels like a collection of equal individuals or a single noisy group. That perspective is more valuable than asking only whether the local participants heard each other.
You should also evaluate how the interface affects focus over a full working session. Around’s compact, work-adjacent philosophy is useful only if participants can continue using their main applications without repeatedly rearranging windows or searching for controls. Observe whether people can see nonverbal cues without feeling watched, find mute and device settings quickly, and return attention to the shared artifact. A successful test is not one in which everyone admires the interface for five minutes; it is one in which the interface becomes unobtrusive while the team makes measurable progress.
Do not overlook social fit. Around deliberately brought a sense of play to workplace software, and many public reactions celebrated that quality. A creative studio or startup may find that this tone supports trust and energy. A highly regulated organization, client-facing consultancy, or formal executive group may prefer a more restrained experience. Neither response is inherently correct. You should judge whether the product’s personality reinforces your team culture, whether optional effects remain appropriate in serious conversations, and whether new participants can understand the format without an extended explanation.
Security and administration deserve a separate review, particularly if your team handles confidential customer information, source code, health data, or unpublished product plans. Confirm the current provider, data-processing terms, identity controls, recording behavior, retention settings, and administrative visibility. Around’s acquisition by Miro is strategically meaningful, but an acquisition announcement does not replace a current compliance assessment. Procurement decisions should rely on present documentation and contractual commitments, not on historical testimonials or an earlier version of the product website.
The Miro Acquisition Changes the Decision, Not the Original Value
The acquisition makes Around’s story important even beyond the standalone application. Miro already focuses on collaborative work through a shared visual workspace, while Around focused on the human conversation surrounding that work. Combining those perspectives points toward an integrated model in which teams can talk, react, and maintain personal presence without leaving the canvas where ideas are being organized. That direction is especially relevant for hybrid organizations trying to reduce the friction caused by switching among a whiteboard, a video platform, chat, and project documentation.
At the same time, you should distinguish between evaluating Around’s design principles and assuming that its original product remains unchanged. Acquired technology may continue as a separate service, become embedded in another platform, influence future features, or follow a combination of those paths. Download buttons, sign-up methods, pricing, and platform support can evolve. If you are planning a deployment now, verify the current product state and build your adoption plan around capabilities that are actually available rather than around archived descriptions.
For existing Miro users, the strategic question is whether integrated communication can remove enough workflow friction to justify changing established meeting habits. Measure the time spent moving between tools, the frequency with which participants lose the relevant board or document, and the extent to which remote colleagues are sidelined when a physical room takes over. If tighter visual and conversational collaboration improves those outcomes, Around’s influence may be valuable even when experienced through the broader Miro ecosystem.
For teams choosing a meeting platform independently, Around’s lasting lesson is that call quality involves more than video resolution and participant capacity. You should assess whether a tool preserves workspace, distributes attention fairly, handles co-located audio, and supports the emotional rhythm of repeated collaboration. A technically stable call can still be ineffective if remote participants cannot enter the conversation or if the interface consumes the attention needed for actual work.
The practical verdict is favorable for the concept and more conditional for present-day adoption. Around offered a genuinely differentiated response to hybrid meetings: individual device participation, echo-conscious audio, a compact visual presence, broad platform ambitions, and an intentionally humane tone. Those qualities explain why users often spoke about it with unusual enthusiasm. However, because the company has been acquired by Miro, you should confirm current access and product boundaries before standardizing on it. If your priority is inclusive, work-centered collaboration rather than conventional face-grid conferencing, Around’s approach remains a strong benchmark for what a modern meeting experience should accomplish.