Launch-Checkliste für Breakout.now

Technisch-actionable Checkliste für Pre-Launch bis Go-Live

Stand: 16. Februar 2026

1. CONTENT REVIEW & BRANDING (Woche 1-2)

Aufgaben

• Domain Migration: Alle Links breakout.now → breakout.now (Code, Docs, Social, Emails)

  • Files: /apps/web/src/**, public/, netlify/functions/, Dokumentation
  • Tools: Grep + Find für Verzeichnis-Scan
  • Estimated: 2-3 Stunden

• Umlaute-Fixes: Alle ae→ä, ue→ü, oe→ö in User-facing Text

  • Files: Komponenten-Text, Email-Templates, Landing Pages, FAQ
  • Fokus: Deutsche Sprache-Standards
  • Estimated: 1-2 Stunden

• App-Text Professional Review: Alle Texte in UI auf Deutsche Grammatik + Tone checken

  • Focus Areas: Modal-Dialoge, Error-Messages, Onboarding-Texte, Button-Labels
  • Tools: QA-Durchgang oder Native-Speaker Review
  • Estimated: 3-4 Stunden

• Brand-Assets Update: Logo, Farben, Schriftarten auf breakout.now-Design prüfen

  • Files: public/favicon.ico, public/logo.*, Tailwind Theme
  • Estimated: 1 Stunde (oder Design-Overhaul je nach Bedarf)

Acceptance Criteria:

• Keine breakout.now Links/Referenzen mehr in Production-Code
• Umlaute korrekt in allen Komponenten
• QA-Pass für Deutsche Sprachversion bestanden

2. HOME HUB / FEED REDESIGN (Woche 2-4)

Tech Stack

• Frontend: React 19 + Tailwind v4
• Backend: Supabase Realtime für Live-Updates
• Components: /apps/web/src/components/

Aufgaben

A. Unified Feed (Artist & Creator View)

• Schema Update: feed_entries Table + RLS für Feed-Zugriff

  • Fields: id, user_id, type (message|session_update|achievement), content, created_at, read_at
  • RLS: Authenticated users können eigene + followed users' Feed lesen
  • Estimated: 2 Stunden

• Feed Component (/components/shared/UnifiedFeed.tsx)

  • Zeigt Messages + Session-Updates + Achievements gemischt
  • Infinite Scroll mit @tanstack/react-query
  • Real-time Updates via Supabase Realtime
  • Estimated: 6-8 Stunden

• Artist View: 3 Selected Sessions + Message Stream

  • Modified /pages/ArtistDashboard.tsx
  • Shows: Top 3 current sessions (by leaderboard position), all direct messages
  • Estimated: 4-5 Stunden

• Creator View: Referral Program + Feed Integration

  • Shows: Referral stats, earnings, feed of events
  • Modified /pages/HostDashboard.tsx
  • Estimated: 4 Stunden

• Support Channel (separate from Feed)

  • New route: /pages/SupportChat.tsx
  • Direct messaging to support team
  • Estimated: 2 Stunden

Acceptance Criteria:

• Feed loaded in <1 second (first 20 items)
• Real-time updates visible within 2 seconds
• Artist sees exactly 3 sessions + messages
• Creator sees referral metrics accurately
• Support channel accessible from main nav

3. ONBOARDING BRIEFINGS (Woche 2-3)

Video/Text Assets (in German)

• Viewer Briefing: "Was ist Breakout.now?" (2-3 min)

  • What: Song-Submission Plattform
  • Why: Get live feedback, discover creators, build fanbase
  • How: Submit song, wait for creator reaction, upvote good ones
  • Asset: Video + /pages/OnboardingViewer.tsx Component
  • Estimated: 3 Stunden

• Creator Briefing: Live-Session Tutorial (3-5 min)

  • How to start session, enable submissions, read leaderboard, award points
  • Interface walkthrough
  • Asset: Video + Interactive guided tour
  • Estimated: 4 Stunden

• Artist Briefing: System Explanation (2-3 min)

  • How merit system works, how to climb leaderboard
  • A&R exposure pathway (Season 2)
  • Asset: Video + /pages/OnboardingArtist.tsx
  • Estimated: 3 Stunden

• Onboarding Flow Integration

  • Show appropriate briefing based on user type (viewer|artist|creator)
  • Track completion in auth_metadata table
  • Redirect to dashboard after completion
  • Estimated: 2 Stunden

Acceptance Criteria:

• All 3 briefing videos recorded + subtitled (German)
• 90%+ of new users complete onboarding
• Users skip briefing and land in correct dashboard view

4. EMAIL SYSTEM (Woche 3-4)

Setup

• Email Provider: Transactional email (SendGrid, Mailgun, or AWS SES)

  • Register domain: noreply@breakout.now
  • Set up SPF, DKIM, DMARC records
  • Estimated: 1 Stunde

• Email Templates (HTML + German Text)

  • Double-opt-in verification
  • Session notification ("Creator going live")
  • Daily digest option
  • Leaderboard milestone
  • Support responses
  • Estimated: 4-5 Stunden

• Backend Integration (/netlify/functions/sendEmail.mts)

  • Function to send templated emails
  • Idempotency key for email duplication prevention
  • Rate limiting (max 5 emails per user per day unless opted in for digest)
  • Estimated: 3-4 Stunden

• Notification Preferences

  • New table: notification_preferences
  • Fields: user_id, email_on_session, daily_digest, email_on_mention, etc.
  • UI Component: /components/settings/NotificationPreferences.tsx
  • Estimated: 2 Stunden

Acceptance Criteria:

• Email delivery rate > 98%
• All SPF/DKIM records passing
• Unsubscribe link functional on all emails
• Double-opt-in working for new users
• Email templates beautiful in all clients (Gmail, Outlook, Apple Mail)

5. LOGIN IMPROVEMENTS (Woche 3)

Current State Review

• Audit existing Supabase Auth setup (currently using email + Google OAuth)
• Test password reset flow
• Check Google OAuth UX

Improvements

• Evaluate: Remove Google Auth?

  • Decision: Keep or remove based on analytics
  • If remove: Migrate existing OAuth users to email-based
  • Estimated: 2-3 Stunden (if removing)

• Password Double-Entry on Signup

  • Add confirmation field to signup form
  • Validate match client-side
  • File: /components/auth/SignupForm.tsx
  • Estimated: 1 Stunde

• Login from All Pages

  • Add "Login" link in header/nav (if not authenticated)
  • Create /pages/LoginPage.tsx (currently might be modal-only)
  • Estimated: 1 Stunde

• "Kein Account?" Flow → Invite Request

  • Change "Create Account" flow to invitation request
  • Email: "You're invited! Click to join"
  • Flow: Invite → Email → Click Link → Auto-signup
  • File: Modify /components/auth/SignupForm.tsx + new requestInvite.mts function
  • Estimated: 4-5 Stunden

Acceptance Criteria:

• Login accessible from home page
• Password confirmation prevents typos (test 10 users)
• Invite system sends within 5 seconds
• Clicking invite link auto-authenticates user
• Google Auth decision made + implemented

6. NEW LANDING PAGES (Woche 4-5)

Pages to Build

All pages in German, mobile-first, Tailwind v4

• Main Landing Page (/pages/Landing.tsx)

  • Hero: "Deine Songs. Live bewertet. Professionell discovered."
  • Value props (for each user type): Artists | Creators | A&Rs
  • Features grid, CTA buttons
  • Estimated: 6-8 Stunden

• Creator Landing (/pages/CreatorOnboarding.tsx)

  • "Engage your audience with live music discovery"
  • Feature: Easy session setup, earn referrals, track metrics
  • Call-to-action: "Start streaming now"
  • Estimated: 4 Stunden

• Artist Landing (/pages/ArtistOnboarding.tsx)

  • "Get discovered. Build your fanbase. Meet A&Rs."
  • Feature: Leaderboard pathway, live feedback, merit rewards
  • Call-to-action: "Submit your music"
  • Estimated: 4 Stunden

• A&R Landing (/pages/AROnboarding.tsx)

  • "Discover emerging talent through live community validation"
  • Feature: Merit-based ranking, verified artists, direct artist access
  • Call-to-action: "Register as A&R" (geplant für Season 2)
  • Estimated: 4 Stunden

• Pricing Page (/pages/Pricing.tsx)

  • Free tier (artists), Creator monetization, A&R tools (Season 2)
  • Stripe integration info (no transaction fees shown yet; will add in Season 2)
  • Estimated: 3 Stunden

• FAQ (/pages/FAQ.tsx)

  • Artist FAQs, Creator FAQs, General FAQs (all German)
  • Interactive accordion component
  • Estimated: 2 Stunden

• Genre Explainer (/pages/Genres.tsx)

  • "Warum Musik-Genres wichtig sind auf Breakout.now"
  • List all supported genres with descriptions
  • Estimated: 2 Stunden

• Legal Pages

  • Impressum (/pages/Impressum.tsx): Company info + legal
  • Datenschutz (/pages/Datenschutz.tsx): GDPR + data handling
  • AGB (/pages/AGB.tsx): Terms of service
  • Estimated: 3 Stunden (Legal review needed)

• Refund Policy (/pages/RefundPolicy.tsx)

  • Clear policy for paid session submissions (future feature)
  • Estimated: 1 Stunde

• Footer Navigation

  • Update footer with all new pages
  • File: /components/shared/Footer.tsx
  • Estimated: 1 Stunde

Acceptance Criteria:

• All pages load in < 2 seconds (Lighthouse > 80)
• Mobile responsive (test on iPhone 12 + Android)
• All German text proofread by native speaker
• Legal pages pass GDPR + German law check
• SEO meta tags on all pages

7. SEO (Woche 5)

Technical SEO

• Public Community Profiles: Make artist leaderboard pages publicly indexable

  • Route: /artist/:artistName (public view)
  • Meta tags: Artist name, top track, stats
  • Allow Google crawl (robots.txt allow)
  • Estimated: 3 Stunden

• Open Graph / Social Meta Tags

  • Add og:title, og:description, og:image to all pages
  • File: apps/web/public/index.html or meta tag injection
  • Estimated: 2 Stunden

• Sitemap + Robots.txt

  • Generate sitemap.xml for all public routes
  • robots.txt: Allow Google, exclude admin routes
  • File: public/sitemap.xml, public/robots.txt
  • Estimated: 1 Stunde

• Stripe Verification

  • Add verification meta tag for Stripe API compliance (if needed)
  • Test Stripe payment flow for SEO/indexing impact
  • Estimated: 1 Stunde

Acceptance Criteria:

8. HYBRID INVITE SYSTEM (Woche 4)

Architecture

• Per-Forum Invite Links (unlimited but appears limited)

  • Table: invite_links (id, creator_id, community_forum, code, uses_count, max_uses_displayed)
  • Route: /invite/:code → Auto signup + forum tagged
  • UI: Creator dashboard shows "Generate invite link for [forum]"
  • Estimated: 4 Stunden

• Invite Appearance (UX trick)

  • Show "3 of 10 invites used" even if creator has unlimited
  • Keeps exclusivity feeling without actual limitation
  • Estimated: 1 Stunde

Acceptance Criteria:

• Creator can generate unlimited invite links
• Link shows "X of 10 used" (fake cap)
• New user clicking link is auto-tagged with forum origin
• Analytics show which forums convert best

9. DEV INTERFACE / ADMIN DASHBOARD (Woche 5-6)

Location

• Admin Routes: /admin/* (protected by is_admin role in Supabase)
• Auth: Service Role Key required (environment variable check)

Features

• Account Management

  • List all users, search by email/name
  • Ban/unban users, reset password
  • View user metadata, session history
  • Estimated: 5 Stunden

• Simulation Mode

  • Create test sessions without real streaming
  • Inject test votes into leaderboard
  • Test payment flow in sandbox mode
  • Estimated: 4 Stunden

• Debugging Central

  • View all recent errors (from Sentry or logs)
  • Replay user sessions
  • Check queue_entries atomic lock status
  • Estimated: 3 Stunden

• Metrics Overview

  • DAU (daily active users), MAU
  • Session count + avg viewer count
  • Revenue metrics (from Stripe)
  • Estimated: 3 Stunden

• Live Session Management

  • View all active sessions
  • Manually end session, inject test entries
  • Monitor stream health
  • Estimated: 3 Stunden

• Support Tickets

  • View submitted support requests
  • Reply to users
  • Mark as resolved
  • Estimated: 2 Stunden

Acceptance Criteria:

• Admin panel loads under 2 seconds
• All user data queries use proper RLS checks
• Service role key never exposed in client code
• Simulation mode clearly labeled (not production)

10. PERFORMANCE & SECURITY (Woche 6)

Performance

• Error & Bottleneck Check

  • Run Lighthouse on all main pages (goal: > 85 on all)
  • Fix images (webp, lazy loading)
  • Code split components (dynamic imports)
  • Estimated: 6-8 Stunden

• Bundle Size Audit

  • Run npm run build --prefix apps/web + analyze dist/
  • Target: < 150KB gzipped JS
  • Remove unused dependencies
  • Estimated: 3-4 Stunden

Security

• Playwright Tests

  • Test critical user flows: signup, submit song, create session
  • Test error handling (malformed input, network errors)
  • Run on CI/CD before deployment
  • Estimated: 6-8 Stunden

• Manipulation Protection

  • Verify all RLS policies (no direct table access for anon)
  • Audit Netlify Function permissions (use service role key only when needed)
  • Check price computation cannot be exploited
  • Estimated: 4 Stunden

• Rate Limiting

  • Add rate limiting to all public functions (signup, submit song)
  • Goal: Max 5 requests per IP per minute for submissions
  • Estimated: 2 Stunden

• CORS & HTTPS

  • Verify CORS headers on Netlify Functions
  • Enforce HTTPS in production
  • Estimated: 1 Stunde

Acceptance Criteria:

• All Lighthouse scores > 85
• Bundle < 150KB gzipped
• Playwright tests pass 100%
• Security audit found 0 critical issues
• RLS policies validated by third-party security review (optional but recommended)

11. DEPLOY ON BREAKOUT.NOW (Woche 6)

Infrastructure

• Domain Setup

  • SSL certificate (Let's Encrypt via Netlify automatic)
  • DNS records configured
  • Email SPF/DKIM/DMARC verified
  • Estimated: 1 Stunde

• Build & Deploy

  • Run npm run build --prefix apps/web in CI/CD
  • Deploy to Netlify production branch
  • Verify environment variables set (Supabase URL, Stripe keys, etc.)
  • Estimated: 1 Stunde

• Smoke Tests

  • Test signup flow end-to-end
  • Test submit song functionality
  • Test creator session + leaderboard
  • Estimated: 2 Stunden

• Monitoring Setup

  • Enable Sentry for error tracking
  • Set up Datadog or similar for uptime monitoring
  • Configure alerts for > 5% error rate
  • Estimated: 2 Stunden

Acceptance Criteria:

• Site loads on breakout.now domain
• All pages load < 2 seconds
• HTTPS working, no mixed content warnings
• Emails send from noreply@breakout.now
• Error tracking logging all errors

12. LAUNCH (Woche 6-7)

Pre-Launch

• QA Final Pass

  • Run full test suite
  • Manual testing on production domain
  • Estimated: 4 Stunden

• Community Announcement

  • Write launch announcement
  • Post on social media, Discord, email list
  • Estimated: 2 Stunden

• Press Kit

  • Write press release
  • Prepare assets for tech blogs/media
  • Estimated: 2 Stunden

Launch Day

• Monitor Uptime

  • Watch error logs + analytics
  • Have team on standby for issues
  • Estimated: 4 Stunden (parallel with soft launch)

• Soft Launch (24 hours before public)

  • Invite 50-100 early users
  • Collect feedback
  • Fix any critical issues

• Public Launch

  • Open signups to general public
  • Announce on all channels
  • Monitor server capacity + performance

Acceptance Criteria:

• 0 critical bugs on launch day
• > 99% uptime during first 24 hours
• Support team responds to inquiries within 2 hours
• First 100 users sign up within 6 hours
• No data loss or security incidents

TOTAL ESTIMATED EFFORT

Team Size Assumption: 2 developers (backend + frontend), 1 designer, 1 QA

Realistic Timeline: 6-8 weeks with full team

NOTIZEN

• Alle Zeiten sind Schätzungen. Tatsächliche Dauer kann variieren.
• "Season 2 geplant" Features sollten klar als Future markiert sein (z.B. A&R-Sektor).
• Regelmäßige Standup-Meetings empfohlen (täglich während Launch-Phase).
• Backup-Plan: Wenn Zeit knapp wird, priorisieren: 1, 5, 6, 12 (MVP launchbar mit Essentials).

Checkliste erstellt: 16. Februar 2026
Für Fragen oder Anpassungen: [Kontaktinfo hier]