Most video conferencing products were designed around a familiar assumption: every participant should occupy a large rectangular tile, while the meeting itself becomes the center of the screen. Around challenged that model. The service presented video calling as a lightweight collaboration layer for hybrid and remote teams—especially teams that need to keep working in other applications while they talk.
That distinction matters because a productive call is not always a presentation. Designers may review a prototype, engineers may inspect a shared build, and project managers may update a planning board. In each case, the work artifact deserves more screen space than a gallery of faces. Around’s interface and positioning emphasized calls that accompany work instead of interrupting it.
The product also addressed a difficult hybrid scenario: several people are physically together while one or more colleagues join remotely. Conventional conferencing systems often force the people in the room to share one camera and microphone. Around promoted a different arrangement in which everyone could use an individual device, keep microphones active, and participate without the echo normally associated with several nearby laptops.
A Video Meeting Designed to Stay Out of the Way
Around’s core idea can be understood as an interface decision with operational consequences. Large meeting windows claim attention even when participants need to examine documents, code, mockups, or dashboards. A more compact visual presence reduces that competition. Faces remain available for social context, but they no longer consume most of the display.
For a team member using a 13-inch laptop, the difference is practical rather than cosmetic. A conventional grid can take nearly 100% of the useful workspace when maximized. If participant video is reduced to small, movable elements, the primary application can retain most of the screen. That can eliminate repeated switching among a call window, a browser, a design tool, and team messaging.
The service described its calls as radically different and focused on helping hybrid-remote teams create, collaborate, and celebrate together. The wording reflects a wider goal than simply transmitting audio and video. Around treated the emotional quality of meetings—whether a call feels heavy, playful, inclusive, or exhausting—as part of product design.
- Compact visual presence: participant video was intended to coexist with active work rather than replace it.
- Collaboration-first positioning: the product targeted people meeting to complete tasks, not only to watch presentations.
- Hybrid participation: individuals in the same room could join from their own devices instead of gathering around one conference computer.
- Cross-device access: the site listed macOS, Windows, major desktop browsers, iOS, and Android.
- Playful team culture: the product’s presentation included social and celebratory use cases alongside formal teamwork.
This combination made Around especially relevant to small and midsize creative or technical groups. Such teams frequently move between concentrated individual work and brief collaborative exchanges. A tool that minimizes meeting overhead can fit that rhythm better than software modeled primarily on conference rooms, webinars, and scheduled presentations.
Why Individual Devices Change the Hybrid Meeting Equation
The hardest hybrid meetings often involve an uneven distribution of people. Imagine that two colleagues are in one office and a third is remote. With a traditional room setup, the remote participant sees a wide camera view, may struggle to identify who is speaking, and can have less conversational influence. Meanwhile, the colocated participants naturally look at each other rather than at the camera.
Putting all three people on separate devices can improve visual equality, but it creates another problem: audio feedback. Several open microphones in one room can capture the same voices at slightly different times. Speakers may then reproduce those signals, creating echo or a distracting loop. Around made its audio approach central to the product, presenting the ability to keep nearby devices connected with their microphones on and without echo as a defining hybrid-work feature.
The benefit is not merely cleaner sound. Individual connections can give every participant a comparable identity in the call. Instead of representing three office workers through one shared tile while a remote worker receives a dedicated tile, the interface can represent all four people separately. That does not erase every social imbalance, but it reduces one obvious structural difference.
A useful way to evaluate this model is to track participation rather than only technical quality. Over five meetings, a team can count how many times each person speaks, how often remote participants are interrupted, and how long it takes them to enter a discussion. If individual-device participation lowers interruptions or narrows large speaking-time gaps, the audio and interface design is producing a measurable inclusion benefit.
Assess Around as a Working Environment, Not Just a Calling Tool
Product evaluations often focus on resolution, participant limits, or whether screen sharing exists. Those criteria are necessary, but they do not fully capture Around’s proposition. The more revealing question is whether a call supports uninterrupted work. The product should therefore be tested while participants perform genuine collaborative tasks, not in an empty demonstration meeting.
Teams evaluating the experience associated with https://around-com.com/ should compare it with their existing meeting workflow under the same conditions: identical participants, similar duration, the same work artifact, and a comparable mix of remote and colocated people. A controlled comparison provides better evidence than impressions formed from two unrelated calls.
- Select a repeatable task. Use a 30- to 45-minute design critique, sprint-planning session, or document review that the team already understands.
- Record interaction costs. Count window switches, requests to repeat audio, interruptions, and minutes lost to setup or troubleshooting.
- Test the difficult room arrangement. Include at least two people in one physical space and one participant joining remotely.
- Measure participation balance. Estimate speaking time by participant and note whether remote colleagues can enter the conversation naturally.
- Collect a short rating. Ask each person to score focus, audio comfort, inclusion, and fatigue from 1 to 5 immediately after the meeting.
Even a small test can expose meaningful differences. Suppose a five-person team runs two comparable 40-minute sessions. If the conventional tool produces six audio disruptions and the alternative produces two, that is a 67% reduction in observed incidents for that sample. The result is not a universal benchmark, but it is actionable evidence for that team. Likewise, saving three minutes of window management per weekly meeting amounts to roughly 2.6 hours per participant over 52 weeks.
Qualitative reactions matter as well because meeting software affects behavior. Public comments highlighted delight, ease, a sense of play, and suitability for getting work done. Other users described moving their meetings to Around or preferring it to familiar conferencing platforms. Testimonials are not controlled research, yet the consistency of those themes supports the idea that the product differentiated itself through experience rather than through a longer checklist of conventional meeting features.
Platform Coverage Reduced the Cost of Joining
A collaboration product becomes difficult to standardize if it excludes part of a mixed-device team. Around’s site listed native support for macOS and Windows, browser access through Chrome, Safari, Edge, and Firefox, and mobile availability for iOS and Android. That coverage spans the principal desktop, browser, and mobile environments used by modern teams.
The service also offered account entry through Google, alongside login, sign-up, and download options. For organizations already using Google identities, that path could reduce initial friction. Fewer account-creation steps can make a noticeable difference when guests, contractors, or new employees need to enter a call quickly.
Platform breadth should still be evaluated in context. Browser participation may be convenient for occasional guests, while a native application may offer a more integrated experience for frequent users. Mobile access is useful for joining in transit or away from a desk, but it should not be assumed to reproduce every desktop workflow. A realistic rollout plan identifies the primary client for daily use and treats the other platforms as access options rather than perfect substitutes.
Security, administration, recording needs, accessibility requirements, and company policy also belong in the decision. Around’s distinctive interface does not remove the need for ordinary vendor assessment. A regulated enterprise may assign more weight to governance and retention controls, while a ten-person studio may prioritize speed, screen efficiency, and conversational flow. The correct weighting depends on the cost of failure in each environment.
Miro’s Acquisition Clarifies the Larger Collaboration Strategy
Around announced that it had been acquired by Miro to help shape the future of team collaboration. Strategically, the combination is understandable. Miro centers work on a shared visual canvas, while Around was built around communication that leaves room for the work itself. One product supplies the collaborative surface; the other developed a less intrusive way for people to remain present around that surface.
The acquisition also changes how prospective users should interpret the product. They should distinguish the historically documented Around experience from the current availability, packaging, and future direction of its capabilities. Product status, supported clients, account access, and commercial terms can evolve after an acquisition. Old testimonials demonstrate what users valued at a particular time, but they do not guarantee that every feature or plan remains unchanged.
From a product-design perspective, Around’s lasting contribution is a strong challenge to the dominant meeting metaphor. It showed that video does not have to occupy the center of digital collaboration. The call can become ambient infrastructure: visible enough to preserve human connection, technically capable of handling difficult hybrid-room acoustics, and restrained enough to let a canvas, prototype, document, or code editor remain primary.
For teams deciding whether this philosophy fits their work, four numbers are more useful than broad enthusiasm: minutes spent setting up calls, audio incidents per session, participation share for remote colleagues, and self-reported fatigue after the meeting. Measure those indicators before and after changing the workflow. If setup time falls, audio problems decline, participation becomes more balanced, and fatigue scores improve, the collaboration-first model is delivering value that extends well beyond a visually distinctive interface.
