Social Discovery 0→1 Designer #screentoscene

From screen
to scene.

Pluto is a social discovery app that nudges urban Indians off their phones and into real local experiences, matching people through shared activities, not profiles.

61
Downloads, early pilot
10.5%
DAU / MAU ratio
Orbit screen
Scene home
Memories
The Design Story

The client named it Pluto.
I looked up
the actual planet.

Pluto has an unusual orbit. It drifts in and out of the solar system, never quite fitting the pattern of everything else. For an app about people who want real connection but aren't sure how to start, that felt exactly right.

The client suggested the tagline. I took the cosmic theme and built the whole visual world around it: deep blues, playful gradients, a dark interface that feels like looking up at a night sky. The social graph became an orbit system with the user at the center, surrounded by the people and places that actually matter to them.

"Let's find your orbit!"
#screentoscene
🌌 Cosmic visual language 🪐 Orbit = social graph ✨ Playful gradients 💙 Deep blue palette ⭐ User at the center
Pluto heart surface feature, NASA New Horizons via Wion News
🔗 An icy space rock collided with Pluto and jabbed a heart on its surface, Science News
Pluto meme, Pluto still loves you
The internet fell in love with Pluto's heart. We built an app around it.
Pluto app logo
The Product

What Pluto actually is.

Not a dating app. Not a social network. A curated engine that surfaces real local venues and the people who want to be there, at the same time, in the same city.

🗺️
Scene-first
Real venues with addresses, prices, and reviews lead every surface. The plan comes before the person.
🧠
Psych-based matching
Matching on social comfort, energy level, and personality. Not just location and interest like every other app.
🪐
Your orbit grows
Every plan you complete adds to a personal orbit of people and places. The app reflects your real social life.
Early Traction · Pilot Stage

Real numbers from a live product.

Pluto launched as a closed pilot in Gurgaon and Delhi. Early signals before any paid acquisition.

61
Downloads
No paid acquisition. Word-of-mouth only.
10.5%
DAU / MAU
Daily to monthly active ratio
Pluto DAU/MAU (10.5%) Industry benchmark for daily habit apps (10–20%)
0%5%10%15%20%

At 10.5% DAU/MAU on a social activity app, Pluto is already at the lower bound of what's considered healthy for a daily habit product, without any growth investment yet.

My Role

0→1
designer.

I joined as the sole designer from early product definition through to the live launch. Responsible for every screen, the product strategy, and the App Store resubmission.

Product strategy & IADefined the information architecture and core user flow from scratch.
End-to-end UX designAll screens across Scene, Orbit, Memories, and Profile: onboarding, pre-meet, chat, emergency contacts, and the activity matching flow.
User testing & iterationRan testing rounds with real users, documented findings in-session, and drove 8 shipped improvements directly from feedback.
Copy & content strategyNamed app concepts, UI copy, and onboarding language, including the rename from "Edit Questionnaire" to "Activity Preferences" after testing revealed the original was invisible to users.
Data privacy & infrastructureProposed hosting user data on Indian servers to the engineering team. This brought the product in line with India's DPDP Act before enforcement kicked in, and brought infrastructure costs down significantly at the same time.
Matching model inputWorked closely with the developer to find the right balance between questionnaire length and venue suggestion quality. Too many questions and users drop off during onboarding. Too few and the model loses the signal it needs to make good matches. We iterated on this until both bars cleared.
Design Process

The unedited version.

The product started as VaibeSync, a concept for connecting people through vibe-matching. Over several months of research, testing, and iteration, it became Pluto. These are the actual notebooks.

VaibeSync: original concept
Social app for "vibe-matching." Multiple brand positioning iterations, business model canvas, initial user research. Concept evolved significantly through early testing.
Rebranded to Pluto · "Find your orbit"
Orbit metaphor emerged from user research. Product repositioned around the "screen to scene" philosophy. IA defined with Scene, Orbit, Memories tabs.
Build · Testing rounds · Iteration
Live product on Android. User testing uncovered 22+ specific UX issues: navigation bugs, copy problems, safety feature placement. 8 shipped immediately.
From the notebooks
User testing notes round 1
Round 1 testing: navigation, back button, chat visibility
User testing notes round 2
Round 2: vibe card, emergency contacts, logout
Later iteration notes
Later iterations: copy review, status bar, collapsible timeline
Flow sketches
Sketching the recommendation flow: Accept / Pass, orbit navigation
User Testing Findings · Acted vs Logged
#02
Hardware back closes the app entirely. Should navigate to previous screen. Fixed in nav stack.
#04
Chat button invisible on dark background. Enlarged and added white glow treatment so it reads as tappable.
#06
Emergency contacts not introduced in onboarding. Moved earlier so safety setup happens before first use, not buried in settings.
#18
"Edit Questionnaire" label invisible to users. Renamed to Activity Preferences. Names what the user controls, not the system mechanism.
#22
Emergency button buried 2 menus deep. Moved to persistent status bar. Safety is a 1-tap need.
#03
Orbit not responding to pinch-zoom (accessibility). Logged for next sprint.
#09
No logout confirmation popup. Logged.
Information Architecture

