Skip to main content

S6. App types

What this page helps you do​

Get a quick plain-English description of the app types used in the guide.

Why it matters​

Builders often say “website” when they really mean “small app with login and a database.” The right label helps you pick a safer path.

You should already have​

  • a basic idea of what your app does

Skip this page if​

What to do​

P1. Simple website​

Mostly public pages. Little or no user data. No complicated app behavior.

P2. SaaS web app​

Users sign in, create or manage data, and expect the app to stay available.

P3. AI app​

The app depends on AI output, model calls, prompts, retrieval, or usage limits.

P4. Internal tool​

Used by a known team or company. Access control and reliability matter more than public marketing pages.

P5. API/backend​

The main thing you ship is a service other systems talk to.

If people sign in or save data, do not treat it as a simple website.

Common mistakes​

  • calling an AI app a normal web app because the interface looks simple
  • calling a logged-in app a website because it only has a few pages
  • forgetting that internal tools still need safe access and backups

Next step​

Go to S4. Choose your path.

Advanced notes​

TODO for contributors: add short examples of well-known app shapes that fit each category.