Home
What matters now, active invitations, current plans and the OMA paths launcher.
Join early access OMA 1.1 · product experience
Distinct experiences.
One familiar home.
OMA 1.1 extends the private friend-group foundation into distinct service experiences, supported by horizontal layers that make every moment more useful without turning the app into a collection of permanent tabs.
Explore the services01
Every service has its own object, lifecycle and first action. Home, Groups, Inbox and Me stay familiar underneath.
The shared foundation
One app, not a collection of mini-apps.
The service name, context and actions change when they matter. Home, Groups, Inbox and Me remain the familiar way through OMA.
Groups
Lasting Groups, Trips, Hangouts and deliberate continuations.
Inbox
Messages, invitations, introductions, requests and service-labelled notices.
Me
Core identity, privacy, active services, safety and account controls.
The OMA services
Different reasons to connect.
The same trust underneath.
Open a service to see its promise, its distinction and the initial mobile-to-outcome flow that makes the concept concrete.
01 · OMA Trips
Go further, together.
A calm private home for the whole journey—from the first idea to the Moments a group chooses to keep.
Structured, multi-day and anticipatory. The Trip Group Space keeps the group identity at the centre while the journey takes shape.
- Overview · Chat · Plan
- Expenses and Concierge modules
- Moments and People
- Recap and archive
BoundaryTrip membership remains the boundary. A Trip does not become public content or a live location feed.
Initial mobile flow
From first action to outcome
01
Start with an idea
Create a Trip or open a group-scoped invitation. The group sees the purpose and the people involved before joining.
Actual service release order
Release one service at a time.
These are the first three product moments to make real. The rest of the OMA 1.1 family can share the foundation without competing with the initial release sequence.
First priority release
OMA Trips
The full private group journey: plan, coordinate, go and keep the right moments.
Second priority release
OMA Couples
A dedicated two-person room that begins with playful connection and grows into optional Bond layers.
Third priority release
OMA Hangouts
A bounded, lightweight group moment with a clear start, live state and clean close.
Mobile product model
One shell.
Different first actions.
OMA should feel like one coherent mobile product. The current service determines the first useful action, while Places and Music enter only when the active context calls for them.
Trips
Plan
The first screen opens the group brief, decisions and upcoming plan.
Couples
Send
Today makes the next small act of connection one tap away.
Hangouts
Start
A moment becomes a private group with a clear expiry.
Explore
Declare
A temporary intention appears before any people or place detail.
Date
Introduce
Purpose and mutual consent come before conversation.
Work
Name the purpose
The reason for meeting is visible before a connection opens.
Places + Music
Add context
Horizontal layers enter the active service instead of competing for permanent tabs.
The invitation contract
An invite opens the door.
Consent creates the connection.
Open the exact path
A typed QR code or private link carries the service, object, scope and expiry.
Preview before joining
See the purpose, visibility, participants and what continuing will share.
Choose explicitly
Joining, activating Date or Work, or publishing an Explore intention requires a deliberate action.
Leave or let it end
Invites can be revoked, temporary states expire and continuation is always a separate choice.