Product demo
Example pre-launch report for an AI-built app
This fictional report shows how MakerToLaunch checks common launch blockers before an app goes live — score, issues, AI assistant, and copy-ready prompts.
Example pre-launch report · Fictional app
Explore the full product experience — score, blockers, AI assistant, and copy-ready prompts — without connecting a repo.
Your launch plan is ready
MakerToLaunch found what is working, what needs attention, and the safest path to go live for TaskFlow.
Launch score
Needs work
What's working
Biggest blocker
Turn off Django DEBUG before production and set ALLOWED_HOSTS
Next best step
Set DEBUG=False and configure ALLOWED_HOSTS in Django settings
Overview
Executive summary
TaskFlow is a promising AI-built monorepo with a Django API and a React/Vite frontend. The project structure is clear and the README explains the product well.
Before you invite real users, fix debug mode, environment variable documentation, and deployment configuration. These are common first-launch gaps — not signs the project is broken.
Monorepo
Detected app parts
Your project has multiple app parts. Developers call this a monorepo — often a frontend and backend in one GitHub repository.
taskflow-api
Backend
52
- Path
- /backend
- Framework
- Django
taskflow-web
Frontend
64
- Path
- /frontend
- Framework
- React/Vite
Strengths
Good news
- README explains what TaskFlow does and how to run it locally
- Frontend has a production build script (`npm run build`)
- Backend dependencies are listed in requirements.txt
- Repository structure is easy to follow (separate backend/ and frontend/ folders)
Priority fixes
Must fix before launch
Turn off Django DEBUG before production and set ALLOWED_HOSTS
Add .env.example files with placeholder values (never real secrets)
Document deployment steps for backend and frontend
Review CORS settings so only your live frontend can call the API
Strategy
Recommended launch path
- A sensible path for this stack:
- Fix DEBUG and secrets in the Django backend first
- Add .env.example files and document required variables
- Deploy the Django API to Railway (beginner-friendly for Python)
- Deploy the React frontend to Vercel
- Set VITE_API_URL on the frontend to your live API URL
- Test sign-up and core flows on the live site
Configuration
Environment variables guide
Backend (Django) — likely required: - SECRET_KEY — Django signing key (generate a new one for production) - DEBUG — should be False in production - ALLOWED_HOSTS — your live API domain - DATABASE_URL — production database connection string
Frontend (React/Vite) — likely required: - VITE_API_URL — public URL of your deployed Django API
Copy .env.example to .env locally and fill in real values only on your machine or hosting dashboard — never commit secrets.
Before you go live
Security notes
- DEBUG mode in Django settings is the highest-priority security fix
- Review frontend code for hardcoded API keys or tokens
- Tighten CORS before going live
- Rotate any secrets that may have been committed to Git history
Checklist
Step-by-step plan
- 1
Set DEBUG=False and configure ALLOWED_HOSTS in Django settings
- 2
Create backend/.env.example and frontend/.env.example with placeholders
- 3
Add a Deploy section to the README with host recommendations
- 4
Deploy taskflow-api to Railway and set production env vars
- 5
Deploy taskflow-web to Vercel with VITE_API_URL pointing at Railway
- 6
Run through sign-up, login, and one core workflow on the live site
- 7
Re-scan in MakerToLaunch to confirm improvements
Your turn
Ready to check your own app?
Connect your GitHub repo and get a pre-launch check like this one — tailored to your stack, your files, and your next steps. Launch Pack unlocks after your free check.