Back to Architect
Architect Path

What Can You Build?

You have an idea. Maybe it's been rattling around in your head for months. Before you build anything, you need to answer one question: what kind of project is it?

12 min read

Why Category Matters

When someone says "I want to build an app," they could mean a hundred different things. A booking platform that runs in a browser. A fitness app on your phone. A word game you play with friends. An automation that saves you 3 hours of copy-pasting every week.

Each of these requires completely different tools, skills, and approaches. A web app uses different technology than a mobile app. A game has different requirements than an automation. Picking the wrong category means picking the wrong tools, wasting time, and building something that doesn't fit what you actually need.

The good news: there are really only four categories that cover 95% of what people want to build. And AI tools have made every single one of them accessible to beginners.

The Four Categories

SaaS / Web App

Software that runs in the browser

If your idea involves people signing up, logging in, and using a tool through a website, it's a web app. This is the most common category and the one with the best AI tooling. Tools like Lovable and Bolt can generate a working web app from a single description.

Think: A CRM, a booking platform, an analytics dashboard, a marketplace, a project management tool, a portfolio site with a backend.

Mobile App

Apps for iOS and Android

If your idea needs to live on someone's phone with push notifications, camera access, GPS, or offline functionality, you're building a mobile app. Cross-platform tools like React Native and Flutter let you write one codebase that works on both iPhone and Android.

Think: A habit tracker, a food delivery app, a fitness app, a local events guide, a photo editing app.

Native Game

Dedicated gaming experiences

This category is for dedicated, standalone games built with game engines like Unity, Godot, or Unreal. These need physics, rendering, game loops, and specialized tooling that web/mobile frameworks aren't designed for. Simple browser games (like a quiz or word puzzle) can be built as a Web App, and casual phone games can go the Mobile App route. You only need the Game category when the core experience requires a real game engine.

Think: A platformer, a 3D adventure, a multiplayer strategy game, a physics-based puzzle, an RPG.

Automation

Connect tools, eliminate busywork

If your idea isn't something people use directly but something that works behind the scenes (connecting tools, moving data, triggering actions), it's an automation. This is the easiest category to start with: tools like Make and Zapier let you build powerful automations with zero code.

Think: Auto-sort emails, generate reports, sync data between tools, post to social media on a schedule, send alerts when conditions are met.

Classify Your Idea

Not sure which category fits? Try our classifier. Browse example ideas or describe your own and we'll tell you what category it matches and what you'd need to build it.

Click any idea to see what kind of project it is and how you'd build it:

Click an idea above to classify it

What If My Idea Doesn't Fit?

Most ideas fit neatly into one category, but some straddle the line. Here's how to think about edge cases:

"I want a web app AND a mobile app." Start with the web app. Modern web apps work great on mobile browsers. Build the native mobile app later, only if you need device-specific features like push notifications or camera access.

"I want to build a game." Ask yourself: does it need physics, real-time rendering, or a game engine? If yes, it's a Native Game. If it's a trivia app, word puzzle, or quiz, that's a Web App or Mobile App with game-like features. You don't need Unity to build Wordle.

"I want to automate something AND build a dashboard to see the results." Build the automation first. Add the dashboard later as a web app that reads from the same data source.

"I just want a simple website." If it's truly static content (no user accounts, no stored data), you don't need a tech stack at all. Tools like Framer, Webflow, or even Notion can handle it. But the moment you need users to log in, store data, or interact with each other, it's a web app.

You don't need to choose perfectly. The point of categorizing your idea isn't to lock you in. It's to point you at the right starting tools and resources. You can always pivot later. The important thing is to start building, learn from what breaks, and iterate.

In the next lesson, we'll demystify how AI actually builds software. You'll learn what "vibe coding" really means, when to use all-in-one platforms vs custom tools, and what you're actually responsible for as the human in the loop.

What You Just Learned

  • Four categories cover 95% of ideas: SaaS/web app, mobile app, game, or automation
  • Category determines your tools. Each type needs a different technology stack
  • Start with one thing. Web app first, then mobile. Automation first, then dashboard
  • Every category is now beginner-friendly. AI tools have lowered the barrier for all four