Around, presented online as around-com.com, was a video collaboration platform designed for remote-first work. Its central idea was that a video call should support the work happening on a computer rather than dominate the screen. Instead of treating every conversation like a formal conference, the service focused on compact, lightweight communication for people editing documents, reviewing code, refining designs, or holding quick team check-ins.
The platform combined native desktop applications, browser access, mobile apps, chat, screen sharing, meeting rooms, and integrations. It was intended primarily for collaborative sessions involving a small group, although a meeting could support as many as 50 participants. Around was later acquired by Miro, the visual collaboration company, to contribute to the development of future team-collaboration experiences.
What Around Was Built to Do
Around described itself as a reimagining of video collaboration for the remote-first era. That positioning reflected a practical distinction: conventional videoconferencing products often make the call itself the main event, while Around was designed for sessions in which participants needed to keep using other applications. The video layer remained visible, but it did not have to occupy most of the display.
This approach was particularly relevant to work that requires both conversation and shared context. A designer may need to see a prototype and the reactions of colleagues at the same time. Developers conducting a code review need access to the code, comments, and development tools while they discuss changes. Writers and project teams may need to edit a document together without repeatedly switching between a full-screen call and the material under discussion.
The service therefore emphasized short, active collaboration rather than passive attendance. Its documented use cases included one-on-one meetings, team synchronization sessions, spontaneous conversations, collaborative document editing, design work, and code reviews. These examples clarify that Around was not merely another way to display a gallery of faces. It was intended to operate as a communication layer around the task.
- One-on-one conversations: colleagues could maintain visual contact while working through a document, plan, or problem.
- Team syncs: small groups could review progress without turning the meeting into a presentation-heavy event.
- Design sessions: participants could discuss visual material while preserving screen space for design software or shared prototypes.
- Code reviews: developers could inspect changes and communicate without allowing the video interface to obscure technical content.
- Unplanned collaboration: a room link could support a quick working session when text messages were no longer sufficient.
The product’s lean design did not mean it was limited to informal calls. Around also provided recording in beta, high-resolution screen-share viewing on mobile devices, and a participant limit large enough for broader team meetings. Its defining emphasis, however, remained focused collaboration in which video supported the activity instead of competing with it.
Floating Mode and the Native Desktop Experience
The most distinctive difference between Around’s desktop and web experiences was Floating Mode. Available in the native applications, this mode allowed the video interface to stay above other applications. Participants could remain visible while a document editor, browser, design program, or development environment occupied the main workspace.
Floating Mode addressed an ordinary but significant problem in remote work: visual contact and digital work often compete for the same screen. When a videoconferencing window takes up most of a laptop display, users may hide it to access their files. Once hidden, the conversation loses some of the facial cues that make live collaboration useful. Around’s interface sought to preserve those cues while reducing the area consumed by the meeting.
The browser app did not include all of the native applications’ functionality, most notably Floating Mode. For that reason, Around recommended the Mac or Windows application to regular users. Browser access was positioned as a convenient option for guests and occasional participants, particularly when they needed to enter a room without installing software.
The minimum listed desktop requirements were macOS Mojave or later for Mac users and Windows 10 for Windows users. On the web, the service supported Google Chrome along with current versions of Safari, Firefox, and Microsoft Edge. These options allowed a host using the desktop application to share a room link with people who did not already have Around installed.
What “Around Adalah” Refers to in Product Searches
The phrase combines the product name with an Indonesian word commonly used to mean “is,” so a search for around adalah is essentially a request for a definition of Around and its role in online collaboration. In this context, Around refers to the remote-work video platform associated with around-com.com, not the ordinary English preposition and not a general category of meeting software.
A concise definition is that Around was a cross-platform video collaboration service built to let distributed colleagues talk, see one another, share work, and keep their main applications in view. It offered downloadable desktop software, a browser-based guest experience, iOS and Android apps, reusable room links, screen sharing, messaging features, meeting recording in beta, and a Slack integration.
The distinction between videoconferencing and video collaboration is important to understanding the product. Videoconferencing can describe any live audiovisual meeting, including webinars and large presentations. Around’s product language concentrated on people doing something together: revising content, evaluating designs, discussing code, or coordinating tasks. Its interface choices were aligned with that narrower, work-centered purpose.
Around’s acquisition by Miro also places the product in a wider collaboration context. Miro operates in visual teamwork, where distributed participants interact with shared material rather than simply watch a speaker. The acquisition announcement stated that Around would help shape the future of team collaboration. That fact explains the company’s strategic destination without changing what the original product was designed to accomplish.
Joining Meetings Across Desktop, Web, and Mobile
Around did not require every participant to use the same type of client. A host with the installed application could share a room link, and an invited guest could join through a supported browser. This reduced friction for external collaborators, interview participants, clients, or coworkers who had not yet installed the desktop software.
The practical tradeoff was that browser users received a more limited experience. They could participate without a download, but they did not have Floating Mode. Frequent participants were therefore directed toward the native application, while browser access served as an entry point for guests. This arrangement balanced immediate access with a more integrated desktop workflow.
The mobile applications extended participation to iOS and Android. Users could start or join an Around call from a phone and hand a session off between computer and mobile device. The mobile experience also supported chat messages, GIFs, emoji reactions, and images shared from the device’s camera roll. Participants could view high-resolution screen shares, an important capability when the shared material contained visual detail.
- Create or open a room: the organizer starts a collaboration session from a supported Around client.
- Share the room link: invitees receive a direct route into the session rather than needing a separate account-specific meeting setup.
- Choose an access method: regular users can enter through the Mac or Windows app, while guests can use a supported browser.
- Move between devices when needed: mobile handoff enables a participant to continue the call away from the computer and later return.
- Keep the work visible: desktop users can use Floating Mode while the team edits, reviews, or presents shared material.
The platform allowed up to 50 participants in a meeting. That ceiling made sessions larger than a typical design critique or code review possible, even though the company recommended the service most strongly for collaboration with a few other people. The recommendation and the technical limit served different purposes: one identified the product’s preferred working style, while the other defined how many people could enter a call.
Recording, Slack, and the Platform’s Practical Role
Around’s recording feature was identified as a beta capability. It allowed a meeting to be captured for later viewing and offered an immersive playback format intended to give viewers a stronger sense of being present in the original session. Recording could be useful when a teammate missed a review, when decisions needed to be revisited, or when a collaborative process had value beyond the live call.
The platform also connected with Slack. Once the integration was configured, users could invoke Around from Slack with the /around command. This placed the transition from written discussion to live conversation inside a tool already used by many distributed teams. Rather than scheduling a separate formal meeting, colleagues could move from a channel conversation into a video collaboration session when the issue required immediate discussion.
These capabilities show how Around fit into a remote-work toolset. It did not attempt to replace document editors, design applications, source-control systems, or team messaging. Instead, it supplied live audiovisual communication alongside those tools. Room links facilitated entry, Floating Mode kept people visible, mobile handoff preserved continuity, and Slack integration reduced the steps required to begin talking.
The product was best suited to teams that valued continuous, task-oriented interaction. A large all-hands presentation could fit within the 50-person limit, but the service’s design logic was most apparent in smaller working groups. In those settings, participants generally need to observe reactions, discuss details, and manipulate shared material at the same time.
Around’s significance lies in this interface philosophy as much as in its feature list. Remote collaboration is not always a sequence of formal meetings separated from “real work.” It can be a conversation that runs beside the work itself. Around treated video as a persistent but compact presence, gave guests a browser route into rooms, and provided native and mobile options for regular participants. Following its acquisition by Miro, that approach became part of a broader effort to shape how distributed teams collaborate around shared content.