Project type determines which block library you get and how your project gets published, it's the single most important choice when creating a project. Here's what each one is actually for:
Website
For content that doesn't need individual user accounts: marketing sites, landing pages, portfolios, blogs, brochure sites. Comes with sections, forms, galleries, pricing tables, and other content-focused blocks. If visitors just read your site rather than logging into it, this is almost always the right choice.
Web Application
Everything a Website can do, plus real accounts: sign-up and login forms, a live database your visitors' data is stored in, and optional two-factor authentication for your own end users. Choose this the moment your project needs "users can create an account and see their own data."
Desktop
An installable Windows or Linux application (currently in Beta; macOS isn't available yet), with access to things a browser can't offer: local file storage, system notifications, global keyboard shortcuts, camera access, a real local login/registration system (accounts hashed and checked entirely on-device), and its own Variables/Condition blocks for branching logic and math.
Mobile
An installable Android app (iOS isn't available yet), with access to device features like the camera, GPS location, biometric authentication, QR/barcode scanning, a real local login/registration system (accounts hashed and checked entirely on-device), and its own Variables/Condition blocks for branching logic and math.
Discord Bot
A bot that lives inside a Discord server: slash commands members can run, and events it reacts to automatically (someone joining, a message being posted, and more).
API
Pure backend, no visual interface of its own: your own endpoints, your own data collections, and optional API-key authentication, built to be called from other tools, apps, or scripts.
Chat Bot
Your own Telegram bot (WhatsApp is coming soon), connected with your own bot token from @BotFather. Build one or more flows, each starting from a trigger (a specific command or any message), that reply, ask follow-up questions, and remember things about each user with variables.
Form Builder
Surveys and questionnaires: short text, long text, email, number, multiple choice, checkboxes, a dropdown, or a rating scale, plus optional section breaks. Publish it to a shareable link and every response is collected in one place, viewable and exportable as CSV.
Tip: You're not permanently locked into one choice — most underlying concepts (variables, conditional logic, workflows) carry over if you start a different project type later, so picking wrong isn't a costly mistake.