Create Tamagui App

Set up a starter repo with expo, expo-router, Next.js, and Tamagui configured and ready to go:

npm create tamagui

By integrating Tamagui, expo-router, Solito, and, Next.js you can enjoy the power and simplicity of creating universal apps.

Currently, we have one template available:

• next-expo-solito Expo, Expo Router, Solito and Next.js (with both /pages and /app dir)

npm create tamagui

Check out the source of the templates .

A big shout out to Fernando Rojo  for creating Solito , a great library for sharing all your views between Expo and Next.js, and the bootstrap repo we borrowed from.

To run the app:

cd myapp
yarn
yarn web # Next.js local dev
yarn native # Expo local dev

📦 Included packages

• tamagui for cross-platform views, themes and animations
• solito for cross-platform navigation
• expo-router for having same routing concepts between web and native
• Expo SDK 48
• Next.js 13

🗂 Folder layout

• apps entry points for each app

  • expo
  • next

• packages shared packages across apps

  • app you'll be importing most files from app/
    • features (don't use a screens folder. organize by feature.)
    • provider (all the providers that wrap the app, and some no-ops for Web.)
    • navigation only for next-expo-solito template, contains the navigation code for RN

You can add other folders inside of packages/ if you know what you're doing and have a good reason to.

🏁 Start the app

• Install dependencies: yarn

• Next.js local dev: yarn web

  • Runs yarn next

• Expo local dev: yarn native

  • Runs expo start

🆕 Add new dependencies

If you're installing a JavaScript-only dependency that will be used across platforms, install it in packages/app:

cd packages/app
yarn add date-fns
cd ../..
yarn

If you're installing a library with any native code, you must install it in apps/expo:

cd apps/expo
yarn add react-native-reanimated

cd ../..
yarn

You can also install the native library inside of packages/app if you want to get autoimport for that package inside of the app folder. However, you need to be careful and install the exact same version in both packages. If the versions mismatch at all, you'll potentially get terrible bugs. This is a classic monorepo issue. I use lerna-update-wizard to help with this (you don't need to use Lerna to use that lib).