Early Frontend Architecture

Goal

Set day-one frontend architecture decisions for young web apps so the project can scale without expensive rewrites. Keep recommendations proportional to the product's actual interaction model.

If the user asks for the original opinionated rationale, or if a recommendation needs stronger justification, read SOURCE_ADVICE.md.

First Classify The App

Before recommending libraries or conventions, classify the app:

• Standard CRUD/SaaS: forms, tables, dashboards, auth, settings, admin workflows.
• Interactive workspace: canvases, editors, inspectors, media, command palettes, nested panels.
• Offline-first/sync-heavy: local-first behavior, optimistic replication, collaboration, Linear-style sync.
• AI/realtime-heavy: streaming responses, job progress, notifications, live data, collaborative updates.
• Content/SEO-heavy: public pages, search traffic, SSR/SSG, marketing or docs surfaces.
• Pure authenticated SPA: app is mostly behind login and does not benefit much from SSR.