// the find
obytes/react-native-template-obytes
📱 A template for your next React Native project: Expo, PNPM, TypeScript, TailwindCSS, Husky, EAS, GitHub Actions, Env Vars, expo-router, react-query, react-hook-form.
A production-grade Expo + React Native starter template from a mobile consultancy that uses it internally. Bundles the current standard stack: expo-router, React Query, TanStack Form, NativeWind (Tailwind for RN), Zustand, MMKV, and a full CI/CD setup with EAS. Aimed at teams who want to skip the week of boilerplate wiring and get to feature work.
The CI/CD setup is genuinely thorough — 10+ GitHub Actions workflows covering builds, E2E via Maestro, type-checking, lint, and release automation, which most homegrown setups never finish. MMKV over AsyncStorage is the right call for auth token persistence, and the choice is intentional, not accidental. Multi-environment config (dev/staging/prod) is baked in via Expo config rather than bolted on later. Feature-sliced directory layout (`src/features/auth`, `src/features/feed`) keeps things from collapsing into a components dumping ground as the app grows.
The sample app (a basic feed with login/onboarding) is thin enough that you'll hit structural decisions the template doesn't answer — deep linking with auth guards, push notifications, offline support — within a week of real development. NativeWind v4 still has rough edges with conditional styles and third-party components, and the template doesn't document the workarounds. There's no state management guidance beyond the auth store example; a real app will need to decide how to scope Zustand stores and the template leaves that entirely open. E2E tests exist but only cover the sample screens — they'll be deleted or ignored as soon as you replace the demo content.