Skip to main content
Functional Design covers what your app does and who does it. It’s the largest of the three specification groups and the one most builders spend the most time on. Five sub-areas:

Archetype

The foundational shape of your app — solution type, commercialization strategy, and pricing details.

User Types

The personas who use the app and the use cases each one performs.

Features

Modules and the features inside them, with user stories, business rules, and acceptance criteria.

System Services

Foundational capabilities — auth, payments, notifications, file storage, and more.

System Requirements

Regional, compliance, security, performance, and accessibility requirements.

How Archie pre-fills these

Functional Design specs are generated from your plan. Archetype reads your initial prompt and the plan’s recommendations; user types come from the plan’s persona section; features come from the plan’s modules; system services and requirements are seeded from the relevant plan sections. Edit any of them in place. Archie stores edits without touching your generated code until you re-run code generation.

FAQ

Most builders start with User Types (to confirm Archie has the right personas) and Features (to refine the modules and user stories). The rest can usually run on Archie’s defaults until you’re ready to ship.
Yes. The Features page lets you add modules and features that weren’t in the original plan. Adding here doesn’t require a plan regeneration.
Yes — they’re different surfaces. Functional Design defines behavior; Visual Design defines look and layout. Both feed into the same generation step.