NativeLaunch: New Monorepo Starter

NativeLaunch now includes a new monorepo-based starter designed for projects that require a shared codebase, multiple apps, and a more scalable structure.

This does not replace the existing single-app starter. The original repository remains supported and continues to be the recommended starting point for most projects.

What’s new

The new NativeLaunch monorepo introduces a different way of working with the starter:

A Turborepo-powered monorepo setup
Shared packages for UI, configuration, and utilities
A production-ready app structure
A lightweight Expo Go playground for previewing screen variants and UI components
Ready-made design variants you can explore instantly in Expo Go
Clear separation between app code and shared logic

This structure is designed for teams, larger projects, or developers who want to experiment with multiple app setups while sharing the same foundation.

Why a monorepo?

As NativeLaunch grew, it became clear that some use cases don’t fit well into a single-app repository.

The monorepo starter was created to support:

Shared UI and design systems
Multiple apps or environments in one codebase
Faster iteration when experimenting with layouts, screens, and components
Better long-term scalability for complex projects

Using Turborepo allows the setup to stay fast, predictable, and easy to extend.

Expo Go playground & design previews

One important addition in the monorepo is a lightweight Expo Go app that works as both a UI playground and a design showcase.

It allows you to explore ready-made screen and design variants instantly — without cloning the repository or running the project locally.

This setup is designed for:

Browsing screen variants and layouts
Previewing UI components and interactions
Comparing different design approaches
Exploring ideas quickly without touching the production app

Scan the QR code below with Expo Go to open the preview app and browse available screens and UI variants:

No installation or build steps required — just scan and explore.

The original starter is still here

If you’re already using the single-app NativeLaunch starter, nothing changes.

The original repository stays active
Documentation continues to focus on the single-app setup
The monorepo is an alternative, not a migration requirement

You can choose the setup that best fits your workflow.

How to choose between them

Single-app starter Best for most projects, MVPs, and solo developers.
Monorepo starter Better suited for larger projects, shared codebases, or teams that want a scalable structure with multiple apps and a UI playground.

Both approaches are part of NativeLaunch and can evolve independently.

Notes

This documentation currently focuses on the single-app starter.

The monorepo setup is best explored directly through the repository, and its structure may differ from the content described in the docs.