50 Screens, 25 Tables, One Solo Developer, One Month

Hackathon-grade apps usually die in the second week of use because the demo path is the only path the developer ever exercised. With Roamly I wanted to see how close to production-shaped a solo build could get in a single contest cycle.

What ended up on the table

• 50+ React Native screens covering swipe-based discovery, real-time chat, group features, voice prompts, and a community-vouched verification system.
• A modular service layer of 15+ services and a Supabase backend with 25+ tables protected by Row Level Security and 20+ migrations.
• A high-performance swipe queue with background processing, local counters for instant feedback, smart caching, and Reanimated-based UI to keep heavy interactions at 60fps.
• Convergence detection for nomads heading to the same locations, multi-intent priority filtering, and compatibility scoring based on shared interests and lifestyle.
• RevenueCat feature gating, real-time chat sync, theme engine with instant switching across 5+ schemes, and safety tooling for blocking, reporting, and face verification.

Why RLS was the unblocker, not the bottleneck

Supabase Row Level Security gets a reputation for slowing you down on day one. It's the opposite over a project's lifetime: every new screen ships with the security model already in place, every join clears the same policy filter, and you never write 'check the user' in code. With 25+ tables, that discipline was the only reason the codebase stayed sane.

What I cut

Voice rooms, gift economy, and a 'pen-pal mode' all sat on the wall. None survived the cut to ship. The product is stronger because the features that did ship are the ones a nomad would actually open the app for: who's heading where I'm going, can I trust them, can we talk.