CarCare Diary

I started from a practical problem: vehicle information is scattered across receipts, messages and memory, and recurring maintenance is easy to defer until something fails.

I researched existing apps and habits, narrowed the opportunity to a record people would actually maintain, and defined an MVP that prioritised clarity over feature breadth.

I owned the information architecture, core flows, interface design and product direction - aiming to reduce the effort of logging activity and make the vehicle record feel like the centre of the product, not a side form.

After launch, a central challenge appeared: many people could add a vehicle and initial information but did not always return to record new activity.

I ran user interviews, read feedback and looked at behaviour patterns to hypothesise where activation and retention friction might be - especially around the first meaningful record after setup.

That led to ongoing work on onboarding, in-product guidance, simpler paths into logging, and reminder and re-engagement strategies.

I extended my role beyond conventional design and used AI-assisted development to build and maintain production software.

With Cursor and coding models I implement functionality, work through architectural decisions, debug issues, iterate on UX details and prepare store releases - in React Native, Expo, TypeScript and Supabase.

That lets me move directly between design, implementation and testing. The AI is how I build and maintain the product. The product itself is a vehicle record.

Shipping the application was only part of the challenge. I also took responsibility for attracting users, communicating value and testing monetisation.

That included Apple Search Ads, creative experiments, custom product pages, App Store optimisation, localization and subscription pricing.

I tracked spend, impressions, taps and installs by campaign, and I paired that with an activation funnel: a device registered, a vehicle added, a log created, and whether that became a purchase.

Reading those two views together changed what I tested next in positioning, onboarding and the path to the first record.

The product began with individual vehicle owners, but multi-vehicle use cases - including small businesses - suggested a different positioning and feature emphasis.

I expanded public messaging and in-product flows toward fleet-style needs, including dedicated landing pages on the CarCare Diary site for US fleet and fleet-management audiences.

Separately, I am developing an AI-assisted go-to-market workflow to research prospective companies, qualify fit and prepare personalised outreach. That workflow is still in development.