How Around Differed From Zoom for Hybrid Teams That Needed Better Meetings

When a remote meeting is supposed to help people think, create, or make a decision, the video call itself should stay out of the way. That was the central idea behind Around, a video collaboration product built for hybrid and remote teams. Instead of treating a meeting as a grid of large faces and noisy audio channels, Around tried to make the online room feel lighter, more flexible, and more comfortable for actual work.

The product became known for a distinctive approach to team calls. Participants could join from their own devices, keep their microphones on without creating the usual echo, and appear in a meeting without allowing the video window to dominate the entire screen. Around was designed for teams that might be working from a home office, a shared workspace, a hotel suite, or a company headquarters at the same time.

That focus made Around different from conventional video conferencing services. Zoom, Microsoft Teams, Google Meet, and Skype generally organize the experience around a meeting window. Around positioned the meeting as one part of a broader workspace, where people could continue writing, designing, reviewing documents, or building software while staying connected to colleagues.

Why traditional video meetings created friction for hybrid teams

In a fully remote meeting, every person is usually represented through the same type of connection. Hybrid meetings are more complicated. Some employees sit together in one physical room while others join from home. The people in the room can hear one another naturally and read body language from several directions, while the remote participants often appear as small faces on a screen and may struggle to enter the discussion.

There is also a technical problem. If several people in one office join the same call from separate laptops, standard conferencing software can produce feedback, echo, and competing microphones. The usual solution is to mute most devices, but that removes the spontaneous reactions and conversational rhythm that make collaboration effective. Remote participants hear only the person who remembered to unmute, while the people in the room share a richer experience.

Around addressed this situation with a different audio model. Its product messaging emphasized that everyone could use an individual device while all microphones remained active without echo. That detail mattered in practice. During a planning session with two colleagues in an office and another teammate joining remotely, the room could keep talking naturally instead of stopping every few seconds to manage mute controls. The remote person heard the conversation as a discussion rather than as a sequence of isolated contributions.

The visual design also reduced a common source of fatigue. Standard video grids encourage participants to watch their own image, monitor everyone else, and maintain an artificial level of eye contact for an hour or more. Around used smaller, floating video bubbles and allowed people to keep the call alongside other work. The result was intended to feel less like performing for a camera and more like sharing a workspace.

  • Individual participation: each person could join from a separate device, even when several teammates were physically together.
  • Active microphones: Around’s audio technology was designed to prevent echo while keeping conversation fluid.
  • Flexible presence: video could remain visible without occupying the entire working screen.
  • Hybrid awareness: the experience aimed to give remote colleagues a more equal role in the room.
  • Work focused meetings: the interface was built for people who meet to produce work, not simply to appear on camera.

What made Around feel different during real work sessions

The most useful way to understand Around is to place it inside a normal workday. Imagine a product team starting with a short standup, moving into a design review, and then staying available for informal questions. In a conventional application, each meeting can feel like a separate event: open the call, enlarge the faces, share a screen, mute and unmute, then close the window. Around tried to make those transitions less disruptive.

For a standup, the small video circles let participants see who was present while keeping notes or a project board open. During a design review, the team could discuss a mockup without making the faces and controls compete with the material under review. When someone needed to focus for several minutes, the call could remain present without demanding constant visual attention.

I found this approach especially practical for small teams. A group of four or five people does not always need a large gallery view. What matters is knowing that colleagues are there, hearing interruptions clearly, and being able to move between conversation and shared work. Around’s design reduced the sense that every meeting required a dedicated stage.

The product also made room for a more informal tone. Its website presented use cases such as modern workspaces, hotel suites, startup houses, and team settings where people might collaborate from different locations. That positioning reflected a broader understanding of remote work: a team is not always sitting at desks in identical offices during identical hours. People may be traveling, working from a temporary location, or joining a conversation from a shared room.

That flexibility was visible in the way users described the product. One team said it had moved all of its meetings to Around and found that the meetings improved. Another user described it as the first video calling software built for people who meet to get work done. These comments point to the same practical benefit: the software was judged by the quality of the working session, rather than by the number of conferencing features it could display.

