The phrase “around adalah” combines the product name Around with the Indonesian word for “is,” so the underlying question is straightforward: What is Around? In this context, Around refers to around-com.com, a video collaboration service designed for remote-first work. Rather than treating a call as a large video conference that occupies the entire screen, the product was built to keep participants visible while they worked together in documents, design tools, code editors, and other applications.

Around positioned itself as a focused collaboration environment for one-on-one conversations, small team syncs, design sessions, document editing, code reviews, and spontaneous meetings. Its distinguishing idea was not simply video calling. It was the combination of video, screen sharing, lightweight meeting controls, and a compact interface intended to remain present without covering the work being discussed.

The company has since been acquired by Miro, the visual collaboration platform. That acquisition is important when assessing Around today: the service’s concepts and technology are relevant to the broader development of digital teamwork, but anyone evaluating present-day access should distinguish the documented Around product from whatever functions Miro currently offers or incorporates into its own platform.

What Around Was Designed to Do

Around addressed a common problem in remote collaboration. Conventional meeting software often places the call itself at the center of the experience, with a grid of participants taking up most of the display. That layout works for presentations, larger meetings, and structured discussions, but it can be less convenient when several people need to concentrate on a shared artifact.

Around reversed that emphasis. The work remained central, while participant video stayed visible in a smaller, less intrusive form. Its native desktop applications included a Floating Mode that allowed the video interface to sit above other applications. Team members could therefore maintain visual contact while reviewing a design, editing a document, or examining source code.

This approach made the product particularly suited to collaborative sessions involving a few active participants. The service supported meetings with as many as 50 people according to its published FAQ, but its recommended uses centered on smaller groups rather than webinar-style events. The stated use cases included:

• One-on-one meetings in which both participants needed to reference shared material.
• Team syncs focused on an active project rather than a formal presentation.
• Collaborative document editing with ongoing voice and visual communication.
• Design sessions where participants reviewed or changed visual work together.
• Code reviews that required discussion alongside an editor or repository view.
• Unplanned conversations that needed to begin without extensive scheduling.

The distinction matters because Around was not merely a compact version of a standard conference grid. Its interface reflected a specific theory of remote work: video should support a shared task without becoming the task. That made it most relevant when a team’s attention needed to remain on software, content, or a creative workspace.

Desktop, Browser, and Mobile Access

Around offered native applications for Mac and Windows, as well as browser-based access. The documented minimum desktop requirements were macOS Mojave or later for Mac users and Windows 10 for Windows users. Its web application supported Google Chrome and recent versions of Safari, Firefox, and Microsoft Edge.

A host using the installed application could invite someone who did not have Around installed. The host shared a room link, and the guest could enter through a supported browser. This reduced the setup burden for occasional participants, clients, or collaborators outside the host’s organization.

The browser experience did not provide every capability available in the native applications. Most notably, it lacked Floating Mode. That limitation affected one of the product’s defining features because browser guests could participate in the meeting but did not receive the same persistent, application-level video overlay. Around therefore recommended the Mac or Windows application for regular users, while presenting the web app as a practical option for guests.

Mobile applications were also available for iOS and Android. They allowed users to start or join calls, communicate through chat messages, send GIFs and emoji reactions, share images from a device’s camera roll, and view high-resolution screen shares. The mobile experience also supported handing a call from a computer to a phone and back again, which was useful when a participant needed to move away from a desk without leaving an active conversation.

For readers encountering the mixed-language search phrase around adalah, the concise definition is that Around was a cross-platform video collaboration product built to keep remote teammates connected while they worked inside other digital tools.

How an Around Session Worked in Practice

The most representative Around workflow began with a room rather than a complicated meeting setup. A participant could start a session and share access with teammates. Regular users could join through the desktop software, while guests could use a supported browser. Once connected, participants could speak, remain visible, exchange chat messages, and use screen sharing to focus the discussion on active work.

A typical small-team session could proceed as follows:

