JAM / Experience system

UI/UX design handout · Mobile app concept

Find your people.
Make some noise.

JAM helps musicians discover compatible people, turn “we should jam” into a specific session and keep playing together. This handout traces the decisions behind its midnight-blue, electric interface.

Session-first discoveryDeliberate confirmationShared planning
JAM music-community case study cover with app screensJAM · concept UI

01 / Product decisions

Discovery only matters when people can play.

Three explicit choices connect finding a match to a plan that musicians understand and can commit to.

01
01 / Discovery

Lead with a session.

A visible date, open slot and expectations make a jam actionable. Musicians remain an alternative discovery route.

02 / Commitment

Confirm deliberately.

Pending, accepted and confirmed are separate states. A material change to time or place asks for renewed confirmation.

03 / Spaces

Put the venue in the plan.

Space suggestions appear inside discovery and session coordination, where equipment, price and booking status are meaningful.

Three JAM design decisions and their tradeoffs
Decisions, tradeoffs and validation questions View full size ↗

02 / Visual foundations

A stage after dark.

Deep blues make music imagery feel immersive. Cyan, blue and a restrained magenta echo live performance without competing with session details.

02
Midnight#0B1024Base canvas
Stage blue#172342Cards and plans
Action blue#3158F8Primary actions
Electric cyan#55D5FFAccent and focus
Display / expressive but directDiscover.
Join. Play.

Bold sans-serif typography makes the next invitation immediately scannable.

Interface / useful details firstSat 19 Sep · 5–7 pm

Date, distance, slot and estimated cost are easier to compare when labels and numerals are consistent.

Token accuracyThese colour values and Inter rendering are presentation references approximating the supplied screens. Confirm exact design tokens and font files in the source before production use.

03 / Typography

Energy with useful detail.

Bold sans-serif headlines give JAM its performance energy; compact interface text keeps time, place, cost and participation easy to compare.

03
Display / headingFind your people. Make some noise.
Body / instructionSaturday · 5–7 pm · three musicians going
Metadata / statusSession details · Join request · My Jams
Font referenceInter is used here as a presentation reference to the supplied boards. Confirm final font files, sizes and weights in the source before build.

04 / Layout patterns

A rhythm across discovery and planning.

Repeated spacing, rounded cards and predictable states help the energetic visual language remain usable through practical coordination.

04
Spacing rhythm

Group, then separate.

Give session essentials their own scan path before secondary stories, tags and social context.

Corner language

Repeat familiar shapes.

Repeat card and control shapes across discovery, session detail and My Jams.

Interaction states

Make changes legible.

Joining, pending, confirmed and cancelled need distinct labels as well as visual treatment.

Reference, not final tokensSpacing bars, radii and state samples illustrate the pattern. Exact values and accessibility behaviour need source-file and device-level verification.

05 / Reusable UI

Make a possible jam feel real.

Components pair the energy of discovery with practical details and unmistakable commitment states.

05
Discovery filters

Start from availability.

SessionsMusicians
Availability · This weekend ⌄

People-first browsing remains available, but a session card reveals an immediate way to participate.

Session card

Show the commitment.

Indie after class · Drummer wantedSat 19 Sep · 5–7 pm · North CampusBeginner friendly · ₹200 est. / person

Location, time, style, open role and estimated cost belong in the decision, not hidden in chat.

Action & status

Request, then confirm.

Request slot →Open group chat
Pending → Accepted → Confirmed

Host acceptance and musician attendance are not the same event. Material plan changes should be explicit.

06 / Information architecture

Four places, one shared intention.

Primary navigation separates finding a session, planning it, staying connected and handling direct messages.

06
Discover

Find a fit

Sessions first, with filters and musician discovery as an alternate path.

My jams

Make a plan

Track requests, confirmed attendance, time, venue and group context.

Community

Keep playing

Stay connected after the first session without reducing the experience to a feed.

Inbox

Coordinate

Messages support a specific plan; they do not replace its visible status.

JAM information architecture diagram
Full information architecture View full size ↗

07 / First-jam flow

From interest to attendance.

A host’s response is followed by a separate participant confirmation, so everyone can see what still needs action.

07
Find a session→Check the fit→Request a slot→Host accepts→Confirm attendance→Play
JAM first-session user-flow diagram
First-jam flow View full size ↗
JAM musician journey board
Musician journey View full size ↗

08 / UX process

Structure before spectacle.

Concept themes and alternate layouts were compared before the visual treatment made the app feel like a live music space.

08
JAM provisional affinity mapping board
Affinity themes Enlarge ↗
JAM sketch wireframes
Sketch explorations Enlarge ↗
JAM low-fidelity discovery screens
Low-fidelity discovery Enlarge ↗
Evidence notePersonas, affinity notes, session data and journeys in this case study are illustrative hypotheses. The proposed benefits still need testing with musicians.

09 / Screen families

Discover. Coordinate. Return.

The final boards show the discovery, session-detail and My Jams experience, plus the practical details needed to make participation feel intentional.

09
JAM final discovery, session and My Jams screens
Core final screens View full size ↗
JAM scheduling screens
Scheduling and coordination View full size ↗
JAM recording-consent design board
Recording consent View full size ↗
01Discover

Find musicians and sessions by fit and locality.

02Session detail

Understand the music, people, timing and venue.

03Join flow

Make intent and participation status clear.

04Scheduling

Coordinate time, place and availability.

05My Jams

Return to upcoming plans and past activity.

06Recording consent

Keep permission explicit rather than implied.

10 / Visual direction

The feeling of a gig. The clarity of a plan.

The dark stage-like palette invites exploration, while the session flow needs quieter, more operational information.

10
Primary expression

Discovery / expressive

Deep blue and electric accents give artists, sessions and local music imagery an energetic setting.

Supporting discipline

Planning / practical

Dates, places, roles, expected costs and consent should remain legible and explicit before anyone commits.

JAM key design decisions and visual direction board
Visual source board View full size ↗
Concept directionThis visual treatment has not been validated through user testing or accessibility evaluation.

11 / Validation & next steps

Test the handoff from match to plan.

These are reasoned design choices, not claims of measured success.

11
Discoverability

Can a newcomer find a suitable jam?

Observe whether session-first results expose the details needed to explain why a session fits.

Commitment

Can members explain their status?

Test pending, accepted and confirmed states, including a revised plan that needs confirmation again.

Space & consent

Can a group plan responsibly?

Check whether equipment, cost, booking status and recording consent are understandable at the right moment.

JAM feedback and validation plan
Proposed validation View full size ↗