Inspiration
Van life looks social from the outside, but in reality it can be isolating. Most people on the road rely on Instagram, random Facebook groups, or campground chats to meet others. None of these are built specifically for van-lifers who want intentional, safe connections.
I wanted to build something that feels more private and trusted. A space where you know the people inside are actually part of the community. Not a swipe app. Not a public social feed. A focused network for people living and traveling on the road.
That’s how Vano started. A simple idea: help van-lifers find the right people nearby, based on what they are actually looking for.
Some want friends to explore with. Some want a travel companion for the next city. Some need help with their van build.
The product is built around that clarity of intent.
What I Learned
The biggest insight was that trust matters more than scale in niche communities.
Instead of open access, Vano uses an application and approval system. That small friction improves quality and makes the space feel safer.
I also learned how powerful simple UX can be. Clear intent filters and structured profiles reduce noise. When people know why they are connecting, conversations start more naturally.
From a product perspective, this project reinforced the importance of shipping a focused MVP. Clean routing, stable auth, and clear feature gating are more important than adding too many features.
How I Built It
Vano is a cross platform mobile app built using FlutterFlow.
Authentication is handled through Firebase Auth using email login. User data is stored in Firestore. Profile photos are uploaded to Firebase Storage. RevenueCat is integrated for subscription management and entitlement based access.
Each user has a structured document in Firestore that includes profile details, approval status, and selected travel intents.
The access flow is straightforward:
If a user has not applied, they see the application screen. If they have applied but are not approved, they see a waiting screen. Once approved, they enter the discovery experience.
Premium features such as Builder Help are controlled through RevenueCat entitlements, allowing feature level access without changing the core experience.
Challenges
One of the main challenges was handling conditional routing properly. The app needed to respond accurately to application status and approval flags without breaking the user flow.
Another challenge was setting up Firestore rules correctly so users can only modify their own data while keeping discovery safe and readable.
Entitlement based feature control also required careful state handling to ensure premium access behaves correctly across sessions.
Finally, scope management was critical. It was tempting to build advanced matching, moderation systems, and push notifications, but the goal was to ship a solid, installable MVP.
Why Vano
Van life is about movement, but meaningful connection should not feel random or unsafe.
Vano is designed as a trusted mobile community where people on the road can find others nearby, based on shared intent and mutual interest.
The MVP proves that a focused, gated, and monetizable van-life network can be built, shipped, and tested as a real product.
Log in or sign up for Devpost to join the conversation.