Skip to main content
Mobile Launcher

Introduction

Initialize, plan, connect, and launch your AI Mobile Launcher app.

Build from one accepted plan

AI Mobile Launcher starts with one buyer-owned initialization workflow. It cleans the template identity, interviews you about the product and its growth loop, generates the canonical plan, records service setup honestly, and gates feature work on your acceptance. The implementation is available on the AI Pro and Standard development branches.

Text
clean → interview → plan → accept → connect → build → launch

The initializer creates docs/PRODUCT.md, docs/FEATURES.md, docs/ROADMAP.md, docs/GROWTH.md, docs/KEYS.md, and docs/INIT-PLAN.md. Wire is the first growth workstream: activation, lifecycle events, the first onboarding experiment, the learning review, and the optimization backlog are planned before feature work begins.

A pending initialization is an editable development tree. It is not a native build, a verified service connection, or release proof.

Two-person AI Pro testing starts from merge commit a7f6cb3 from PR #30. The Standard workflow merged through PR #31.

Documentation Sections

Initialize the Boilerplate

Set up your development environment and get the boilerplate running on your machine.

Recovery and deeper guides

The initializer is the canonical path. Use these guides when an existing project needs one artifact repaired or you want to inspect the underlying system.

Learning & Tutorials

Deep dive into the boilerplate architecture and deployment.