Tindcar — Swiping for Cars and Their Owners
Tindcar brings the familiar swipe mechanic of dating apps to the world of cars. Users build a garage, flip through cards of vehicles and owners, match, and chat — a community of car enthusiasts built around their vehicles.
The Problem
Car enthusiast communities live scattered — across forums, groups, and comment threads under listings. Finding an owner of the same model, a fan of the same build, or simply someone to talk cars with is surprisingly hard. There's no single place where connections are built around the vehicles themselves.
Meanwhile, the swipe mechanic has long become a universal language of connection: millions grasp it intuitively. The question was how to carry that simple, familiar interaction into the car niche — and do it with secure sign-in and a dependable foundation.
What We Built
We're building Tindcar as a Flutter app for iOS and Android with a .NET 10 and MongoDB backend. A user signs in with Google or Apple, builds their own garage of cars, flips through cards of other vehicles and owners, likes the ones that click — and a private chat opens on a mutual match.
The foundation is laid around secure authentication: identity is keyed on the provider-and-id pair rather than the email, which works correctly even with Apple's private-relay addresses. A unique index guarantees one account per identity. On top of that base, the product verticals — garage, swipes, matches, and chat — are built out step by step.
Key Capabilities
Swipe Matching
The familiar swipe mechanic, carried over to cars. Flip through cards of vehicles and owners, like the ones that resonate, and wait for a mutual match.
Personal Garage
Every user builds their own garage: adding their cars with photos and details. It's the profile that matches and conversations are built around.
Google & Apple Sign-In
Log in with Google or Apple ID — no clumsy forms. Identity is keyed on the provider, not the email, which is safe for Apple's private-relay addresses.
Post-Match Chat
Match with someone and a private chat opens. Owners of the same model — or simply fellow enthusiasts — find each other and start talking.
One Account per Provider
A unique index guarantees one account per provider identity. No duplicates, no confusion across multiple logins.
Solid Backend
JWT authentication with refresh tokens, a clean layered architecture, and MongoDB underneath. Ready to scale swiping, matches, and chat.
Outcomes
Familiar Mechanic, New Niche
A swipe pattern millions already grasp intuitively opens an entirely new niche — a community of car enthusiasts built around their vehicles.
Safe Authentication
Google and Apple sign-in keyed on the provider removes passwords and protects privacy — especially with Apple's private-relay addresses.
A Foundation to Scale
The clean .NET 10 and MongoDB backend is laid out to add verticals — swipes, matches, chat — without rewriting the foundation.
Why It Matters
Tindcar shows how a proven interaction pattern can be carried into a fresh niche to deliver a product that feels familiar from the first touch. Users have nothing to learn — they already know how to swipe.
For Codevia, it's another example of a mobile product built from the foundation up: secure authentication and clean architecture first, then the features that bring the app to life.