Inspiration
Vanlife and digital nomad communities are growing, but the tooling is still fragmented. People use one app for meeting others, another for groups, another for expert advice, and random chats for technical build help.
Nomad Connect came from that gap: one app where nomads can discover people nearby, build trusted connections, and get practical help for vanlife decisions.
What it does
Nomad Connect is a mobile app for vanlifers and traveling nomads that combines:
- Profile + travel verification flow with badge-based trust signals
- Social discovery and matching (including radar-style discovery)
- Direct and activity-based chat
- Activity creation and community meetups
- AI support features for van-build guidance, photo analysis, and cost estimation
- Expert Marketplace with paid consultations
- Subscription tiers (
Explorer,Adventurer,Lifetime) and one-time expert products (expert_50,expert_75,expert_100)
How we built it
We built Nomad Connect as a full-stack mobile system:
- Frontend: Expo + React Native + context-based state management
- Backend: Node.js + Express API routes
- Database/Auth: Supabase
- Monetization: RevenueCat connected to Google Play products/subscriptions
- Core flows: Auth/session, profile state, matching/chat, activities, expert bookings, subscription gating
We designed around a practical architecture: fast local state + background refresh. For example, profile/session bootstrap was optimized so users can enter the app quickly while verification status refreshes asynchronously.
Challenges we ran into
- Monetization mapping complexity: Product IDs and entitlement IDs had to match exactly across app code, RevenueCat, and Play Console. Small mismatches broke tier access.
- Expert purchase routing: Initially one expert product path worked reliably while others failed due to strict ID/rate selection logic.
- Startup loading delays: On mobile reopen, auth and verification checks could block rendering and leave users on a spinner.
- State synchronization: Keeping subscription/auth state consistent across app restarts and listener callbacks required careful handling of async race conditions.
Accomplishments that we're proud of
- Shipping a working end-to-end mobile platform instead of only a prototype UI
- Integrating recurring subscriptions and one-time purchases in the same app
- Building a usable expert booking and payment flow
- Improving startup behavior by unblocking UI from slow verification requests
- Turning a broad idea into a focused product with clear audience fit
What we learned
- Product IDs and entitlement modeling are as important as code quality in monetized apps.
- “Works on one test case” is not enough for payment logic; matching and fallback strategy must be robust.
- Mobile UX quality depends heavily on startup orchestration, not just screen design.
- For community products, trust and safety features are core infrastructure, not optional add-ons.
What's next for Nomad Connect
- Improve onboarding personalization by user type (new nomad, experienced van builder, social-first traveler)
- Expand expert marketplace quality controls (reviews, response SLAs, structured consultation packages)
- Add stronger local community mechanics (recurring events, group channels, reputation signals)
- Deepen safety tooling (meetup check-ins, trusted contact flows)
- Strengthen analytics and conversion tracking for monetization funnels
We’re continuing to build Nomad Connect as a practical operating layer for nomad life: meet the right people, make better decisions, and move from online discovery to real-world outcomes.
Built With
- api
- asyncstorage
- console
- drizzle
- drizzle-kit
- expo.io
- express.js
- groq
- javascript
- native
- navigation
- node.js
- openai
- orm
- play
- postgresql
- query
- react
- revenuecat
- router
- supabase
- tanstack
- typescript
Log in or sign up for Devpost to join the conversation.