01
The schedule, navigable
Sessions by day and track, filterable, with a detail screen for the speaker and the room. A saved agenda, so an attendee sees their day rather than everyone’s.
Use case — native mobile app
Build the companion app for your conference or festival
Event apps are quoted per event and arrive as a rebranded shell two weeks before the doors open. Meanwhile the schedule is a PDF that everyone screenshots, and a room change reaches attendees through a sign taped to a door. The app you need is the schedule, a way to save what you are attending, a map, and one channel that can interrupt a thousand people at once — which is a push notification, which means it has to be a real app.
- Real React Native and Expo — native navigation and native components, not a web view
- Push announcements to every attendee via expo-notifications
- Personal agenda saved on the device, readable offline
- Schedule and speakers in your own Supabase project
- Scan a QR code and run it on your own phone through Expo Go while you build
- Cloud builds through EAS reach TestFlight and Play internal testing
Start with this prompt
Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.
Build a native mobile app for a two-day conference. Schedule: sessions grouped by day, with a track filter and the time and room on each row. Tapping through shows the description, the speaker with a photo and bio, and a Save to my agenda button. My agenda: everything I saved, in time order, with a warning when two sessions clash. Speakers: a browsable list with profiles. Info: a venue map image, wifi details, and the code of conduct. Push an announcement to everyone when an organiser posts one — for example a room change. Data in Supabase: sessions, speakers, tracks and announcements. My saved agenda lives on the device so it works without wifi at the venue. Seed two days of sessions across three tracks.
What to build next
- Add a per-session rating and comment after it ends.
- Add a QR badge scan to swap details with another attendee.
- Add sponsor pages with logos and links.
Native mobile app
What the build actually consists of
For conference organisers, festivals, meetups and internal company events who want their own app for the price of building it once. If the event is a single-track afternoon, a web page is enough — this pays off when the schedule has parallel tracks and can change.
02
The venue, and the moment
A map of the venue, and push announcements through expo-notifications for room changes and last calls — the one thing a PDF and a website cannot do at all.
03
Yours after the event
The content is data in your own Supabase project, so next year is an update rather than a new quote. The React Native code is yours, exportable to GitHub.
What you get
- A full schedule by day and track, with filters
- Session detail with speaker, room and description
- A personal agenda from the sessions an attendee saves
- A venue map and practical information
- Push announcements for changes and last calls
Describe it. Watch it build.
Paste the prompt above and scan the QR code when the build lands — the app runs on your own phone while you are still changing it. The free plan needs no card.
Start buildingFAQ
Questions, answered.
Will the app work when the venue wifi collapses?+
The saved agenda is on the device, so an attendee can always see their own day. Ask for the full schedule to be cached locally too and it will be — worth stating in the prompt, because venue connectivity is the normal failure mode for event apps.
Can we update the schedule without rebuilding the app?+
Yes — the schedule is data in your Supabase project, so a change there reaches every phone. Build a small web admin screen in the same account and your team can edit sessions without touching the app.
Can we get it on the stores before the event?+
Plan for it. EAS builds reach TestFlight and Play internal testing quickly, which is fine for staff and speakers; a public store listing is your own submission from your own developer accounts and Apple’s review takes time, so do not leave it to the final week.