Orbit Living
Solving the trust, reliability and usability gap in society management apps.
company
Beeyond Tech
role
UI/UX designer
team
status
Live on app store & play store
overview
A society management app for gated communities. I led design across its core resident modules, hq dashboard and product website.
the problem
research
Three people,
one app.
Built on Beeyond's research with 20+ residents and a competitor audit before every module, so it works for a 58-year-old owner as easily as a 22-year-old tenant.
the website
One product, two very different buyers.
Residents use Orbit, but committees decide whether a society gets it. I designed and built the product pages for both in Framer, along with the demo booking and the FAQ.
visit orbitliving.co ↗
Add: orbitliving.co hero, full width
resident app
Four modules,
one journey.
I led onboarding, community, listings and payments, and designed the expanded marketplace.
onboarding
The gate before the gate.
Orbit doesn't onboard you into an account. It onboards you into a place.
principles
Place before profile.
Find your flat first. Details come later.
Trust, the way it already works.
Verified by people who know you, not a form.
No dead ends.
Pending residents can still read notices.
society and flat
Role comes late, once you've found your flat.
type-ahead · verified badges · wing, then unit
loading and pending
Waiting isn't a dead end.
status banner · notices open · payments later
components
Every state, even the unhappy ones.
phone · one-time code · search · select
community
The daily reason to open the app.
Every feature had to beat one thing: just texting the group.
Feedback said one long form felt overwhelming, so sale and rent now show only their own fields.
Add: event detail + family RSVP modal
RSVP for the whole household in three taps.
Add: search states + empty feed
Everything searchable, and an empty feed invites the first post.
listings
List your home. Without the broker.
Residents list flats inside their own society — verified, with what Orbit already knows pre-filled.
01
Progressive disclosure
A unified form would show 14 fields at once — most irrelevant based on type. The toggle-driven split shows only what the resident needs, when they need it.
impact: reduced perceived form length by ~40%
02
Steppers over free text
Lease Term, Lock-in, and Notice Period use ± steppers. Eliminates invalid inputs and makes the interaction feel like a preference, not a form field.
impact: zero invalid month values in testing
03
Auto-fill from property records
Area data is pre-populated from the resident’s verified record. Eliminates the #1 complaint on 99acres — incorrect manually-entered area data.
impact: prevents misrepresentation at source
status lives on every card — no tapping in
Active
Pending
Rejected
marketplace
From flats to everything.
The first version sold only property. I designed its expansion to anything — furniture, decor, fashion.
payments
The most sensitive three minutes in a resident's month.
One rule: full transparency before any money moves.
Full transparency before every rupee leaves.
The failure screen answers "did I lose money?" first — moved there after feedback.
benchmarked against ApnaComplex, NoBrokerHood, MyGate and Society Connect
beyond the app
Two more
surfaces.
The public website that sells Orbit, and the internal dashboard that runs it.
the website
One product, two very different buyers.
Residents use Orbit, but committees decide whether a society gets it. I designed and built the product pages for both in Framer, along with the demo booking and an FAQ that answers any question a visitor types.
feature cards
Browse it like a hand of cards.
Each card is one feature with its real screen. Dragging through them feels like flipping through the app.
demo booking
A demo booked in one sitting.
Two steps, connected to Cal.com. Online or in person at the society, and the confirmation adapts: a Meet link, or the address.
faq
Ask anything.
Visitors type any question and get an answer straight away, instead of waiting for a demo call.
behind the platform: hq
Designing for the people behind the product.
Orbit's internal teams needed to see how the platform was doing inside each society, and act on it. Under NDA, so every visual here is recreated with dummy data.
proposed
Health, measured on two signals.
Four signal groups became the two the team could actually measure: engagement and support. Each society is compared with its own history, and tiers and trend arrows lead.
proposed
Adoption across three apps.
Opens and actions per module, for the resident app, RWA dashboard and guard app. The weakest modules come first.
shipped to dev
Roles, the Shopify way.
Preset roles, a module × action matrix, and a duplicate action for roles that are almost the same.
small details
The IFSC code fills in the bank and branch.
The society name comes pre-filled.
One status colour system across every table.
how it reached engineering
Each design went over as a staged build brief for Claude Code: checkpoints, tested scoring logic, mock data first.
takeaway
Measure what you can actually measure. Cutting the score to two signals made it trustworthy.
design system
Built
to scale.
Co-built with our senior designer and documented in Dev Mode, so developers built from components, not static screens.
outcome
Live,
in use.
On the App Store and Play Store, used by a society of ~1,000 residents.
reflection
The hardest problems weren't visual, they were decisions that had to hold up.
Next time, I'd make testing formal and start it with the very first prototype.