Vantly - Devpost Story

Inspiration

The van life and digital nomad movement is exploding—with over 1 million van lifers in the US alone—yet there's no dedicated app for this community. Nomads are scattered across Facebook groups, Reddit threads, and general social networks, making it hard to find compatible travel companions, discover vetted camping spots, or connect with like-minded people in their area.

As an AI engineer who's always been fascinated by niche communities, I saw Shipyard as the perfect opportunity to learn mobile development while building something meaningful. The van life community deserves purpose-built infrastructure, not fragmented workarounds.

What it does

Vantly is a mobile-first social platform that helps van lifers and digital nomads: 🎯 Discover Compatible Travel Companions - Tinder-style swipe matching based on travel style, interests, and current location 🌍 Build Community - Share experiences, tips, and photos through BuilderHub and Activities feeds with commenting and engagement 🛠️ Manage Nomadic Life - Track expenses, create location-based checklists, and access travel tools 💎 Premium Features - "Vantly Pro" subscription ($9.99/month) unlocks unlimited swipes, advanced filters, priority visibility, and enhanced tools via RevenueCat integration

The app is live on Google Play Internal Testing, built with React Native, Supabase, and RevenueCat for sustainable monetization.

How we built it

Tech Stack:

• Frontend: React Native + Expo for cross-platform development
• Backend: Supabase (PostgreSQL, Auth, Real-time, Storage)
• Monetization: RevenueCat SDK with Google Play subscriptions
• Build & Deploy: EAS Build for production Android App Bundle (.aab)
• Styling: NativeWind (TailwindCSS for React Native)
• Navigation: React Navigation with bottom tabs and stack navigators Architecture:
• Context API for global state (Subscription, Authentication)
• Service layer for API abstraction (RevenueCat, Supabase)
• Row-Level Security (RLS) on all database tables
• Production-ready subscription flow with entitlements and offerings Development Process:
• Designed core user flows (onboarding → discovery → community → tools)
• Built authentication with Supabase Auth
• Implemented swipe matching with local state + Supabase backend
• Created community features (posts, activities, comments)
• Integrated RevenueCat with production API keys
• Configured Google Play subscriptions (monthly_premium)

7. Built and deployed via EAS to Internal Testing

Challenges we ran into

1. First Mobile App Ever 🚀
This was my first production mobile app! Coming from AI/ML and web development, I had to learn React Native, Expo, mobile navigation patterns, and native concepts in the hackathon timeframe. The Expo docs and community were lifesavers. 2. RevenueCat Service Account Setup 🔐
Setting up the full RevenueCat integration required understanding Google Play Console's service account credentials, product configuration, and entitlement architecture. The documentation was thorough, but coordinating multiple platforms (RevenueCat dashboard, Google Play Console, app code) was complex. I got the framework fully integrated, with service account credentials pending for complete activation. 3. EAS Build Learning Curve 📦
First time using EAS Build for production Android bundles. Learning about app signing, release channels, and .aab vs .apk distribution was challenging but valuable. 4. Time Management ⏰
Building a complete app with social features, tools, subscriptions, AND getting it production-ready in the hackathon window required ruthless prioritization. I focused on core MVP features and shipped a working product over a perfect one. 5. Real-time State Sync 🔄

Keeping local app state synchronized with Supabase real-time subscriptions while handling offline scenarios and optimistic updates was tricky, especially for the swipe matching logic.

Accomplishments that we're proud of

Shipped a WORKING Android app on Google Play Internal Testing - judges can actually install and use it! Built my first mobile app - Learned an entirely new domain (React Native, mobile patterns, distribution) during the hackathon Complete RevenueCat integration - Production API keys, subscription products configured in Google Play Console, entitlements and offerings set up, paywall implemented Full user journey - Onboarding → Authentication → Profile Setup → Discovery → Community → Tools → Subscription - every core flow works Real-time social features - Implemented swipe matching, community posts, activities feed with Supabase real-time subscriptions Production-quality code - TypeScript throughout, proper service abstractions, security via RLS policies, clean component architecture Solved a real problem - Built for an underserved community (van lifers) with genuine needs, not a generic social app

Sustainable monetization - Designed a freemium model that adds value without being exploitative

What we learned

Technical Skills:

• React Native and Expo ecosystem from scratch
• Mobile app architecture patterns and navigation
• RevenueCat SDK integration (products, entitlements, offerings, purchase flows)
• Google Play Console setup (subscriptions, internal testing, distribution)
• EAS Build workflows for production deployments
• Mobile-specific UX considerations (gestures, bottom tabs, modals) Product Development:
• Ruthless feature prioritization under tight deadlines
• MVP thinking - what's essential vs nice-to-have
• Designing subscription paywalls that communicate value clearly
• Building for judges while keeping real users in mind Mobile Distribution:
• App signing and keystore management
• Internal testing tracks and tester management
• Production build configuration (.aab bundles, versioning) RevenueCat Deep Dive:
• Understanding the products → entitlements → offerings → packages hierarchy
• Service account credential requirements for platform integration
• Production vs test API keys and environment setup
• Feature gating based on entitlement checking Biggest Lesson: Shipping beats perfection. I could have spent weeks polishing details, but getting a working app in users' hands (even if it's beta testers) teaches you more than infinite planning. Shipyard's production requirements forced me to actually finish and deploy. --- ## What's next for Vantly ### Immediate (Post-Hackathon)
• Complete RevenueCat service account setup for full payment processing
• Add annual subscription tier ($79.99/year) for better LTV
• iOS version via TestFlight and App Store deployment
• App branding - Design and add proper logo/icon
• Enhanced animations and UI/UX polish ### Technical Improvements (Months 1-3)
• Upgrade matching algorithm - Replace rule-based matching with Google Maps integration for location-aware suggestions
• Offline sync - Critical for users with unstable network connections on the road
• Real-time messaging - Chat between matched users with push notifications
• Voice/video calls - Using Twilio or WebRTC for in-app communication
• Map view - Show nearby nomads and resources on an interactive map ### Feature Expansion (Months 3-6)
• Location reviews - User-generated reviews for campsites, parking spots, amenities
• Event creation - Community meetups and gatherings
• Profile verification - Safety and trust features
• Premium-only tools - Gate advanced expense analytics and planning tools behind subscription
• More travel tools - Route planning, packing checklists, weather integration ### Growth & Business (Months 6-12)
• Public beta launch on Google Play and App Store
• Influencer partnerships - Collaborate with van life creators for authentic growth
• Referral program - Organic user acquisition
• Content creator tools - Enable creators to share travel guides and monetize expertise
• Marketplace - Gear, services, and experiences for nomads ### Long-term Vision My dream is to be an entrepreneur and build a successful company. Vantly has real potential to become the essential platform for the nomadic lifestyle—not just a social app, but infrastructure for an entire community. I'd love the opportunity to grow this further, whether through:
• Continued development and organic growth
• Potential funding to accelerate feature development
• Partnership opportunities with van life brands/creators
• Possible acquisition by a company serving the travel/nomad market The van life community is real, growing, and underserved. With 1M+ van lifers in the US and expanding globally, there's a massive market opportunity. Shipyard gave me the perfect kick-start to build something meaningful. --- Testing Link: https://play.google.com/apps/internaltest/4700956857309762666 Built with: React Native | Expo | RevenueCat | Supabase | EAS Build | TypeScript | NativeWind

Built With

• appdev
• build
• eas
• expo.io
• native
• react
• revenuecat
• supabase
• typescript