App design · UX / UI · for UXIndia 2026
CLIENT
Self-initiated, from volunteering at UXIndia 2026
SCALE
5-day conference app · 8 screens · 3 attendee types
MY ROLE
Research, flows, wireframes, UI, design system, coded prototype
TIMELINE
2026 · 15 days
Open the prototype →
01 · Context · The conference
I volunteered in hospitality and operations. All day, people had the same questions like: where is my session, has it moved, and who should I meet? The answers were spread across printed schedules, WhatsApp groups and word of mouth so most of the times even I did not know for sure.
01 · Context · Why an app
Before designing anything, I looked at how two large international events handle the same problems, and what attendees say they need.
Dubai · Europe · Asia
Affiliate World
Its official app is built around meetings. It suggests people who are a good fit, lets you message and book a meeting before you arrive, and connects you by scanning a badge QR. The schedule, your meetings and the venue map all work offline.
Takeaway: matching + booking a time and place turns ‘we should talk’ into an actual meeting for attendees.
Brighton · San Diego
BrightonSEO
Networking runs as a programme of its own: speed networking in a hub, roundtables, drinks receptions and fringe meetups, published alongside the talks.
Takeaway: people plan their day around talks and people together, so both belong in one schedule.
of attendees say networking influences whether they attend an event.
prefer structured networking or a mix, over 'just go with the flow'
say following up with people they met often leads to no meaningful outcome.
So UXIndia needed more than a schedule: it needed a way to make being in the conference easier, meet the right people, at the right time and place.
01 · Context · The idea
The app isn’t organised by features. It follows an attendee’s day.
Arrive: where do I go and what’s first.
Session: what’s on, and a quick note.
Break: who should I meet and what’s next.
Recap: what did I miss and who did I meet.
Each stage shows only what you need in that moment.
Arrive
Next session, a countdown, the map to ease arrivals.
Session
Time left, the speaker, one note box to collect thoughts.
Break
Swipe Meet or Skip. Intros need both to say yes.
Recap
Your day, kept to share or download.
02 · Process · Overview
Discover
Watched attendees at the desk and wrote down every question.
Define
One problem: people miss sessions and miss people.
Design
Sorted the content, mapped the app, then sketches to screens.
Build + test
Vibecoded a working prototype and fixed what confused people.
02 · Process · Content
Before drawing a screen I put every piece of content a conference app could show on its own note, about fifty in all. Then I sorted them with four questions, so the app would only ever show what matters at that moment.
The content dump
event name
day number
date
venue
ticket QR
attendee name
role
interest tags
schedule
session title
speaker
topic and brief
format
room or hall
start and end time
duration
timer
registration desk
map of the place
floor levels
washrooms
food area
heat map
room change
delay information
help button
volunteer text bot
emergency
save a moment
timestamp
quick note
private notes
ask/offer card
topic match
say hi + meeting spot
saved contacts
photos
captions
session tag
posted by
day artifact
sessions attended
moments saved
people met
send notes to self
missed session key points
share + download
volunteer mode
podcast scheduling
request speaker availability
booked slot
auto-reminder
Sorted by four questions
What does the user need to find first?
session title
timer
room or hall
map of the place
help button
schedule
What can they discover later?
ask/offer card
heat map
say hi + meeting spot
missed session key points
share + download
What information is essential?
room change
topic and brief
session title
start and end time
room or hall
heat map
help button
day artifact
emergency
delay information
What information is secondary?
speaker
floor levels
washrooms
quick note
ask/offer card
food area
missed session key points
photos
share + download
session tag
sessions attended
send notes to self
format
What the sorting decided: room changes and delay information are essential, so they interrupt. Speakers, floor levels and food are secondary, so they wait one tap away.
02 · Process · Structure
The sorted content became a map. Four stages hang off the home screen, each with only the screens it needs, so nobody has to dig for what they need right now.
Splash
Log in
Schedule screen
Home
Home
From the home screen
Speaker name
Room number
Timer
Map
Ask / offer
Session
In a session
Title
Summary
Speaker photo
Timer
Quick note
Break
Between sessions
Crowd map
Other session → schedule → select → key notes
Next session timer
Offer / ask match → about the person → location
Leaving
At the end of the day
My day summary
Download
Share
02 · Process · People
Every screen had to work for all three.
COMES ALONE
01
Meera, 27
“I know three people here.”
WANTS
Meet the right people, without the awkward bit
WORRIED BY
Cold introductions
Shaped: Ask and Offer on Break
COMES WITH HIS TEAM
02
“Wait, which room are we in now?”
WANTS
Never miss a room or time change
WORRIED BY
Printed schedules are not updated
Shaped: Orange alerts + one schedule
VOLUNTEER AT THE DESK
03
Sana, 22
“Everyone asks me where Hall B is.”
WANTS
Answer fast, point the right way
WORRIED BY
The same question, again
Shaped: Lorem + crowd map
03 · Design · Low fidelity
First I sketched out rough screens to visualise a look for the app and then developed low fidelity wireframes on Figma. These are few of the screens to show how planning of what each stage shows first was done and no colour or type choices were made yet.
01
Log in
03
Home
02
Schedule
Schedule runs long on purpose. It is the one screen people scroll, so every other screen stays short enough to read in a glance.
04
In session
06
Ask and Offer
05
Break
Break is the busiest stage. Crowd, next session and matches share one screen so nobody has to hunt between rooms. It also has a toggle option to view the crowd map and see where people are.
07
Crowd map
08
Leaving: Recap
03 · Design · Final screens
Eight screens from the vibecoded prototype, in the order an attendee meets them. Shown at the app’s real proportions.
01
Log in
02
Welcome
03
Schedule
04
Home
05
In session
06
Break
07
Ask and Offer
08
Leaving: Recap
04 · Features · Home
Live ticker: changes scroll past in orange.
Next session: title, room and a big countdown.
View schedule: jump between the five days in one tap.
Session card: flips to show the brief and speaker.
Ask + Offer: two pieces that fit together.
Quick actions: the current stage grows to show its name.
04 · Features · Light and dark
System
Light
Dark
04 · Features · Alerts
It drops in from the top of whatever you are doing, the moment it happens.
Room 1 · 11:00
→
Hall B · 11:30
The alert slides in over whatever you are doing.
!
Room changed
Workshop is now in Hall B
04 · Features · Lorem, the assistant
Where is it?
Room changes
Pick a session
What next?
04 · Features · Ask and Offer
Walking up to a stranger is the hard part, so the app does the first step for you.
1
Start of the day
Add one thing you’re looking for (your ask) and one thing you can help with (your offer).
2
In the break
The app suggests people whose asks and offers match yours.
3
Swipe
Meet or skip, like a card. Nobody sees a skip.
4
Both say meet
A short meeting is booked for that break, with a spot to find each other.
05 · The design system
Graphite and soft linen do most of the work, so colour stays rare. Bold shapes and drop shadows make it feel tactile and easy with one thumb.
One font. A few loud colours.
DM Sans
Regular · Medium · SemiBold · Bold
Big, steady numbers for timers. Short labels you can read while walking.
Colour, by how much of the screen it covers
60%
PRIMARY
Graphite · #2C2E2E
App background in dark theme. Almost every screen sits on it.
15%
PRIMARY
Slate · #3B3E3E
Cards, sheets and the navigation capsule.
10%
SECONDARY
Soft Linen · #E8EDDF
Text on dark, and the light-theme background.
6%
SECONDARY
Light Blue · #ADD8E6
Default buttons, info states and Offer.
4%
ACCENT
Celadon · #ACE1AF
Confirm, active nav and Quiet crowd zones.
4%
ACCENT
Molten Orange · #E8601C
The main action, countdowns, Ask and alerts.
1%
ACCENT
Signal Rose · #FF5C7A
Errors and Busy crowd zones only.
Percentages are the share of screen area set in the UXIndia design system: 60 · 15 · 10 for the base, accents kept small so they stay loud.
Primary button: presses down and springs back.
Icon buttons: Google, Apple and Microsoft sign-in.
06 · Reflection
next: volunteer and speaker modes, tested at the next edition ✿
© 2026 Kashvi Singhal