Around also introduced a sense of play that is often missing from business software. A team could use the space for a casual conversation, a remote social moment, or a themed gathering rather than treating every call as a formal appointment. One public example described a team campfire session conducted through the platform. That kind of use showed how the product could support connection and celebration alongside focused collaboration.

For teams evaluating the service or looking for background on its original purpose, http://around-com.com/ represented a product built around this specific meeting philosophy: reduce the mechanical burden of video calls and give people more room to work together naturally.

How Around compared with Zoom and Microsoft Teams

Zoom became popular because it made scheduled video meetings easy to join and dependable at scale. Microsoft Teams combined meetings with chat, files, calendars, and enterprise administration. Both products can support remote work effectively, especially when an organization already depends on their wider ecosystems. Around took a narrower and more opinionated path by concentrating on the human experience of the call.

The difference was not simply a matter of color, layout, or branding. It was a difference in what the application considered important. A conventional meeting platform often asks, “How do we put every participant into the call?” Around asked, “How can people remain productive while they are in the call?” That question influenced the audio, the size of participant video, and the relationship between the conversation and the rest of the desktop.

For a large company that needs webinars, complex permissions, extensive recording controls, or deep calendar administration, a general enterprise platform may remain the more practical choice. Around was most compelling for teams that valued a lighter meeting environment and wanted the call to fit around their work. A five-person creative team, a distributed startup, or a product group working across time zones could benefit more from reduced friction than from a long list of administrative options.

There was also a meaningful difference in the treatment of hybrid meetings. With ordinary conferencing tools, a room full of employees may still behave like one participant. The people sitting together exchange glances and comments that the remote colleague cannot fully perceive. Around’s individual-device approach was intended to make each person visible and audible as an independent participant, even when several people occupied the same physical space.

In a real comparison, I would evaluate the platforms against the same meeting rather than counting features. Start with a short team check-in, then share a document, move into an unplanned discussion, and finish with an informal conversation. Notice whether remote participants interrupt comfortably, whether the room develops echo, how often people touch mute controls, and whether the video window distracts from the task. Those observations reveal more about a collaboration tool than a feature checklist does.

Where the product fit best and what changed later

Around was particularly well suited to hybrid-remote teams that wanted meetings to feel inclusive without making everyone stare at a large video grid. It fit teams that worked in short collaborative cycles, used several desktop applications at once, and preferred conversation that could continue while people looked at a brief, a design file, a task list, or a shared document.

It also appealed to teams that cared about emotional quality. The company’s message that meetings do not have to crush the soul was deliberately direct. Long video calls can create fatigue through constant self-monitoring, poor room acoustics, repetitive controls, and the pressure to look attentive every second. A calmer interface cannot solve every organizational problem, but it can remove several small sources of strain.

The product supported desktop and browser access across macOS and Windows, with compatibility for Chrome, Safari, Edge, and Firefox. Mobile options were available for iOS and Android. That range mattered for distributed teams because participants do not always join from the same kind of device. A meeting may include someone at a workstation, someone using a laptop in a shared office, and someone joining from a phone while traveling.

Around was later acquired by Miro, the visual collaboration company. The acquisition connected Around’s experience in video communication with Miro’s broader work on team collaboration and shared visual spaces. This is an important part of the project’s current story: Around was not simply another independent conferencing brand competing on call length or participant limits. Its ideas became part of a larger effort to shape how teams communicate and create together.

That history also explains why the product remains relevant when discussing the future of hybrid work. The most valuable lesson from Around was not a single interface element. It was the decision to treat audio, presence, focus, and social connection as connected design problems. A meeting feels fairer when remote participants can speak naturally. It feels less tiring when the interface does not demand constant attention. It becomes more useful when people can keep working while they talk.

Teams choosing a video platform should therefore begin with their working habits. If meetings are mainly large presentations, an established conference service may cover the need. If meetings depend on quick decisions, collaborative review, and equal participation between office and remote colleagues, the Around approach offers a more thoughtful standard. The question is whether the software helps people do better work together, and that was the measure Around consistently put at the center of its product.