What is it called?
Who uses it? This is the question that decides the architecture, and it is the hardest one to change later.
Customers and a team A product people sign up to, plus an operator console. Customers only No separate back office yet. A team only An internal tool. Nobody outside uses it.
Where do they use it? A website The browser, and that is all for now. Website and phone app Adds an Expo app against the same API. Website and desktop app Adds a Wails app that can work offline. Web, phone and desktop Every target, plus a docs site. No interface at all An API other things call.
Where does the data go? SQLite is the one to pick while learning: there is no container to start and nothing to install.
Postgres The production answer. Needs Docker, or a hosted database. SQLite A file. No Docker, no database server, nothing to install.
Which frontend? Next.js Server components, and the frontend most people know. Vite and TanStack Router A single-page app, typed routes, very fast reloads.
Will one deployment serve several customers? If each customer is an organisation with its own users and its own data, say yes now. Adding tenancy later means touching every query, every permission check and every billing record.
Yes, it is multi-tenant