1. A host opened or started an Around room from the desktop application.
2. The host shared the room link with colleagues or external participants.
3. Invitees joined through a native application or a supported web browser.
4. One participant shared the relevant document, design, code, or application window.
5. Desktop users used Floating Mode to keep video present while working in other software.
6. Participants discussed changes, responded through chat or reactions, and completed the task together.
7. If needed, an eligible meeting could be recorded for later viewing.

Around also documented a Slack integration. After connecting the two services, users could invoke Around from Slack with the /around command. This reflected the product’s emphasis on quick, contextual meetings: a text conversation could move into a live session without requiring participants to switch to a separate scheduling process first.

The service included a meeting recording feature in beta. Its purpose was not limited to producing a basic video file. Around described an immersive playback experience intended to help later viewers feel more connected to the original meeting. Because the feature was labeled beta, its availability and behavior could have been subject to change, and it should not be treated as equivalent to a permanent archival or compliance-recording system without separate verification.

The documented meeting limit of 50 participants gave Around room to support larger team conversations, but scale alone did not define the product. Its interface and recommended scenarios favored direct collaboration. Organizations seeking broadcast controls, large-event administration, or highly formal conference management would have been evaluating a different category of requirements.

What Made the Interface Different

Around’s main product decision was to reduce the visual dominance of conventional video conferencing. In many meeting tools, large participant rectangles compete with the document or application under discussion. Around instead used a leaner visual presentation and proprietary technology to make participants feel present without requiring a full-screen meeting window.

Floating Mode was the clearest expression of that approach. By remaining on top of other applications, the interface preserved facial cues and conversational awareness while leaving most of the screen available for productive work. For a designer, that could mean keeping a design canvas unobstructed. For a developer, it could mean reviewing code while still seeing colleagues. For a writer or project team, it could mean editing a document without repeatedly switching between the document and a conference window.

The practical benefit depended on the nature of the meeting. Floating video offered less advantage during a lecture or presentation where participants were primarily watching one speaker. It was more relevant when several people were actively manipulating or reviewing the same material. Around’s design should therefore be evaluated as a workflow choice, not simply as a cosmetic variation on video chat.

Its guest-access model reinforced that workflow. A team could use the full desktop experience internally without requiring every occasional collaborator to install software. At the same time, the difference between native and browser functionality meant that not all participants experienced the same interface. Teams relying heavily on Floating Mode needed to account for whether key contributors were using the desktop application or joining from the web.

The mobile handoff feature addressed another practical aspect of remote work: calls do not always remain tied to one device. Moving between a computer and a phone could preserve continuity during a meeting, although tasks such as detailed design review or code collaboration would naturally remain better suited to a larger screen.

How to Assess Around After the Miro Acquisition

Around’s acquisition by Miro changes the way the product should be considered. The available product information establishes what Around was designed to do and which platforms and features it supported. It does not, by itself, guarantee that every original application, download, integration, room, or beta feature remains available under the same terms today.

For that reason, a current evaluation should separate product history from present service status. The historical product can be described with confidence as a remote-first video collaboration tool featuring native Mac and Windows applications, browser access for guests, iOS and Android applications, Floating Mode, screen sharing, chat and reactions, mobile call handoff, Slack integration, and beta meeting recording. The published FAQ placed the meeting capacity at 50 participants and recommended the service especially for smaller collaborative sessions.

The acquisition also helps explain why Around remains relevant even if a buyer is comparing current platforms rather than choosing the original standalone service. Its core design question—how to maintain human presence without obscuring shared work—continues to matter in visual collaboration, distributed product development, and hybrid teamwork. Miro’s acquisition statement explicitly connected Around with the future of team collaboration, indicating that the value extended beyond operating another conventional calling application.

The verdict is therefore conditional. Around is worth understanding as a distinctive model for task-centered video collaboration and as technology acquired by Miro. Its compact interface, Floating Mode, guest browser access, mobile support, and focus on working together differentiated it from meeting tools organized mainly around a participant grid. However, anyone considering it for active organizational use should confirm the current availability of the standalone applications and individual features rather than relying solely on historical documentation.

In plain terms, Around was built for people who wanted to talk face to face while keeping documents, designs, and code in the foreground. That focused purpose—not the ability to host a video call by itself—is the most accurate answer to what Around was and why its approach attracted Miro’s interest.