You've run npx create-expo-app, and three days later you're configuring NativeWind v4 PostCSS, debugging Supabase deep-link callbacks, and writing your fifth token-refresh useEffect. The decision hits: keep grinding, or buy a $79 React Native template and skip to the actual product?
This post is a decision framework with the actual numbers. No marketing — the math leans toward buying, and the rest of this post explains exactly when it doesn't.
Buy when:
- The app is a recognizable pattern (auth + DB + payments + a vertical UI)
- You're solo or a two-person team
- Your time is worth more than $50/hour
Build from scratch when:
- The UX is genuinely novel
- You have hard compliance (HIPAA, PCI L1, SOC 2)
- You're learning React Native and the setup is the point
- You're at 1M+ user scale on day one
The setup tax
Foundation work, before any product code:
Expo + TS + ESLint + Prettier ......... 4h
Expo Router v4 (typed routes) ......... 6h
Supabase auth (email/Apple/Google) .... 14h
NativeWind v4 + dark mode ............. 8h
TanStack Query + Zustand .............. 6h
Stripe / RevenueCat ................... 16h
Push (APNs + FCM via Expo) ............ 8h
Supabase Storage + RLS ................ 6h
Sentry + PostHog ...................... 4h
EAS Build + iOS/Android signing ....... 8h
─────────────────────────────────────────
Total .................................. ~80h
At $75/hr indie rate that's $6,000 of your time. At $150/hr US contract, $12,000. Most of those hours are commodity work — you are not building a moat, you are configuring app.json.
Template price tiers in 2026
$0–29 screen kits, free boilerplates (no backend, stale fast)
$49–99 full-stack with real backend (Supabase/Firebase/Node)
$199–499 vertical clones (food delivery, marketplace, dating)
If a $79 template saves 60 of those 80 hours, the effective hourly rate for from-scratch to win is under $1.32/hour. Don't be that cheap.
Buy vs. build at a glance
| Factor | Build | Buy |
|---|---|---|
| Time to deployable build | 3–6 weeks | 1–2 days |
| Cash cost | $0 | $49–499 |
| Time cost | 80–200h | 2–8h customization |
| Code understood day 1 | 100% | 60–80% (100% after a week) |
| Architecture quality | Your choices | Template's choices |
| Security posture | What you remember | What was shipped |
| Best for | Novel UX, learning, compliance | MVPs, vertical clones, agency work |
The buyer's checklist
Before you buy, verify:
# 1. Is the backend real or mocked?
grep -r "mockApi\|fixtures" src/
# 2. React Native + Expo version
cat package.json | grep -E "react-native|expo"
# Floor in 2026: RN 0.81, Expo SDK 54
# 3. Leaked keys
git log -p | grep -iE "sk_live|service_role|AKIA"
# 4. TypeScript strict mode
cat tsconfig.json | grep strict
# 5. Last commit recency
git log -1 --format=%cd
# 6. License terms
cat LICENSE
If a template fails on (1) — backend is mocked — you don't have a template, you have a screen kit. You will rebuild the entire backend.
What "production-ready" should actually mean
Six bars a template should clear before it can use the phrase:
- A Postgres schema with RLS you can
supabase db push— see Supabase RLS docs - Auth flows that pass App Store review (Apple Sign-In mandatory if any other social)
- Server routes for anything sensitive (no API keys on device)
- Error / loading / empty states wired everywhere
- EAS Build profiles producing signed iOS + Android binaries — see EAS Build docs
- AI agents (Claude Code, Cursor) can extend it without breaking the architecture
The sixth is the 2026 bar that didn't exist in 2023. AI agents do their best work on known-good repos. Templates that confuse agents lose to ones that don't.
When buying wins
- Your app is "X for Y" where both X and Y already exist
- Solo / two-person team
- Agency / contractor billing a client (license permitting)
- You want a security baseline you didn't write at 1 AM
- You're driving development with AI agents
When building wins
- Novel UX with no obvious analog
- Hard compliance constraints
- Learning React Native — the setup is the point
- Extreme scale on day one
- Template stack is wrong for you (e.g., you need Firebase, template is Supabase)
A two-minute decision framework
- Screen architecture obvious in 5 min of whiteboard? → buy
- App describable as "X for Y"? → buy
- Timeline < 60 days? → buy
- Billing a client > $5,000? → buy
- Learning React Native? → build the first, buy the second
Two or more "buy" answers and you don't need a calculator.
Disclosure
I work on production-grade React Native templates ($49–99 on RN 0.81 / Expo SDK 54 / Supabase). Bias acknowledged. The math still leans toward buying for most indie apps — and when it doesn't, the post above tells you exactly why.
Whatever template you evaluate, run the buyer's checklist above. A real template ships a real backend (schema, RLS, server routes), passing App Store review, with EAS Build profiles ready to go. If it doesn't ship those, the price you spent on it bought you nothing.
If none of the templates on the market match your app shape, build from scratch. That's the only honest answer to the buy-vs-build question.
For the longer breakdown — the FAQ and the line-by-line "what a real template ships" inventory — see the Applighter blog.
What's the foundation work that ate the most hours on your last React Native project? Drop it in the comments — I'm collecting the unglamorous setup tasks indie devs underestimate for a follow-up.
Top comments (0)