Rehab Roshen

How we researched

• Semi-structured interviews, 15–20 minutes each, with 5 residents of integrated neighborhoods.
• What motivates joining an event? What blocks tournament sign-ups? What builds neighborhood belonging?

What we heard

• Disconnection — residents want local activities but have no central hub.
• Friction — event registration is confusing and fragmented.
• Motivation — clear rules, progress tracking, and team play drive engagement.

8 user stories, 3 clusters

• Ease & clarity — find a tournament fast, know the rules before registering.
• Casual vs. competitive — room for fun players and stat-driven ones.
• Social play — join with friends, discover challenges nearby.

A 4-tab architecture

• Home — today's tournaments, community map, leaderboards, suggestions.
• The Arena — categorized tournaments and open challenges.
• My Tournaments — upcoming and past events.
• Profile — stats, achievements, accessibility, settings.

Designers × developers, day one

We worked in tight sync with the two Flutter developers from the start, so every component we drew was realistic for a one-week build. As UX Analyst I ran the rapid sketching sessions — refining screen structure, hierarchy, and component placement on the spot.

Two calls that shaped the app

• Frictionless onboarding — residents reach the real experience in seconds.
• A community map view that grounds digital events in physical neighborhood spaces.

Developer handoff

Developer-ready Figma frames, tokenized assets, and clear interactive-state specs went straight to the Flutter team — and I sat with them for real-time UI debugging so the coded app matched the design pixel-for-pixel.

A fully functional Flutter prototype and pitch, delivered in seven days — awarded for teamwork, design execution, and real impact on community quality of life.