Most video meeting tools were designed around a simple assumption: one person, one computer, and one quiet room. Hybrid work breaks that model. Put two coworkers in the same office, add three remote participants, leave every laptop microphone active, and a conventional call can quickly become a mess of echo, feedback, dominant voices, and awkward camera angles. Around approached this problem from a different direction. Rather than treating video as a digital conference room, it was designed as a lightweight collaboration layer for teams that need to work together while they talk.
That distinction matters. A presentation meeting can tolerate a large speaker window and a row of passive listeners. A design critique, planning session, or product review cannot. People need to move between documents, prototypes, and shared work without the call occupying all available screen space. They also need enough visual and vocal presence to read the room, respond naturally, and prevent remote colleagues from becoming spectators. Around positioned its video calls specifically for hybrid and remote teams that create, collaborate, and celebrate together, with an emphasis on making meetings feel less draining.
In practice, I judge a collaboration tool by what happens after the first five minutes. A polished entry screen is useful, but the real test begins when someone shares a prototype, two people in the office speak at once, and a remote teammate tries to interrupt with an important correction. Around’s value proposition was built around those ordinary but difficult moments. Its compact visual approach kept participants present without turning their faces into the main content, while its audio technology addressed one of the most persistent failures of hybrid meetings: several active devices in the same physical space.
Fix the Room Before the Agenda
The most distinctive Around scenario was straightforward: everyone joins from their own device, everyone keeps a microphone available, and the software works to prevent echo. This is more important than it may sound. In a traditional setup, coworkers sitting together usually gather around one conference-room computer. The people in that room can speak naturally to one another, but remote colleagues see a distant group and hear audio filtered through a single microphone. Side comments, facial reactions, and quieter voices are easily lost. The room becomes the center of the meeting, while everyone outside it participates from the edge.
Giving each person an individual device changes the balance. Every participant has a personal camera, a direct view of shared material, and an equal place in the conversation. The difficulty is audio feedback: nearby laptops hear both the original voice and sound from neighboring speakers. Around promoted unique audio technology intended to let multiple people join in the same room with their microphones on and without the familiar echo loop. One user quoted on the product site described a meeting with two people on-site and one online in which all three had the same experience and equal “power of voice.” That is a concise description of what good hybrid design should accomplish.
I have found this setup especially effective in working sessions with a small local group and one or two remote specialists. In a typical product critique, the designer needs to point at an interface, the engineer needs to question a state change, and the remote researcher may need to bring in customer evidence. With a single room camera, the researcher often waits for a formal pause because conversational cues are hard to read. With an individual connection for each person, reactions are more visible and interruption feels less like breaking into someone else’s room. The technology does not create inclusive behavior by itself, but it removes several structural disadvantages.
The same principle applies in less formal environments. Around explicitly illustrated hybrid work in modern workspaces, hotel suites, and startup houses rather than limiting the product story to conventional boardrooms. That reflects how distributed teams actually operate. A temporary project group may have three people around a kitchen table, another working from home, and a colleague joining from a phone between appointments. The software was available for macOS and Windows, through major browsers including Chrome, Safari, Edge, and Firefox, and on iOS and Android. That breadth reduced the chance that one participant would be excluded simply because the team was working away from its normal office equipment.
Keep Work Larger Than Faces
Around’s design philosophy also challenged the visual hierarchy of standard video conferencing. Large portrait tiles can create the sensation of constant performance: every movement is enlarged, eye contact is ambiguous, and the actual work competes with the call for space. For a team reviewing a document or building a product together, that hierarchy is backward. The artifact should remain central, while video should supply social context. Around became known for a more compact, playful meeting presence that could sit alongside the applications people were already using.
For a clear picture of how the service framed that experience, www.around-com.com/ presents Around as video calling for extraordinary teams and emphasizes meetings centered on creating, collaborating, and celebrating rather than merely watching speakers. That wording matches the strongest practical use case: active sessions in which conversation accompanies work. It is less about reproducing a boardroom on a screen and more about letting teammates remain aware of one another while editing, sketching, testing, or making decisions.
During design reviews, I use a simple test: after screen sharing starts, can participants still follow both the material and one another without continuously rearranging windows? If the answer is no, attention fragments. Someone covers a relevant panel with the meeting window, another loses sight of reactions, and a third stops taking notes because there is no comfortable place to put the document. A compact call interface lowers this friction. The benefit is not visual novelty for its own sake; it is preservation of working space and cognitive focus.
The lighter presentation can also change the emotional tone of recurring meetings. Around’s public testimonials repeatedly described the product as delightful, beautiful, and joyful, and one team mentioned holding a Friday virtual campfire. Those reactions are notable because video software is usually discussed in terms of reliability rather than affection. Playfulness is not a substitute for clear audio or stable access, but it can make recurring rituals feel less mechanical. In my own team practice, a relaxed social session works better when the tool does not make every participant feel as though they are delivering a formal presentation. People stay engaged longer when the interface supports the mood instead of imposing corporate formality on it.
That does not mean every meeting should become casual. A serious planning review still needs a defined owner, an agenda, and a decision record. The lesson from Around is narrower and more useful: visual presence should be proportional to the task. If the goal is to watch a keynote, a prominent speaker view makes sense. If the goal is to compare mockups, resolve implementation questions, or co-write a launch plan, faces should remain available without overwhelming the work. Good collaboration software adapts to human attention rather than demanding that humans adapt to the software’s default layout.
Run the Meeting as Designed
Tools cannot rescue a poorly structured meeting, so I pair the Around model with a few operating habits. Before a hybrid session, I ask every participant to join individually, even when several people share a physical room. I keep the shared artifact open before the call begins and name one person responsible for capturing decisions. I also address remote participants early instead of allowing the local group to establish a private conversational rhythm. This combination gives the audio system, personal video presence, and compact interface a chance to deliver the equality they were designed to support.
A concrete example is a six-person sprint review with three coworkers in a studio and three people elsewhere. The studio participants sit at their normal desks rather than crowding around a conference display. Each person opens the same prototype and joins from a laptop. The facilitator begins with the decision to be made, not a general status update. As the prototype is tested, everyone can speak from their own position, see reactions, and inspect the same material. At the end, the facilitator reads back the chosen changes and assigns owners. The call remains a work surface rather than becoming a ceremony about being on camera.
There are still practical boundaries. Headphones may remain the safest option in especially noisy spaces, device quality varies, and no echo-management system can fix an unstable network. Mobile access is valuable for continuity, but detailed collaborative work is usually easier on a larger screen. Teams should also decide whether a playful meeting style is appropriate for external conversations, interviews, or highly formal presentations. Around’s approach is strongest when the participants already share a working context and need fast, natural interaction around common material.
The project’s later history is also relevant. Around announced that it had been acquired by Miro to help shape the future of team collaboration. The strategic fit is clear: Miro centers work on a shared visual canvas, while Around focused on keeping people connected without allowing the call to dominate that work. An acquisition notice, however, is not the same as a guarantee that every standalone feature, download, price, or platform workflow remains unchanged. Teams assessing current availability should distinguish the enduring design ideas from any specific product status shown at a given moment.
Around’s lasting contribution is a practical reframing of hybrid video. The essential unit is not a room camera broadcasting a group to outsiders; it is each participant joining with an individual voice, view, and place in the work. Audio should accommodate people who share a room. Video should provide connection without consuming the screen. The interface should respect both serious collaboration and the social rituals that hold distributed teams together. When those conditions are met, a meeting feels less like a scheduled transmission and more like colleagues actually working side by side.