Real mobile onboarding
Five-step first-run flow: goals, workspace context, topics, timing. State survives anonymous-to-signed-in transitions without data loss.
Expo · Convex · RevenueCat · Open source
ShipHappens is a production-ready Expo starter — auth, Convex backend, RevenueCat paywalls, and onboarding all wired and tested. Skip the infrastructure sprint and stop burning AI tokens on problems you've already solved.
The hidden cost
Auth, subscriptions, backend state, onboarding, and App Store constraints all need to work together. Here's how long that takes — and how many AI tokens it burns — from scratch:
What you get
ShipHappens is designed to be edited, renamed, and shipped. Production defaults with separate dev controls so you can test every monetization state without faking backend data.
Five-step first-run flow: goals, workspace context, topics, timing. State survives anonymous-to-signed-in transitions without data loss.
RevenueCat wired end-to-end. Annual/monthly packages, entitlement sync, restore purchases, and webhook handling already modeled.
Native redirect auth, Convex JWT validation, protected functions, server-derived user IDs, and account deletion. Clerk and Logto both supported.
Ships with an authenticated task tracker: ownership checks, free-tier usage limits, and premium bypass. Something real to build from.
Toggle free vs premium, reset onboarding, replay the App Store review demo, and test every monetization state locally in seconds.
Legal links, feedback, push-token registration, app-open tracking, analytics identity, EAS env sync, and setup docs already in the codebase.
AI-ready codebase
The fastest AI coding workflow isn't a blank prompt — it's a coherent repo with consistent naming, clear auth boundaries, backend rules, and predictable extension points. Stop burning tokens re-explaining your stack.
Add a premium-only habit streak feature using the existing Convex auth helper, RevenueCat entitlement state, and onboarding preferences.Inside the repo
Every piece your subscription app needs — mobile client, Convex backend, web surface, shared config, docs, and scripts — structured around a real task app and ready to rename.
Clone the repoExpo mobile app with typed routes and React Compiler enabled
Convex backend: users, tasks, subscriptions, feedback, push tokens
Clerk or Logto native auth wired into Convex custom JWT auth
RevenueCat paywall, packages, entitlement sync, and webhook examples
Onboarding flow with local persistence and signed-in migration
Profile screen: feedback, legal links, account deletion, dev toggles
Next.js web surface for marketing, support, privacy, and terms
Admin/dev scripts for user cleanup and RevenueCat product setup
Docs for local setup, auth/Convex integration, and webhook testing
Pricing · Open source
ShipHappens is fully open source. Clone the repo and start building — no payment, no wait.
Starter
Normally$199
FREEEverything you need to ship your first paid app.
Open source · free forever
Pro
Normally$249
FREEBuild multiple products. Get updates. Ship faster every time.
Open source · free forever
Get the full codebase on GitHub. Fork it, star it, ship your app.
Support me on Ko-fiFAQ
Clone or fork the public GitHub repo, follow the setup docs, and add your Convex, Clerk, and RevenueCat keys. No payment or invite required.
No. The value is the integration work: native auth, Convex data ownership, subscription state, onboarding, paywall flow, analytics, feedback, and release-adjacent tooling. Screens are secondary.
The tiers reflect what used to be paid plans. Everything is now included in the open-source repo — pick whichever card matches how you think about your project.
Both are supported. The repo includes integration examples for Clerk and Logto wired into Convex custom JWT auth. You pick the one that fits your stack.
Yes. The code is structured around provider boundaries. You can swap pieces, but the included defaults are wired and documented so you can move fast immediately.
Yes. A task tracker with authenticated ownership, a free open-task limit, and premium entitlement bypass — so you can see every integration working together before you start building.
Ready to ship?
Skip weeks of auth, paywall, and backend plumbing. Stop burning AI tokens on problems you've already solved. Start from a production-ready foundation.