WebMobi
Mobile app demo · iOS

The app that asks
before it shows.

Realty Connect Global Summit 2026. 8,500 attendees. Three days. You walk in. The app doesn't open with a menu — it opens with a question. You answer in plain words. It guides you to the right person, the right session, the right room. No tab bar. No feature grid. No hunting.

What it is

  • A personal concierge
  • A networking guide
  • A real-time assistant
  • Conversation, not navigation

What it is not

  • A schedule browser
  • A feature list
  • A chatbot UI
  • A directory of strangers
Flow A · 00:00–00:18

Who should I meet?

Sara opens the app at 10:24 AM. She's been awake for two hours and hasn't talked to a single person yet. The app doesn't ask her to scroll a list of 8,500 names. It asks her one question, and her answer is the first move of the day.

10:24

Good morning,
Sara.

What would you like to do?

Ask anything… 🎙
Who should I meet now?
PR
Priya Raman
VP Marketing · Harbor Realty
She's hiring agents in your market
MO
Marcus Okonkwo
Broker-owner · Crestpoint Realty
You both spoke at PLG Summit '24
AL
Aisha Lin
Head of Tech · Northwind Realty
Both leading AI adoption in 2026
Priya was at the Atrium Cafe two minutes ago. Want me to suggest a meet point?
Atrium Cafe
30 ft · 1 min walk
01

"Good morning, Sara."

The home screen is one greeting and three suggested prompts. No tabs. No notifications panel. One question, three answers.

02

She taps the first prompt.

"Who should I meet now?" — a question she'd say out loud to a colleague. The app receives it like one.

03

Three faces, one reason each.

Not 47 names ranked by a fit score. Three people. Each card answers the only question that matters: why this person, right now?

04

"Connect" — sent.

The connection is made. The app immediately offers the next step before Sara has to ask: where to meet, how close, how long.

05

Walk there.

30 feet. One minute. The map is a hint, not a feature. The conversation has carried Sara from "good morning" to "shaking hands" in eighteen seconds.

~18 seconds
Flow B · 00:00–00:14

What's next for me?

Same app. Different question. Sessions are not the primary surface — they're a guided answer when Sara asks. No long lists, no filters, no track-by-track tabs. The app picks one session, says why, and offers the next step.

11:42

Welcome back,
Sara.

What's on your mind?

Ask anything… 🎙
What's next for me?
12:00 PM · Pacific Ballroom A

PLG patterns that built
a $400M brokerage.

Anna Lewis · VP Product, Linear
Matches your interest in tech adoption + sales mastery
Saved. I'll nudge you five minutes before. Anna will also be at the speaker mixer at 6 PM — should I add it?
01

"What's next for me?"

The same conversational entry, two hours later. Sara doesn't open an "Agenda" tab. She asks.

02

One session, one reason.

Not a list. One session — because Sara asked what's next, not what's available. The app shows why.

03

"Save my seat."

The phrase is the action. No "register," no "RSVP," no toast that says "added to calendar."

04

The next step is offered, not asked for.

Anna is also at the 6 PM mixer. Sara didn't ask about Anna twice — but the app remembers Sara liked Anna, and offers the next moment to meet her in person.

~14 seconds
The identity layer

Minimal profile.
Maximum signal.

Sara's profile is what the app uses to suggest who she should meet. Three interests. Three numbers. No bio paragraph, no work history, no skill list. The matching is in the matching — the profile is what matters and nothing else.

SK
Sara Kapadia
Director of Marketing · Harbor Realty
Tech adoption PLG Marketing
12
Events / yr
47
Connections
3
Follow-ups

What would make this generic — and why it doesn't.

Hard rules from the spec. Each one is a failure mode this design explicitly avoids.

Avoid
A bottom tab bar

Home, Agenda, People, Map, Profile — five tabs is five decisions every time the app opens. The conversation collapses all of them into one prompt.

Avoid
A directory of attendees

8,500 names is a wall, not a network. The app suggests three faces with one reason each — that's what a guide does.

Avoid
Chatbot bubbles

Conversation-driven doesn't mean chat-driven. Cards, faces, sessions. The only "bubble" is the AI follow-up, and it's framed as an action — not a reply.

Avoid
Filter chips, sort orders, search

The app already knows. Filters are the user re-asking the question. We answer once.

Avoid
"Thinking…" states

A skeleton row is the absolute most we show. AI complexity is hidden, not performed. If it feels slow, it feels broken.

Avoid
Onboarding screens

The app's first screen is a greeting and a question. The user is already inside.