Implementierungs-Reihenfolge für Breakout.now Launch

Detaillierte Abhängigkeits-Analyse & kritischer Pfad

Stand: 16. Februar 2026

KRITISCHER PFAD (Critical Path)

Die Reihenfolge, in der Features implementiert werden müssen, um nicht blockiert zu sein:

Start
  ↓
[1] Content & Branding (1 Woche)
  ↓
[2a] Email System Setup (2 Tage) ← Blockt: Onboarding, Invite-System
  ↓
[3] Auth + Login Improvements (2 Tage) ← Blockt: Alles andere
  ↓
  ├─→ [4a] Onboarding Briefings (3 Tage, parallel mit 2b)
  ├─→ [4b] Landing Pages (2 Wochen, parallel mit 2a)
  ├─→ [5] Invite System (3 Tage, nach Auth)
  └─→ [6] Feed/Home Hub (3 Wochen, nach Auth)
       ↓
       [7] Admin Dashboard (2 Wochen, optional für MVP)
  ↓
[8] Performance & Security Audit (2 Wochen)
  ↓
[9] Playwright Tests + QA (1 Woche)
  ↓
[10] Deploy + Launch (1 Woche)
  ↓
End

Kritischer Pfad Dauer: ~6 Wochen mit Full-Time Team

Critical Path Items (wenn eines verzögert, verzögert sich ganzer Launch):

Content & Branding (Domain-Fix blockiert alles)
Auth/Login (blockiert Onboarding + Invite)
Email System (blockiert Invites)
Feed Implementation (blockiert Creator/Artist Experience)
Performance & Security (blockiert Deployment)

WOCHENPLANIERUNG (Weekly Breakdown)

WOCHE 1: Grundlagen + Branding

Ziele: Domain konfiguriert, Branding klar, Auth updated

Tag	Task	Verantwortung	Status
Mo	Content Review & Branding (alle Links breakout.now → breakout.now)	Backend	-
Mo/Di	Umlaute Fixes in allen Komponenten	Frontend	-
Di/Mi	Password Double-Entry + Login-from-all-pages	Frontend	-
Mi	Email System Setup (SendGrid/Mailgun)	Backend + DevOps	-
Do	Email template design + translations	Frontend/Content	-
Do/Fr	Breakout.now Domain Setup + SSL	DevOps	-
Fr	QA: Content Review Pass 1	QA	-

End-of-Week Deliverables:

✓ breakout.now Domain live mit SSL
✓ Alle alten breakout.now Links entfernt
✓ Umlaute überall korrekt
✓ Auth Flow updated (double-entry passwords)
✓ Email System konfiguriert

Go/No-Go: Falls Ende Woche 1 nicht alles ready → verzögert Launch um 1 Woche

WOCHE 2: Onboarding + Auth finalisieren

Ziele: Invites funktional, Onboarding-Flow ready, Landing Pages started

Parallele Tracks:

Track A: Auth + Invite System (Frontend/Backend)

Task	Verantwortung	Est. Stunden
"Kein Account → Invite Request" Flow	Frontend	4
Invite Code Generation + Validation	Backend	3
Invite Email Template	Content	2
Test: End-to-End Invite Flow	QA	2
Subtotal Track A		11 Stunden

Track B: Onboarding Briefings (Content/Video/Frontend)

Task	Verantwortung	Est. Stunden
Record 3 Briefing Videos	Content/Video	6
Create OnboardingViewer Component	Frontend	2
Create OnboardingArtist Component	Frontend	2
Create OnboardingCreator Component	Frontend	2
Integration in Auth Flow	Frontend	1
Subtotal Track B		13 Stunden

Track C: Landing Pages Started (Frontend)

Task	Verantwortung	Est. Stunden
Main Landing Page (Hero + Value Props)	Frontend	4
Pricing Page Structure	Frontend	2
FAQ Skeleton	Content	2
Subtotal Track C		8 Stunden

