NontonNyaman — Project

App start & identity

Here’s the start screen and logo we shipped for the first public demo.

NontonNyaman — start page and logo

Why I built this. I love the energy of live sports, but in our early research it was obvious that the experience isn’t equal for everyone. Accessibility details are scattered, staff are stretched, and moving from A to B inside a stadium can be stressful if you use a wheelchair or walker. NontonNyaman (“comfortable watching” in Bahasa Indonesia) is my team’s attempt to fix that, a companion app that puts navigation, assistance, and information in one place for mobility-impaired fans.

What the app does. Pick your stadium, choose a destination like an accessible bathroom, ramp, or nearest exit, and the app guides you with clear directions. If something goes wrong, there’s an emergency button to reach stadium support immediately, and a general “request assistance” flow that notifies trained staff to come to you. Profiles store only the essentials, name and mobility needs, so staff can help appropriately.

How we got there. We mixed desk research with fieldwork: five interviews with mobility-impaired spectators, on-site surveys at Suncorp and The Gabba to map key facilities, and a review of the market (Ticketmaster, Ticketek, Eventbrite). The gap was consistent across sources: accessibility info is shallow, navigation is ad-hoc, and assistance is reactive. We designed to fill that gap.

Exhibition demo

A short clip from the on‑campus exhibition where we walked people through navigation, assistance, and profiles.

Research & methodology

We used a mixed-methods approach:

Literature review: what “good” accessibility looks like in stadia and law (e.g., ADA adherence, trained staff, wayfinding).
Market comparison: popular event apps lack depth on accessibility and proactive assistance.
Interviews: validated needs like emergency assistance, direct staff contact, and private escalation (alert staff, not strangers).
On-site survey: mapped facility coordinates (exits, ramps, bathrooms) to power navigation.

Key features

Stadium navigation: searchable stadiums and one-tap routing to accessible facilities.
Emergency assist: dedicated button to contact stadium emergency support fast.
Request assistance: notify designated staff who come to your location.
User profile: minimal data (name, mobility details) so staff can help effectively.
News & stays: optional feed and nearby accommodation suggestions for traveling fans.

Tech choices

Frontend: Flutter (Dart) for a fast, accessible mobile UI.
Backend: Python + Django with ORM, auth, and admin out of the box.
Data: Stadium facility coordinates (lat/long) stored for routing.
Infra: GitHub for version control; Heroku for easy deploys to staging.

Safety & respect

Ethics: design for inclusion; support assistive tech; avoid dark patterns.
Security: lean on Django hardening and encrypted storage for sensitive bits.
Privacy: follow Australia’s APPs, consent, data minimisation, and encryption of sensitive info.
Risk planning: identified technical and team risks and tracked mitigations.

Design snapshots

Here are selected screens from the NontonNyaman app design. (All assets live in ./assets/images/nontonnyaman.)

Where it landed

Usability tests were encouraging: clearer wayfinding reduced anxiety, and direct staff contact felt safer than broadcasting for help. There’s still a long road — better indoor positioning, richer facility data, and deeper partnerships with venues — but this project proved the value: accessibility isn’t a “nice to have”; it’s the path to a better game-day for everyone.

← Back to Projects

Technical documentation

If you want the full deep dive — research, features, tech stack, and evaluations — read or download the PDF.

Open PDF (opens in a new tab)