Roadsy

Your private driving journal. Record your trips, understand your habits, and rediscover your roads.

Comment

Roadsy turns everyday driving into a private, visual journal. Record a trip, revisit its route, understand the evidence behind your driving score, and see the roads you have explored over time.

Inspiration

A drive can be a daily commute, a weekend escape, or a route worth remembering. Once it ends, it is easy to lose the details: where you went, how the journey felt, and how it fits into your driving over time.

Roadsy brings those journeys together in a personal journal. The idea is to make driving history useful and interesting while giving people control over sensitive location data. A saved drive should offer more than a line on a map. It should help someone revisit a journey, understand their habits, and see their own progress.

What it does

Roadsy combines trip recording, a visual driving journal, and personal exploration.

  • Record and organize drives. Save routes, distance, and duration, then add notes and vehicle labels or correct a trip recorded as a passenger.
  • Review a journey. Explore the route and driving feedback, with breakdowns for smoothness, braking, acceleration, and cornering. Data confidence helps explain what the phone actually recorded.
  • See a bigger picture. Bring lifetime totals, accumulated road coverage, achievements, and monthly summaries into one place.
  • Revisit the details with Pro. Replay routes, explore older trip details, and review longer-term score trends and richer insights.
  • Keep control of the data. Use encrypted local storage, export records, manage deletion, and choose whether to enable cloud backup. Sharing includes controls that reduce the amount of route information disclosed.

The free experience includes manual recording, trip details from the most recent 72 hours, lifetime totals, accumulated map, achievements, and core export and privacy controls. Older journeys remain stored when their details become locked. Roadsy Pro adds automatic recording, access to retained older trip details, replay, advanced insights, and optional cloud backup.

Driving feedback is intended for reflection after a trip. Scores depend on phone signals and their quality; they are not an insurance rating or proof of safe driving.

How it was built

Roadsy is a native Android app built with Kotlin and Jetpack Compose. Its domain layer handles the journal, scoring, route geometry, coverage, achievements, and privacy trimming.

Recording writes to an encrypted local journal so that trip history does not depend on a continuous network connection. Mapping combines native map interfaces with road data used to calculate personal exploration. Supabase provides account and backend services, including authorization for backup and subscription access.

RevenueCat and monetization

Roadsy uses a freemium subscription model. Pro adds ongoing convenience and deeper history while core recording and privacy controls remain available for free.

RevenueCat is integrated into the Pro subscription flow. The Android app retrieves current offerings, displays store-provided subscription options, and handles purchases and restores. Trial messaging follows the eligible offer supplied by the store instead of assuming every person qualifies for the same promotion.

Billing is tied to the authenticated account. The RevenueCat customer identity uses the same account identifier as the backend, and backend reconciliation determines Pro access. The implementation handles pending purchases, cancellation, restore, and account changes, rather than treating a local purchase callback as the final authority.

Challenges encountered

Reliable recording was a central engineering challenge. Location access can be interrupted, providers can become unavailable, and background execution is constrained. Roadsy needs to preserve an active journal through temporary interruptions and avoid turning a recording failure into an incorrectly completed drive.

Another challenge was being conservative with GPS evidence. Noisy or missing samples can distort a route, driving feedback, or road coverage. The implementation must account for uncertainty rather than award progress or present precise conclusions that the data cannot support.

Privacy also affects the whole product. Storage, sharing, export, backup, deletion, and account switching all need consistent ownership rules. Subscription handling adds a similar challenge: purchases and entitlements must stay attached to the correct person through restores and account changes.

Accomplishments

The project brings recording, trip review, personal road coverage, and subscription access into a coherent mobile workflow. Privacy is part of the architecture through encrypted local storage, controlled backup, and deliberate sharing.

The RevenueCat integration goes beyond displaying a paywall. It connects store offerings, authenticated identity, purchase and restore states, and backend entitlement checks to the features that Pro unlocks.

Behavioral tests cover areas where correctness matters, including recording persistence, scoring evidence, coverage calculations, ownership, and privacy.

Lessons from development

A useful driving journal depends on trust in the record. Clear recovery states and durable storage matter as much as the map itself. Driving feedback is more useful when it explains its evidence and limitations, and location privacy needs to shape features from the beginning.

Subscription design also belongs in the product architecture. Account identity, entitlement checks, restore behavior, and feature access must agree so that purchasing Pro creates a predictable experience.

What's next for Roadsy

Roadsy will continue to grow around the driving journal: richer long-term insights, more useful monthly recaps, and deeper ways to explore the roads that make up a person's history. Continued improvements to recording reliability, battery use, and the Android experience will make it easier to keep that history without extra effort.

Built With

Share this project:

Updates

Submission history