Odomtr

• 

  Fill-ups chart, and manual adding of Fill-up data.

• 

  The list of Fill-ups, showing swipe functionality to edit or delete.

• 

  Onboarding flow, quickly add cars via VIN photos!

• 

  Main home page with two cars populated. Note quick access to fill-ups, most commonly used feature.

• 

  The maintenance screen, showing summerizations of the mechanic reports, as well as buttons to view the raw PDF and share the PDF as well!

Inspiration

I'm a car guy, and was using my competition to track my car. I absolutely hated how many taps and input fields I needed to do in order to do something as simple as tracking a fuel fill-up. The app I was using at the time required 5 separate screen taps in order to get to the fill-up screen. So I decided I could do better.

What it does

Odomtr allows you to track your fuel mileage, and maintenance records of your car via taking photos (for fill-ups) or scanning in documents (for full on mechanic maintenance records) and then we use AI to parse records to make it so that you don't have to manually input a ton of data.

To get started, all you need to do is take a photo of your door card of your car with your VIN, using that, we fill out your year, make, model, and fuel type for you.

The ideal scenario for a fill-up for example is open the app, and with two photos (one of the odometer and one of the gas pump/receipt) you can fully gather all the data for a fill-up to track.

The maintenance record uses a full on document scanner that allows you to take multiple page document scans and creates a PDF that is stored locally and in the cloud for your records before sending off for parsing and summarization, breaking down individual costs, total costs, when and where the work was done, and more.

How we built it

The app is a React Native app that allows for both iOS and Android development with barely any platform specific code, with a Convex back end. This workflow has enabled incredible velocity and I've been insanely happy with it.

Challenges we ran into

I iterated through at least 3 different libraries and spent probably over a week of work iterating on a chart solution for fuel efficiency, I just couldn't find one that I really liked. But I'm quite happy with what I landed on.

Beyond that, a lot of the normal things, dealing with Apple's App Store submission process is an absolute pain.

Accomplishments that we're proud of

Is it a cop out to say "everything"? This is my first mobile app of my own, and I'm insanely proud of what I've done so far. Some of the highlights is how well the document scanning works and the charts for fuel mileage.

What we learned

A whole lot about react native, Convex, and React in general. I've learned a ton about how to write an app for offline use, live updating, and performance optimizations.

What's next for Odomtr

Polish and features! I already have a backlog that will keep me busy for months. I haven't really gone into "promotion mode" yet as there are still some core features I'd like to get done before doing so. Next big two features are search of your records and then a flow for folks that DIY their work instead of taking it to a mechanic. After those are done I imagine I'll be seriously putting in a marketing effort.

Built With

• ai
• convex
• gemini
• react-native