When we launched v2, every suite quietly assumed one thing: you were building a web app. That assumption is gone. You can now tell InitRepo exactly what you're building, and the entire documentation suite — blueprint, architecture, UX, roadmap, and all — is tailored to that platform.
New project types
Mobile apps. Building for iOS and Android? Pick a mobile stack (Expo + Convex, React Native + Firebase, or Flutter + Supabase) and your docs plan for native concerns: app-store deployment, offline behavior, device permissions, push notifications, and platform UI guidelines — with native component libraries, not web kits that don't run on a phone.
Desktop apps. Installable software for Mac, Windows, and Linux, with Tauri or Electron stacks and the packaging, auto-update, and OS-integration concerns that come with shipping a real binary.
APIs & backends. No end-user UI? The "design" document becomes an API contract and developer-experience spec — endpoints, auth, rate limiting, versioning, and error models — instead of screens.
Automations & scripts. Bots, scrapers, data pipelines, and scheduled jobs get an operator-experience spec: triggers and scheduling, configuration surface, inputs and outputs, logging, and failure handling.
Live now — and being tested
All four are live in the wizard today. We're actively running real projects through each platform and tightening the output as we go, so if you spot something that doesn't fit your stack, that feedback goes straight into the engine.
Pick your platform and start a project.