expo-examples

Topics in the source

• Expo Examples
• Two modes
• Workflow
• 1. Find the right example
• 2a. Inspiration mode — study without touching the user's project
• 2b. Scaffold mode — new project from an example
• 3. Adapt into the user's app — non-destructively (critical)
• Gotchas

expo/examples is Expo's official library of 70 integration examples — directories named with- (e.g. with-stripe, with-maps), each built around one library or service. These are not full apps: they're managed projects (no ios//android/ dirs — native setup is via config plugins), and the typical one is a single screen of 100–200 lines. Mine them for the canonical integration pattern — the dependency set, app.json config plugins, and minimal wiring Expo maintains against the current SDK — and adapt that into the user's app. Don't expect to lift an application architecture from them. Reach for an example before hand-rolling an integration. (Kinds — full-stack, showcases, starters — are noted in ./references/catalog.md.) 1. Inspiration / adapt (most common) — the user already has a project. Find the matching example, read its key files, and apply the pattern to their code. 2. Scaffold — greenfield. Start a fresh project directly from the example. Map the user's need to an example name (e.g. payments → with-stripe, auth → with-clerk). ./references/catalog.md is a categorized snapshot for fast triage — but it drifts, so confirm against the live list: meta.json is the source of truth for w

This is an excerpt. Refer to the complete source and its current requirements.