Local-First React Native (Expo) Template
Budget: $30 – $250 USD
I’m putting together a production-ready Expo starter that lets any future mobile app work completely offline first, then sync seamlessly when a connection is available. What I need is a fully wired template written in TypeScript with the following pieces already talking to each other:
• Tinybase as the client-side state engine, pre-configured for conflict-free local storage
• Cloudflare Workers (or Durable Objects) handling the real-time sync layer
• Supabase hooked in as a nightly backup target
• Clerk providing email-and-password authentication, with a simple switch to allow anonymous sign-in
• RevenueCat enforcing paywalls on protected routes
• Onboarding flow and route guards already scaffolded
• Uniwind (Tailwind-like) theming so styles stay consistent out of the box
• Any other plugins and configuration for a production app (eg security, analytics/bug monitoring etc)
I’d like clean, commented code plus basic documentation that maps every folder, shows how each service is configured, and lists any environment variables I must add before deploying. Where something is opinionated (e.g., the sync strategy or Clerk middleware), include a brief note on why it was chosen and how to swap it if my needs change.
Acceptance criteria
1. I can clone the repo, run `npx expo start`, create an account, go offline, make changes, come back online, and see data automatically merge.
2. Creating a subscription in RevenueCat immediately unlocks a pay-walled screen.
3. One command pushes the Cloudflare Worker and seeds Supabase tables.
4. Documentation covers setup, environment, and extension points clearly enough that a mid-level developer can follow it without you on the call.
Once you hand over the code, we’ll schedule a 1–2-hour video session where you walk me through architecture decisions, build scripts, and any gotchas I should know before shipping to TestFlight and Google Play.
If you’ve built something similar or have public repos that prove deep Expo experience, please include them in your proposal.
• Tinybase as the client-side state engine, pre-configured for conflict-free local storage
• Cloudflare Workers (or Durable Objects) handling the real-time sync layer
• Supabase hooked in as a nightly backup target
• Clerk providing email-and-password authentication, with a simple switch to allow anonymous sign-in
• RevenueCat enforcing paywalls on protected routes
• Onboarding flow and route guards already scaffolded
• Uniwind (Tailwind-like) theming so styles stay consistent out of the box
• Any other plugins and configuration for a production app (eg security, analytics/bug monitoring etc)
I’d like clean, commented code plus basic documentation that maps every folder, shows how each service is configured, and lists any environment variables I must add before deploying. Where something is opinionated (e.g., the sync strategy or Clerk middleware), include a brief note on why it was chosen and how to swap it if my needs change.
Acceptance criteria
1. I can clone the repo, run `npx expo start`, create an account, go offline, make changes, come back online, and see data automatically merge.
2. Creating a subscription in RevenueCat immediately unlocks a pay-walled screen.
3. One command pushes the Cloudflare Worker and seeds Supabase tables.
4. Documentation covers setup, environment, and extension points clearly enough that a mid-level developer can follow it without you on the call.
Once you hand over the code, we’ll schedule a 1–2-hour video session where you walk me through architecture decisions, build scripts, and any gotchas I should know before shipping to TestFlight and Google Play.
If you’ve built something similar or have public repos that prove deep Expo experience, please include them in your proposal.
Related categories:
JavaScript
Mobile App Development
Testing / QA
React Native
Cloudflare
Tailwind CSS
Expo