Expo - Handles app routing of screens
Next.js - Handles web routing of screens (SSR Works)
React Query - Handles data fetching and hooks (Expo + Next)
(Others are using TRPC with clients in Expo and Next)
Zustand - Handles gllobal state (Expo + Next)
Tamagui - Component libary (Expo + Next)
Performance on the web with SSR rendering, React-Query pre-caching, and Next.js static builds is insanely good.
You have to bring your data fetching, and state, but `create-tamagui-app` is pretty amazing if you get stuck into it for a couple of hours.
I imagine in a few months there will be a monorepo starter with:
Expo
Next
Prisma / Supabase auth and database
Data fetching with TRPC
Tamagui Design System
Zustand client-state
Tamagui for "View" components and styling (+SSR on web)
+ React Query for data fetching, cache management, and neat hooks to use that data in apps. (+SSR on web
+ Zustand - "lite" state management on RN and React Web
+ Moti for X-Platform animations
+ Zeego for X-Platform menus
= Ridiculously high percentage of code re-use across web and react-native apps.
Expo - Handles app routing of screens Next.js - Handles web routing of screens (SSR Works) React Query - Handles data fetching and hooks (Expo + Next) (Others are using TRPC with clients in Expo and Next) Zustand - Handles gllobal state (Expo + Next) Tamagui - Component libary (Expo + Next)
Performance on the web with SSR rendering, React-Query pre-caching, and Next.js static builds is insanely good.
You have to bring your data fetching, and state, but `create-tamagui-app` is pretty amazing if you get stuck into it for a couple of hours.
I imagine in a few months there will be a monorepo starter with:
Expo Next Prisma / Supabase auth and database Data fetching with TRPC Tamagui Design System Zustand client-state
Someone's probably working on it right now