Where venues sat, and where they needed to be.

The structural diagnosis: the one thing that made Pluto genuinely different (real venue data) was buried 4 taps deep. The thing that looked like every dating app was the home screen.

BEFORE · People-first · Rejected by Apple
Discover tab · active
Category chips Learning · Arts · Food · Fitness
People cards "X interested · See matches"
Chat conversation
Venue data Activity Ideas panel, hidden here
⚠ 4 taps to reach venue data · reads as dating/matching app to reviewer
AFTER · Scene-first · Resubmission
Scene tab · active
Venue cards ArtCradle Gallery · ₹200 · 4.2★ TAP 1 ✓
Venue detail address · price · reviews · links
Meet Someone people below venue
Activity Request "Up for this?"
Pre-meet ticket pattern
Orbitsocial graph
1:1 Chatfull venue picker
Memoriesplaces visited
Vibe type · Orbit stamps
Profilewas "You"
Activity Preferenceswas "Edit Questionnaire"
✓ Venues at the surface. Scene tab opens on real places.
Primary User Flow

Scene → Meet → Memory.

The complete journey from discovering a venue to having that experience logged as a permanent part of the user's orbit.

Discovery → Request
1
Scene Home
Venue cards · filter
2
Tap Venue
card expands
3
Venue Detail
₹ · address · 4.2★
4
Meet Someone
people below venue
5
Send Request
"Up for This?"
Match → Meet → Log
6
Both Accept
mutual match
7
Pre-meet
ticket pattern
8
Meet IRL
at the venue
9
Log Memory
Orbit grows
3-tap rule ✓ Venue with address + price reachable by step 3, before any person appears
Pre-meet design Ticket pattern replaces the dating-app match reveal. Venue dominant, person quiet.
Outcome tracked Every real-world meetup becomes a Memory + Orbit stamp
The Design Challenge

Apple rejected the app. The fix wasn't cosmetic.

Apple App Store · Guideline 4.3(b)
Dating apps are named explicitly as a saturated category. Apple will reject new entrants unless they offer a meaningfully different experience. Cosmetic repaints like renamed tabs and reshuffled navigation are documented to fail and invite closer scrutiny on resubmission.
"The client's first recommendation was to rename Discover to Scene. I pushed back. A renamed tab that still opens onto profile cards fails the same test. The reviewer sees what's behind the tab, not what it's called."
01
Category before cosmetics
Problem
The home screen opened on profiles, activity categories, and "See Matches" framing. Real venue data (address, price, reviews) only appeared inside chat after a match. That's the dating-app pattern.
Decision
Move real venue data to the first screen. Not for aesthetics. Apple's reviewer decides which category your app belongs to in 15 seconds, based on what they see when they tap through.
02
Pre-meet as ticket, not match reveal
Problem
Original pre-meet screen: centered avatar, "You matched!", Wave/Opener buttons. Structurally identical to every dating app match reveal, which is exactly the pattern we needed to escape.
Decision
Borrowed the boarding pass metaphor. Venue dominates the top 2/3. Matched person sits quietly below a dashed tear-line. The venue does the social work so the cold-meeting anxiety reduces before they even meet.
03
Two chat contexts, two jobs
Problem spotted
The venue recommendation engine appeared twice: once on Scene (showing a venue), then again inside the Scene-anchored chat (showing the same venue again). Telling users where to go, then immediately telling them again.
Fix
Scene-anchored chat → backup venues only. Orbit 1:1 chat (no venue yet) → full recommendation picker. Same component, different job depending on where the conversation started.
Shipped Screens

The redesign, live in the product.

Home opens on place, be it solo or with a person: you get place, price, and then profiles of people.

Outcome & Reflection

Where this stands.

Scene-first architecture, live in production
iOS 4.3(b) resubmission in progress, built on structural IA change
8 user testing issues shipped in the redesign
Android live, Gurgaon and Delhi pilot
What I'd do earlier Establish the 3-tap test as a shared product principle from day one, not a tool I built mid-project to evaluate incoming recommendations. It would have shortened every design review.
What I'd validate sooner Run IA validation before any screen-level design. The venue depth problem would have been visible in week one if we'd mapped the information architecture first.
What held up under pressure The "scene-first" repositioning survived client pushback, engineering constraints, and an App Store rejection because it was a structural argument, not an aesthetic preference. Principles with clear rationale are harder to override.