App Dev Planner

App Dev Planner is an open-source planning workspace for turning rough app ideas into technical specs, roadmaps, and developer-ready briefs.

The project is currently an early MVP under active development. It is being prepared for a stronger public/open-source release posture, but it should still be treated as a work in progress.

Live Demo

https://app-dev-planner.vercel.app

Screenshots

The screenshots below are captured from the live demo.

Landing Page

Features and Workflow

Audience Fit and CTA

Problem

Early app ideas often live across chat logs, notes, screenshots, and unfinished documents. That makes it hard for builders to clarify scope, identify technical risks, and hand a project to a developer or AI coding agent with enough context.

App Dev Planner provides a guided planning flow that turns product, technical, security, testing, deployment, and maintenance answers into a structured technical blueprint.

Target users

• Solo developers validating a new app idea before implementation.
• Indie hackers turning product ideas into actionable build plans.
• Freelancers collecting clearer client requirements.
• Product-minded builders preparing developer-ready briefs.
• Students or small teams documenting capstone, MVP, or internal-tool plans.
• AI-assisted builders who want better prompts, specs, and handoff documents.

What the app currently does

Based on the current codebase, App Dev Planner includes:

• A public landing page introducing the planning workflow.
• Email/password registration and login through Supabase Auth.
• A protected dashboard that lists the signed-in user's projects.
• Project creation with app name, app type, description, and draft status.
• A guided brainstorming flow with 12 sections and 55 questions.
• Autosaved brainstorming answers stored in Supabase.
• Project detail pages with progress tracking across answered questions.
• Markdown technical blueprint generation from saved answers.
• Preview of the generated technical blueprint.
• Client-side export to visual HTML and Markdown.
• PDF export guidance through browser print from the generated HTML.
• Project deletion that removes related brainstorming answers and generated documents.

Current limitations

• The app expects a Supabase project and compatible tables/policies to exist.
• Database migrations are not yet included in the repository.
• Automated tests are not yet present.
• CI is limited to dependency install, lint, and build checks.
• A short walkthrough video is not yet included.
• Some generated blueprint sections describe intended architecture and future capabilities, not all of which are implemented as app routes today.

Tech stack

• Next.js 16 App Router
• React 19
• TypeScript
• Tailwind CSS 4
• Supabase Auth and PostgreSQL
• @supabase/ssr and @supabase/supabase-js
• file-saver for browser downloads
• docx dependency reserved for document export work
• ESLint

Project structure

app/
  page.tsx                         Public landing page
  (auth)/login/page.tsx            Login page
  (auth)/register/page.tsx         Registration page
  auth/logout/route.ts             Logout route
  dashboard/page.tsx               Protected project dashboard
  projects/new/page.tsx            Project creation
  projects/[id]/page.tsx           Project detail and progress
  projects/[id]/brainstorming/     Guided planning questions
  projects/[id]/preview/           Generated blueprint preview
  projects/[id]/export/            Export UI and client-side exporters
lib/
  supabase-browser.ts              Browser Supabase client
  supabase-server.ts               Server Supabase client
  supabase.ts                      Shared Supabase client
proxy.ts                           Supabase session refresh and route protection

Local setup

Clone the repository:

git clone https://github.com/marcomartinomarch2005/app-dev-planner.git
cd app-dev-planner

Install dependencies:

npm install

Create a local environment file:

cp .env.example .env.local

Fill in your local Supabase values in .env.local.

Run the development server:

npm run dev

Open http://localhost:3000 in your browser.

Environment variables

Only public Supabase browser values are required by the current app code:

NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=

Use .env.local for real values. Do not commit .env.local, service-role keys, database passwords, or other private credentials.

Supabase setup notes

The code currently reads and writes these tables:

• projects
• brainstorming_answers
• generated_documents
• export_history

The app assumes authenticated users can only access their own project data. Before a public demo or production deployment, confirm Row Level Security policies, table constraints, and delete behavior in Supabase.

See docs/SUPABASE_SETUP.md for setup notes, schema outline, and RLS reminders.

Documentation

• Supabase setup
• Public release checklist
• Issue backlog drafts
• Screenshot guidance
• Open-source application notes
• Release notes draft
• Security review notes
• Next.js/PostCSS audit review

Roadmap

See ROADMAP.md for the current public-readiness roadmap.

Near-term themes include:

• Public release readiness.
• Documentation and demo assets.
• Export improvements.
• AI-assisted specification review.
• Testing and CI.
• Security hardening.
• App planning templates.

Contributing

Contributions are welcome once the repository is public. Please read CONTRIBUTING.md before opening an issue or pull request.

Good first contribution areas include:

• Improving setup documentation.
• Adding screenshots or demo walkthroughs.
• Refining planning questions.
• Improving generated blueprint formatting.
• Adding tests.
• Improving accessibility and UI clarity.

Security

Please do not open public issues for sensitive security reports. See SECURITY.md for responsible disclosure guidance.

Code of conduct

This project uses a concise contributor code of conduct. See CODE_OF_CONDUCT.md.

License

This project is released under the MIT License. See LICENSE for details.