Guide
Pick the right project type
Seven project types, and how to know which one fits your idea.
Before you start
- None. Read this before creating a project.
- 1
Why the type matters
The project type shapes the questions the AI asks during onboarding and the skeleton your first build starts from. A close match means fewer questions and a first build that already has the right structure. It is set when the project is created, so it is worth a minute of thought.
- 2
Content + records, the safe default
Lists, forms, a profile, maybe an admin view. This is the classic app shape and it fits most ideas: recipes, workouts, bookings, inventory, customer registers, habit trackers. If your app is mostly about creating and browsing things, pick this.
- 3
Single-purpose tool
One hero screen that does one thing well. Timers, calculators, converters, checklists. Pick this when your app has no real database of records, only a task to perform.
- 4
Reader / feed
Browsing and reading is the core: articles, news, digests, catalogs. The structure centers on a feed and a reading view instead of forms.
- 5
Chat / messaging
Conversations with a composer and realtime updates. Pick this for chat apps, support inboxes, or anything where people write to each other.
- 6
Game / interactive
A fullscreen stage with a HUD and no bottom navigation. Pick this for games and playful interactive experiences. The onboarding asks game questions instead of app questions.
- 7
Shopify storefront
A native mobile app for a Shopify store you already run: products, cart, checkout, customer login. Shopify keeps owning products and orders, AppMuse builds the mobile experience. This type is Flutter only.
- 8
Pro mode
Build from scratch with your own stack, design system and libraries. There is no questionnaire: you write everything as one opening brief. Pick this only if you know exactly what you want. For everyone else the standard types give a better result faster.
- 9
If nothing fits perfectly
Pick the closest one. The type sets the starting point, not a limit: the AI adapts as you describe your app, and you can ask for anything in the chat afterwards. When two types both feel right, Content + records is usually the better bet.