Week 2 Deliverables:

✓ Invite System 100% functional
✓ Briefing videos recorded + uploaded
✓ Onboarding flow tested by 5 internal users
✓ Landing Page Hero live
✓ Pricing structure defined

WOCHE 3: Feed Implementation + Landing Pages

Ziel: Home Hub/Feed working, All Landing Pages drafted

Track A: Feed Implementation (Backend + Frontend)

Supabase Schema: feed_entries table + RLS (2 Stunden)
Realtime Listener: Supabase Realtime subscription (1.5 Stunden)
Feed Component basic version (4 Stunden)
Artist Dashboard Integration (3 Stunden)
Creator Dashboard Integration (3 Stunden)
Support Channel (2 Stunden)
Testing: Unit + Integration (3 Stunden)
Subtotal: 19.5 Stunden

Track B: Landing Pages Sprint (Frontend)

Creator Landing Page (3 Stunden)
Artist Landing Page (3 Stunden)
A&R Landing Page (3 Stunden)
FAQ Interactive (2 Stunden)
Impressum + Datenschutz (drafts) (2 Stunden)
Footer + Navigation (1 Stunde)
Subtotal: 14 Stunden

Track C: SEO Prep (Frontend + Backend)

Public artist profiles + meta tags (2 Stunden)
Sitemap generation (1 Stunde)
robots.txt (0.5 Stunden)
Subtotal: 3.5 Stunden

Week 3 Deliverables:

✓ Feed visible in artist + creator dashboards
✓ Real-time updates tested
✓ All landing pages drafted
✓ SEO structure defined

WOCHE 4: Polish + Admin Dashboard Prep

Ziel: Landing Pages polished, Admin Dashboard foundation, Performance audit

Track A: Landing Pages Polish (Frontend + Design)

Designer review + revisions (4 Stunden)
Mobile responsiveness test (2 Stunden)
German language proofreading (2 Stunden)
Stripe integration info added (1 Stunde)
Subtotal: 9 Stunden

Track B: Admin Dashboard Foundation (Backend/Frontend)

Account Management basic UI (5 Stunden)
Simulation Mode setup (3 Stunden)
Debugging Central (error log viewer) (2 Stunden)
Metrics Overview (basic dashboard) (2 Stunden)
Subtotal: 12 Stunden

Track C: Performance + Bundle Audit (Frontend + DevOps)

Lighthouse audit all pages (3 Stunden)
Image optimization (webp, lazy load) (4 Stunden)
Code splitting + tree-shaking (3 Stunden)
Bundle size analysis (2 Stunden)
Subtotal: 12 Stunden

Track D: Feed Polish (Frontend/Backend)

Infinite scroll UX testing (2 Stunden)
Performance optimization (2 Stunden)
Fix any edge cases (2 Stunden)
Subtotal: 6 Stunden

Week 4 Deliverables:

✓ All landing pages production-ready
✓ Admin dashboard basic functions working
✓ Performance: All pages Lighthouse > 85
✓ Bundle size < 150KB gzipped

WOCHE 5: Admin Dashboard Complete + Security

Ziel: Full Admin Dashboard, Security audit complete

Track A: Admin Dashboard Complete (Backend/Frontend)

Live Session Management (3 Stunden)
Support Tickets Interface (2 Stunden)
User Analytics Dashboard (3 Stunden)
Testing (3 Stunden)
Subtotal: 11 Stunden

Track B: Security Audit (Backend/Security)

RLS policy review (2 Stunden)
Rate limiting implementation (2 Stunden)
CORS + HTTPS verification (1 Stunde)
Penetration testing (3 Stunden)
Fix any vulnerabilities (variable)
Subtotal: 8+ Stunden

Track C: Final Polish (Frontend/Content)

Genre Explainer page (1.5 Stunden)
AGB + Refund Policy complete (1.5 Stunden)
Email templates finalize (1 Stunde)
Subtotal: 4 Stunden

