Build and ship a truck driver profit calculator app as a non-developer

A non-developer rode in a truck for two weeks to find a problem, then had Claude Code build a React Native profit calculator for drivers; six months on it has about 200 downloads and 3 paying users.

Done withClaude CodeinSupabase· Nov 12, 2026

What they did

The poster, who does not call themselves a developer, spent two weeks as a passenger with a truck driver looking for a real problem. They saw that drivers paid per mile or by a share of the load rarely know what they actually earn, so they built Truck Driver Helper, a calculator that shows one profit number. Claude Code wrote nearly all the code: a React Native and Expo app, a Supabase backend, RevenueCat subscriptions, and an admin panel with signup, usage and payment analytics. It also helped fix two App Store rejections, one for a paywall that did not show price, duration and terms links, and one for a missing reviewer test account. The poster gave it one small task per prompt, tested on a real phone after each change, and pasted exact error messages back.

How it went

The app shipped to the stores. Six months in it has about 200 downloads, 3 paying users and $15 a month in revenue. Two of the paying users were drivers met on the trip. The poster still had to handle the feel of the app on a real device, where swipes felt wrong even when the code worked, catch regressions (one toggle broke about five times), and work out what Apple's reviewers wanted. Their verdict: building was the easy part, finding users is the real work.

Worth knowing

A commenter who works in enterprise software questioned how a non-developer can judge data handling and security in an app built this way; the poster did not say how they checked it. Expect App Store review to ask for clear paywall terms and a test account.

Try it

With Claude Code· 6 parts to fill in

Help me build a [platform] app for [audience] that does [one core job] in [project folder], using [stack, e.g. React Native, Expo and Supabase]. I am not a developer, so take one small task at a time, explain what you changed in plain words, and tell me exactly what to test on my phone before we move on. When I paste an error, fix that error only. Before submitting to [App Store or Play Store], check the paywall shows price, duration and terms links and that reviewers have a test account. List anything that touches user data or security and explain the risk before you build it. Stop after each task and wait for my test result.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related