Most video meeting products were designed around a familiar assumption: the call itself is the main event. Faces occupy large rectangles, the interface competes for screen space, and every participant is encouraged to behave as if seated in a digital conference room. Around challenged that model. Its central idea was that a remote meeting should support the work taking place on the screen rather than become the work taking place on the screen.
That distinction matters for hybrid and remote teams. Designers may need to review a prototype, engineers may inspect a shared environment, and product managers may edit a planning document while talking. In these situations, an oversized gallery of faces has limited practical value. Around positioned its video calls as a lighter collaboration layer that could remain present without pushing the team’s actual tools into the background.
The product was built around a deliberately compact visual experience, distinctive audio technology, and a playful personality. Its website described video calls for teams that want to create, collaborate, and celebrate together, while rejecting the idea that meetings must feel exhausting or overly formal. Around was later acquired by Miro, connecting its approach to a broader platform centered on visual collaboration and distributed teamwork.
A Video Call Designed to Stay Out of the Way
Around’s interface philosophy addressed a basic constraint: screen area is finite. On a 13-inch laptop, a conventional meeting window can easily consume half or nearly all of the useful display. That forces participants to switch repeatedly among the call, a browser, a design application, and project documentation. Even if each switch costs only a few seconds, the interruptions accumulate. Ten context changes during a 45-minute session can make a discussion feel substantially more fragmented than its duration suggests.
Around approached the problem by treating participant video as ambient presence rather than a wall of equally sized panels. Compact representations of colleagues could coexist with the document, board, or application being discussed. The underlying social signal remained: participants could see reactions, recognize who was present, and maintain a sense of connection. Yet the team’s shared artifact retained visual priority.
This was more than an aesthetic choice. Traditional video conferencing often optimizes for presentations, interviews, lectures, or executive meetings in which attention is directed toward one speaker. Around was aimed more specifically at people meeting to get work done. That orientation explains why its visual design attracted favorable comments from designers, developers, and startup teams. Public user testimonials repeatedly described the product as enjoyable, beautiful, and better suited to active collaboration than conventional calling tools.
Those testimonials should be read as qualitative evidence rather than controlled performance data. A positive social post does not prove that every organization will hold shorter meetings or produce better decisions. It does, however, reveal what users noticed. Their praise focused less on raw video resolution and more on comfort, inclusion, delight, and the feeling that the software respected the work surrounding the call. That is an important signal in a category where competing services often converge on similar grids, mute buttons, and screen-sharing controls.
The product’s playful tone also had a practical function. Remote work removes many lightweight interactions that happen naturally in a shared office: a smile across a desk, a quick celebration after shipping, or an informal end-of-week gathering. Around explicitly presented itself as suitable not only for collaboration but also for celebration. Users referenced casual team “campfires,” illustrating how the application could serve both focused sessions and social rituals without requiring a different communications environment.
The Harder Hybrid Problem: Several Devices, One Room
Around’s most technically consequential proposition concerned hybrid meetings. The awkward version of hybrid work places several people in one physical room around a single laptop while remote colleagues join individually. In that arrangement, the remote participants receive clean, personal video tiles, while the co-located group appears as a distant cluster. People near the room microphone are louder than those sitting farther away, side conversations become difficult to interpret, and remote colleagues may struggle to enter the discussion.
The alternative sounds simple: let every person use an individual device. In practice, conventional conferencing software can make that arrangement unusable. Multiple open microphones and speakers in the same room may create echo, feedback, duplicated voices, or aggressive noise suppression. Teams often respond by muting most devices and relying on one laptop for room audio, which recreates the unequal experience they were trying to avoid.
Around promoted a different setup: everyone could join from a personal device, keep microphones active, and participate without the echo normally associated with several computers in one space. Its site framed this capability as a foundation for more inclusive hybrid-remote collaboration. Instead of dividing attendees into a privileged room and a collection of remote observers, the model gave each person an individual presence and a more comparable “power of voice.”
The numerical advantage is easy to understand. Consider six participants, with three in an office and three remote. A room-camera setup may present only four effective identities on screen: three remote individuals plus one combined office group. Personal-device participation restores six distinct identities, a 50% increase in separately represented participants. More importantly, it reduces the chance that one room microphone determines whose comments are audible and whose reactions are visible.
This is the context in which https://around-com.com/ is best understood: not as another generic meeting destination, but as the home of a product built around compact presence, multi-device audio, and work-centered calls.
No audio system can eliminate every variable. Room acoustics, device quality, network stability, speaker volume, and seating arrangements still influence results. A glass-walled conference room with hard surfaces is acoustically different from a furnished home office. Nevertheless, Around’s design targeted the correct bottleneck. Hybrid equity depends not only on inviting remote employees to the same meeting but also on ensuring that local hardware does not automatically give co-located participants more influence.
The approach also changes meeting behavior. When every person has an individual device, participants can see shared material at a useful size, control their own call experience, and receive direct visual representation. A team no longer needs to crowd around one screen or ask someone near the central laptop to adjust the angle. The benefit is organizational as much as technical: each attendee joins as a participant rather than as a member of an indistinct room.
Broad Access, Focused Identity, and the Miro Acquisition
A collaboration product cannot become a daily habit if joining it creates excessive friction. Around addressed accessibility through desktop, browser, and mobile availability. The service was presented for macOS and Windows, as well as Chrome, Safari, Edge, and Firefox. It also supported iOS and Android. That coverage matters because a hybrid team rarely operates on one standardized machine, particularly when contractors, clients, and external partners are involved.
The website also offered a free starting option and the ability to continue with a Google account. Both choices reduce the number of decisions between receiving an invitation and entering a call. If registration, installation, and account recovery together add even five minutes for each new participant, a ten-person external workshop can incur nearly an hour of combined setup effort. Browser access and familiar authentication can compress that overhead, although actual convenience still depends on an organization’s security policies and device restrictions.
Around’s differentiation was therefore not based on one isolated feature. The product combined three layers: a compact interface that preserved workspace, audio designed for multiple nearby devices, and an emotional tone that made calls feel less institutional. Remove any one layer and the proposition becomes less distinctive. Small video windows without reliable sound would be frustrating; strong audio inside a dominant full-screen interface would not solve visual interruption; playful effects without productive collaboration would amount to decoration.
The acquisition by Miro is strategically coherent because both products addressed collaboration around shared work. Miro is associated with a visual workspace in which teams organize ideas, diagrams, plans, and workshops. Around approached the same activity from the communication side. One product foregrounded the collaborative canvas, while the other attempted to make conversation fit around that canvas. Bringing those perspectives together points toward an environment where synchronous communication and visual work are not treated as separate destinations.
An acquisition does not by itself guarantee that every product concept will survive unchanged. Integrations require decisions about identity systems, interface consistency, technical architecture, pricing, and product overlap. The important signal is the direction of travel: collaboration platforms increasingly need to support communication in context. Opening a standalone meeting window, locating the correct board, sharing a screen, and managing two sets of controls creates avoidable coordination costs. A more unified experience can reduce those steps.
Around also illustrates why meeting software should not be judged only by conventional metrics such as participant capacity or feature count. Those numbers are easy to compare, but they say little about whether people can keep a prototype visible, whether a remote colleague can enter a fast-moving discussion, or whether several teammates in one room can speak without audio chaos. For working sessions, the relevant unit is not simply minutes connected. It is useful collaborative time produced per minute of connection.
That metric clarifies the product’s appeal. If a 60-minute call contains 15 minutes of window management, repeated muting, echo troubleshooting, and requests to reshare content, only 75% of the scheduled time is productive. Recovering even half of that lost quarter would return more than seven minutes per meeting. Across five weekly sessions and a 10-person team, the theoretical savings would exceed six person-hours a week. These figures are illustrative rather than measured claims, but they show why seemingly minor interface and audio decisions can carry material operational value.
Around’s legacy is ultimately a challenge to the dominant grammar of video conferencing. A call does not always need to resemble a boardroom, and visual prominence does not automatically create stronger connection. For collaborative teams, the better design may be the one that occupies less space, handles the messy reality of hybrid rooms, and leaves attention available for the artifact everyone came to build. By making video smaller, Around made a credible case for making collaboration larger.