Week 5 Deliverables:

✓ Admin dashboard fully functional
✓ Security audit passed (0 critical issues)
✓ All legal pages complete + reviewed
✓ All email templates finalized

WOCHE 6: Testing + Deployment

Ziel: Alles getestet, Live on breakout.now

Track A: Playwright Tests (QA + Frontend)

Test signup flow (1.5 Stunden)
Test submit song (1.5 Stunden)
Test create session (1.5 Stunden)
Test leaderboard voting (1 Stunde)
Error handling tests (2 Stunden)
Run full test suite (1 Stunde)
Subtotal: 8.5 Stunden

Track B: Smoke Tests (QA)

Create test accounts (1 Stunde)
Manual end-to-end flow (3 Stunden)
Cross-browser testing (2 Stunden)
Mobile testing (2 Stunden)
Subtotal: 8 Stunden

Track C: Monitoring Setup (DevOps)

Sentry integration (1 Stunde)
Datadog or similar setup (1.5 Stunden)
Alert rules configured (1 Stunde)
Subtotal: 3.5 Stunden

Track D: Deployment (DevOps/Backend)

Final environment variable check (0.5 Stunden)
Build optimization (1 Stunde)
Deploy to production (0.5 Stunden)
Verify all systems live (1 Stunde)
Subtotal: 3 Stunden

Track E: Launch Prep (Product/Content)

Write launch announcement (1.5 Stunden)
Prepare social media posts (2 Stunden)
Press release (1.5 Stunden)
Soft launch to 50 users (ongoing)
Subtotal: 5 Stunden

Week 6 Deliverables:

✓ 100% of Playwright tests passing
✓ Manual QA sign-off
✓ Site live on breakout.now
✓ All monitoring configured
✓ Soft launch successful (no critical bugs)

WOCHE 7: Public Launch + Monitoring

Ziel: Public launch successful, 24/7 monitoring

Activities:

Monitor error logs constantly (Day 1)
Fast-response to critical issues
Collect early user feedback
Celebrate! 🎉

DEPENDENCIES MATRIX

Content & Branding (Week 1)
  ├─→ Auth Improvements (Week 1)
  │   ├─→ Invite System (Week 2)
  │   ├─→ Onboarding (Week 2)
  │   └─→ Feed (Week 3)
  │
  ├─→ Email System (Week 1-2)
  │   └─→ Invite Emails (Week 2)
  │
  ├─→ Landing Pages (Week 2-4)
  │   └─→ SEO (Week 3-4)
  │
  └─→ Admin Dashboard (Week 4-5)
      └─→ Security Audit (Week 5)

  ├─→ Performance Audit (Week 4)
  │   └─→ Fixes (Week 4-5)
  │
  └─→ Testing (Week 6)
      └─→ Deployment (Week 6)

BLOCKERING SCENARIOS & CONTINGENCY

Scenario 1: Feed Implementation Takes Longer (Week 3 slips)

Impact: Artist/Creator experience delayed

Mitigation:

Simplify feed to MVP: Show only session notifications (no achievement feed yet)
Ship achievement system in Season 2
Still allows creators to stream and artists to submit

Delay Risk: +1 week

Scenario 2: Security Audit Finds Critical Issues (Week 5)

Impact: Can't ship if critical vulnerabilities

Mitigation:

Start security audit EARLY (Week 4 instead of 5)
Have security expert on standby
Fix critical issues immediately

Delay Risk: Variable (3-7 days typical)

Scenario 3: Designer/Video Production Bottleneck

Impact: Landing pages delayed, onboarding videos delayed

Mitigation:

Hire freelance designer + video editor early
Create briefing video outlines in Week 1
Use existing assets from competitor platforms as inspiration

Delay Risk: +3-5 days typical

Scenario 4: Stripe/Payment Integration Issues

Impact: Can't process paid submissions if applicable

Mitigation:

NOT critical for MVP launch (artists submit free, creators verify)
Defer paid features to Season 2
No payment processing needed for launch

Delay Risk: 0 (can skip for MVP)

GO/NO-GO CRITERIA BY WEEK

End of Week 1

✓ All breakout.now → breakout.now migrations complete
✓ Domain live + SSL working
✓ Auth flow updated
✓ Email system operational
✓ No critical tech debt

Go/No-Go Decision: If any of above failed → STOP, fix, reschedule launch

End of Week 2

✓ Invite system 100% functional
✓ Onboarding briefings recorded
✓ Landing Page Hero ready for review
✓ No critical bugs

Go/No-Go Decision: If invite system broken → 3-day delay acceptable

End of Week 3

✓ Feed working in both dashboards
✓ All landing pages drafted
✓ SEO structure defined
✓ Performance baseline measured

Go/No-Go Decision: If feed has major bugs → extend Week 4 for fixes

End of Week 4

✓ All landing pages mobile-responsive
✓ Admin dashboard basic functions
✓ Lighthouse scores > 85
✓ Bundle < 150KB gzipped

Go/No-Go Decision: If performance not met → 5-day code review

End of Week 5

✓ Security audit completed
✓ 0 critical vulnerabilities
✓ All legal pages reviewed
✓ Admin dashboard complete

Go/No-Go Decision: If security issues found → immediate fix window

End of Week 6

✓ All Playwright tests pass
✓ Manual QA sign-off
✓ Site live on breakout.now
✓ Monitoring configured
✓ Soft launch no critical issues

Go/No-Go Decision: Commit to public launch

PRIORITIZATION IF TIME RUNS SHORT

If you're running out of time before the deadline, prioritize in this order:

MUST-HAVE (MVP Launch)

✓ Content & Branding (domain working)
✓ Auth + Invite System
✓ Song Submission + Leaderboard (existing features)
✓ Creator Session + Voting (existing features)
✓ Security Audit + Fixes

NICE-TO-HAVE (Skip if necessary)

Feed/Home Hub (can ship Session Notifications only)
Admin Dashboard (can manage users via Supabase directly)
Fancy Landing Pages (ship plain vanilla pages if needed)
All legal pages (launch with basic Impressum only)

CAN-DEFER-TO-SEASON-2

A&R Tools
Paid features
Advanced metrics
Advanced admin features

Minimum MVP: Core platform working + security passed → launch and iterate

RESOURCE ALLOCATION

Recommended Team

1 Backend Developer: Supabase, Netlify Functions, Email, Auth
1 Frontend Developer: React components, Landing Pages, Feed UI
1 DevOps/Deployment: Netlify, Domain, Monitoring, Security
1 QA Engineer: Testing, Smoke tests, Bug reports
1 Product/Project Manager: Coordination, stakeholder updates, launch planning
1 Designer: Landing pages, UI polish (can be part-time)
1 Content Lead: Onboarding videos, Email templates, Copy

Total: ~7 people full-time, or 5 people + freelancers

COMMUNICATION PLAN

Daily (During Launch Push)

9 AM: 15-min standup (what's done, blockers, next steps)
5 PM: Async Slack update on progress

Weekly

Friday 4 PM: Weekly review + Go/No-Go decision
Friday 5 PM: Stakeholder update email

Pre-Launch (Week 6)

Daily syncs become 2x daily
Status dashboard updated hourly
Critical issues escalated to leadership immediately

NOTES

Alle Zeiten sind Schätzungen basierend auf durchschnittlicher Produktivität
Puffer für Meetings, Slack-Unterbrechungen, etc. bereits einkalkuliert (~20%)
Team sollte Focus-Zeit haben (minimal meetings, Slack mute)
Dokumentation / Knowledge Transfer sollte parallel laufen (wichtig für Post-Launch Wartung)

Implementierungs-Roadmap erstellt: 16. Februar 2026
Letzte Aktualisierung: [Datum hier]