Product Roadmap

Product Roadmap: Q1 2026 Full-Feature Production Launch

Full-feature production launch roadmap for PhenomApp (Peregrine version) targeting production deployment on March 15, 2026. This roadmap delivers the complete PhenomApp feature set (except AR identification modes) through parallel development.

Created: January 21, 2026 Status: Ready for Implementation Current Date: January 21, 2026 Days to Production: 53 days (7.5 weeks) Days to Beta: 39 days (5.5 weeks)

Executive Summary

The PhenomApp roadmap has been accelerated to full-feature production launch by March 15, 2026. This represents a compressed development cycle delivering the complete feature set (except AR modes) through parallel development. The strategy emphasizes:

1. Phase 0: Administrative Setup ✅ COMPLETED (January 21, 2026) - Apple/Google account provisioning complete, no blockers for Sprint 1
2. Three 2-week development sprints (Jan-Mar 2026) with parallel development streams
3. Sprint 1: Critical infrastructure foundation
4. Sprint 2: MVP integration + sensors + OAuth
5. Sprint 3 (EXPANDED): Full feature implementation including C2PA, 3D globe, heatmaps, gamification, teams, desktop website, and 3rd party integrations
6. One-week Beta Testing Phase (Mar 1-7, 2026) with 20-50 beta testers validating complete feature set
7. One-week Production Deployment (Mar 8-15, 2026) for App Store and Google Play release
8. Production Launch targeting March 15, 2026 or earlier upon store approval

Philosophy: Complete, tested, production-ready. Beta is for final validation before public release.

Key Differentiator: PhenomApp will be the first C2PA-enabled phenomenon documentation app with 3D globe visualization and gamification, allowing users to create cryptographically signed, verifiable video evidence of phenomena using Publish Own Site, Syndicate Everywhere (POSSE) methodology with advanced discovery and engagement features.

Team: @goldeneagle3636 (Backend/DevOps) + @jonathan.hart (Frontend Lead) Target Market: Phenomenon researchers, documentation enthusiasts, media organizations Production Launch Date: March 15, 2026

Timeline Overview

2026 Q1 Timeline - Full-Feature Production Launch with EAS Deployment
|---Phase 0---|---Sprint 1---|---Sprint 2---|---Sprint 3 (EXPANDED)---|---Beta---|---Production---|
Admin Setup   Foundation     Integration    All Features + C2PA + Viz Launch    Test      Launch
Dec-Jan 2026  Jan 20-Feb 2   Feb 3-Feb 16   Feb 17-Mar 1                      Mar 1-7   Mar 8-15
Apple/Google  EAS Config     API + OAuth    + EAS Pipeline                     TestFlight  App Store
Account Setup CI/CD          Sensors       All Features                        Internal    Google Play

Sprint Timeline with Dates

Viewing the Roadmap: GitHub Project Iterations

All sprints have been configured as Iterations in the GitHub Project, allowing you to view, filter, and track work by sprint.

Configured Iterations

The following iterations are configured in the Peregrine Project Board:

How to View by Iteration

Method 1: Roadmap View (Recommended for Sprint Planning)

1. Go to: https://github.com/orgs/Phenom-earth/projects/3/views/4
2. The Roadmap view displays all issues organized by iteration in a timeline format
3. Each iteration appears as a horizontal swim lane with its issues
4. You can see sprint duration, dates, and issue dependencies

Method 2: Board View with Iteration Filter

1. Go to: https://github.com/orgs/Phenom-earth/projects/3
2. Click “Filter” at the top
3. Type: iteration:"Sprint 1 - Foundation" (or any sprint name)
4. View only the filtered sprint issues in Board layout

Method 3: Table View Grouped by Iteration

1. Go to Table view in the project
2. Click “Group by” dropdown
3. Select “Iteration”
4. Issues will be organized into collapsible sections by sprint

Method 4: Create Custom Sprint Views

1. Click “New view” next to the view tabs
2. Choose Board or Table layout
3. Name it “Sprint 1”, “Sprint 2”, etc.
4. Add filter: iteration:"Sprint 1 - Foundation"
5. Save the view for quick access

Issue Distribution by Sprint

Sprint 1 (7 issues):

• PhenomApp #16, #17, #18, #19, #20, #33, #34

Sprint 2 (6 issues):

• PhenomApp #21, #22, #23, #24, #31, #32

Sprint 3 (10 issues):

• PhenomApp #25, #26, #27, #28, #29, #30, #35
• www #57, #58, #59

All issues have been assigned to their respective iterations and are visible in the project board.

Phase 0: Administrative Setup & Identity Verification ✅ COMPLETED

Timeline: December 2025 - January 2026 Status: ✅ COMPLETED - January 21, 2026 Owner: Matthew Stevens

All Phase 0 administrative tasks have been completed ahead of Sprint 1. Apple Developer Program enrollment, Google Play Console setup, and all service accounts are fully configured and ready for EAS integration.

Administrative Milestones

Phase 0 Completion Summary

Completed: January 21, 2026

All administrative setup tasks have been successfully completed:

✅ Apple Developer Program:

• D-U-N-S number obtained from Dun & Bradstreet
• Apple Developer Program enrollment approved
• Apple Team ID obtained and documented
• Organization account configured (not personal)
• Ready for EAS iOS builds and App Store submission

✅ Google Play Console:

• Google Play Developer Account created and active
• Developer profile setup completed
• Service Account JSON key generated with Release Manager permissions
• Organization account configured
• Ready for EAS Android builds and Play Store submission

✅ Security & Documentation:

• All credentials stored securely in 1Password vault
• Team access configured for both platforms
• EAS CLI authentication tested and verified
• Setup procedures documented for team reference

Success Criteria for Phase 0

• ✅ D-U-N-S number obtained from Dun & Bradstreet
• ✅ Apple Developer Program enrollment approved
• ✅ Apple Team ID obtained and documented
• ✅ Google Play Developer Account active and verified
• ✅ Google Service Account JSON key generated with Release Manager permissions
• ✅ Both accounts configured for organization (not personal)
• ✅ Credentials stored securely in 1Password vault (chmod 600)
• ✅ Team has access to both accounts
• ✅ EAS CLI can authenticate with both platforms
• ✅ All documentation complete before Sprint 1 begins (Jan 20, 2026)

Critical Notes

• Apple identity verification can take 2-4 weeks for organizations (faster for individuals, 1-3 days)
• Google Play account activation is usually instant but can take up to 48 hours
• MUST be completed before Sprint 1 begins (Jan 20, 2026)
• Delays in Phase 0 directly block Sprint 1 EAS pipeline configuration
• If Apple enrollment delayed, consider Android-only launch for March 15, iOS follows in v1.0.1

References

• Apple Enrollment: https://developer.apple.com/programs/enroll/
• Google Play Console: https://play.google.com/console/about/
• EAS Deployment Guide
• D-U-N-S Lookup: https://www.dnb.com/duns-number.html

Mermaid Gantt Chart

gantt
    title PhenomApp Full-Feature Production Launch 2026 with EAS
    dateFormat YYYY-MM-DD

    section Phase 0
    Admin & Apple/Google Setup :phase0, 2025-12-01, 2026-01-20

    section Sprint 1
    Foundation & EAS Pipeline :s1, 2026-01-20, 2026-02-02

    section Sprint 2
    MVP Integration + Sensors + OAuth :s2, 2026-02-03, 2026-02-16

    section Sprint 3 (All Features)
    C2PA + 3D Globe + Heatmaps + Gamification + Teams + Desktop + Integrations :crit, s3, 2026-02-17, 2026-03-01

    section Beta Testing
    Full Feature Testing + EAS Builds :beta, 2026-03-01, 2026-03-07

    section Production Launch
    Full-Feature App Store & Google Play Deployment :crit, milestone, prod, 2026-03-08, 2026-03-15

Production Launch Feature Set (March 15, 2026)

Included in Production Launch (v1.0.0)

Essential Features for Production Release:

• ✅ Full user authentication: Email, Google OAuth, and Apple OAuth sign-in
• ✅ Single-button video recording with GPS location capture
• ✅ C2PA cryptographic signing on 100% of videos (CORE FEATURE)
• ✅ C2PA metadata embedding with sensor data and GPS coordinates
• ✅ Metadata editing (location, category, title, description)
• ✅ Advanced video editing with trim, filters, and effects
• ✅ Video upload to AWS S3 with CloudFront CDN delivery
• ✅ Video feed display with endless scroll
• ✅ Map view with H3 hexagonal clustering
• ✅ 3D interactive globe view with phenomena visualization
• ✅ Heatmap layers by category (UAP, Cryptid, Paranormal, etc.)
• ✅ User profiles with statistics and achievements
• ✅ Gamification system with points, badges, and leaderboards
• ✅ Multi-user phenomenon detection rewards
• ✅ Team formation and coordination
• ✅ Advanced search and filtering capabilities
• ✅ Event detail view with context visualization
• ✅ Comprehensive onboarding and tutorials
• ✅ Desktop website for web-based viewing and administration
• ✅ 3rd party integrations: MUFON, NUFORC, NASA data feeds
• ✅ Permission handling (camera, microphone, location)
• ✅ Error handling and automatic retry logic
• ✅ C2PA signature verification support
• ✅ Production API infrastructure and scaling
• ✅ Support documentation and user guides

ONLY Feature Deferred to Future Version

Feature Deferred to v1.1+:

• ⏳ AR Identification Mode (Real-time satellite, airplane, planet, ship tracking overlays) - v1.1

Sprint Breakdown

Sprint 1: Critical Foundation + EAS Pipeline (Jan 20 - Feb 2, 2026)

Priority: CRITICAL - Blocks all development Duration: 2 weeks (14 days) Target Completion: February 2, 2026 Team: @goldeneagle3636 (Backend/DevOps), @jonathan.hart (Frontend) Dependencies: Phase 0 MUST be complete

Issues in This Sprint

What We’re NOT Doing (Deferred)

• ✗ GitHub Actions CI/CD (Issue #18) - Defer to Sprint 2
• ✗ Frontend TypeScript refactor (Issue #19) - Use existing structure
• ✗ Docker Compose environment (Issue #20) - Set up manually or basic setup

Sprint 1 Success Criteria

• ✓ PostgreSQL database running locally with basic schema
• ✓ Hasura GraphQL API operational at http://localhost:8080
• ✓ Core tables created: PhenomUser, VideoRecord, Location, SensorData
• ✓ ESLint and Prettier configured
• ✓ Jest basic test framework in place
• ✓ EAS build profiles configured (Development, Preview, Production)
• ✓ EAS secrets management operational
• ✓ iOS and Android build settings configured in eas.json
• ✓ Signing credentials managed by EAS (iOS provisioning profiles, Android keystore)
• ✓ All Sprint 1 tests passing (50%+ coverage)
• ✓ Team can start implementing API queries
• ✓ EAS build pipeline tested and ready for Sprint 2

Week-by-Week Breakdown

• Week 1 (Jan 20-26):
  • Issue #16: Hasura + PostgreSQL setup (Begin immediately)
  • Issue #17: ESLint/Prettier configuration
  • Issue #33: EAS build profiles configuration (eas.json setup)
• Week 2 (Jan 27-Feb 2):
  • Complete #16 schema (users, videos, locations, sensor_data tables)
  • Finalize #17 testing framework
  • Complete #33 iOS and Android build settings
  • Issue #34: EAS secrets management setup
  • Integration testing for basic API queries
  • Test EAS builds for all profiles
  • Sprint 1 completion by Feb 2

Dependencies

• Blocking: Phase 0 completion (Apple/Google accounts MUST be ready)
• Blocked By: None - Sprint 1 is foundational

Sprint 2: MVP Integration + Sensor Data + OAuth (Feb 3 - Feb 16, 2026)

Priority: HIGH - Enable real API, sensor capture, and full authentication Duration: 2 weeks (14 days) Target Completion: February 16, 2026 Team: @goldeneagle3636 (Backend), @jonathan.hart (Frontend)

Issues in This Sprint

What We’re NOT Doing (Deferred)

• ✗ AWS S3 + CDN setup (Issue #24) - Basic cloud storage setup
• ✗ Advanced sensor data - Just basics needed for C2PA

Sprint 2 Success Criteria

• ✓ GraphQL API queries for user auth and video records
• ✓ Email-based authentication working
• ✓ Google OAuth sign-in fully functional
• ✓ Apple OAuth sign-in fully functional
• ✓ All three authentication methods can create user accounts
• ✓ OAuth tokens stored securely
• ✓ Users can sign up and log in with any of the three methods
• ✓ JWT tokens generated and validated
• ✓ Basic API client in frontend
• ✓ Login flow end-to-end functional
• ✓ User signup and profile creation working
• ✓ Sensor data collection API endpoints working
• ✓ Basic sensor data (GPS, device motion, timestamp) stored with video metadata
• ✓ API responses match frontend expectations
• ✓ CI/CD pipeline includes EAS build triggers
• ✓ All Sprint 2 tests passing (60%+ coverage)
• ✓ Development team can begin video recording feature work

Week-by-Week Breakdown

• Week 1 (Feb 3-9):
  • Issue #21: Core GraphQL endpoints (users, auth)
  • Issue #23: Full authentication implementation (Email + Google + Apple OAuth)
  • Issue #26: Sensor data schema and collection endpoints
  • Issue #22: Begin API client setup
  • Issue #18: CI/CD pipeline with EAS integration
• Week 2 (Feb 10-16):
  • Complete #21, #23, #22, #26
  • End-to-end auth flow testing for all three methods
  • Sensor data integration testing
  • Performance testing (API < 500ms response time)
  • CI/CD pipeline fully functional with EAS
  • Sprint 2 completion by Feb 16

Dependencies

• Depends On: Sprint 1 completion (Hasura schema + EAS pipeline)
• Blocking: Sprint 3 (video recording feature + C2PA signing)

Sprint 3: Full Feature Implementation + C2PA (Feb 17 - Mar 1, 2026)

Priority: CRITICAL - All production features Duration: 2 weeks (13 days) Target Completion: March 1, 2026 Team: Development team working in parallel streams Effort: Compressed timeline with parallel development

Major Feature Categories in Sprint 3

Team Assignments:

• Backend/API: @goldeneagle3636 (Auth, APIs, 3rd party integrations)
• Frontend Core: @jonathan.hart (Video, C2PA, core UX)
• Frontend Viz: TBD (3D globe, heatmaps, map views)
• Frontend Social: TBD (Gamification, teams, profiles)
• Desktop Web: TBD (Desktop website development)
• Video Processing: TBD (Advanced video editing)

Core Features (Parallel Streams)

Stream 1: Video & C2PA (Frontend Core + Backend)

Stream 2: Discovery & Visualization (Frontend Viz + Backend)

Stream 3: Social & Engagement (Frontend Social + Backend)

Stream 4: User Experience (Frontend + Backend)

Stream 5: Web & Integrations (Backend + Frontend Web)

Sprint 3 Success Criteria

• ✓ All features from all parallel streams completed and integrated
• ✓ Camera and microphone permissions working (iOS/Android)
• ✓ Single-button recording interface fully functional
• ✓ Live camera preview with duration timer
• ✓ Basic GPS location capture integrated with video
• ✓ Advanced video editing with trim, filters, and effects
• ✓ 100% of recorded videos are C2PA signed
• ✓ C2PA manifests include GPS coordinates and device sensor data
• ✓ Signature verification detects tampering correctly
• ✓ Signing performance < 30 seconds for typical video
• ✓ Video upload with progress tracking
• ✓ Basic feed showing uploaded videos
• ✓ Retry logic with exponential backoff for failed uploads
• ✓ Battery drain acceptable during recording (< 40%/hour)
• ✓ 3D globe rendering correctly with phenomena visualization
• ✓ Heatmap layers functional and queryable by category
• ✓ Advanced search and filtering working across all attributes
• ✓ Event detail view showing full context
• ✓ Gamification system awarding points correctly
• ✓ User profiles displaying achievements and statistics
• ✓ Team formation and coordination features functional
• ✓ Onboarding and tutorials complete
• ✓ Desktop website deployed and functional
• ✓ 3rd party integrations (MUFON, NUFORC, NASA) active
• ✓ Videos verifiable using c2pa-tool or Verify.org
• ✓ Works reliably on both iOS and Android
• ✓ Crash rate < 5% (beta target)
• ✓ All Sprint 3 tests passing
• ✓ Ready for beta testing and production submission

Week-by-Week Breakdown

• Week 1 (Feb 17-23) - Parallel Feature Development:

  • Stream 1: Issue #24 (S3+CDN), #25 (Permissions), #26 (Recording UI), #29 (C2PA signing) - START IMMEDIATELY
  • Stream 2: Issue #31 (3D Globe), #32 (Heatmaps), #33 (Detail View)
  • Stream 3: Issue #35 (Rewards), #36 (Profiles), #37 (Teams)
  • Stream 4: Issue #38 (Onboarding)
  • Stream 5: Issue #39 (Desktop), #40 (3rd Party APIs)
  • Integration: Begin connecting streams

• Week 2 (Feb 24-Mar 1) - Integration & Testing:

  • Stream 1: Complete C2PA signing (#29, #30), video editing (#27), upload (#28)
  • Stream 2: Complete 3D globe, heatmaps, search (#31-34)
  • Stream 3: Complete gamification and teams (#35-37)
  • Stream 4: Complete onboarding (#38)
  • Stream 5: Complete desktop website and 3rd party integrations (#39-40)
  • Comprehensive Integration Testing:
    • All features working together
    • Sign multiple videos with different sensor data
    • Verify signatures with external tools
    • Tamper detection testing
    • Performance benchmarking
    • Cross-feature user workflows
  • Comprehensive testing on real devices
  • Bug fixes and performance optimization
  • Final production readiness check
  • Beta Launch: March 1, 2026

Dependencies

• Depends On: Sprint 2 completion (API, auth, sensor data)
• Blocking: Beta testing and production launch
• Critical Path: C2PA signing must complete by Feb 28 to allow 2 days of verification testing

Development Coordination

IMPORTANT: The compressed timeline requires parallel development streams across all features during Sprint 3. This requires:

• Clear parallel development boundaries
• Defined API contracts between streams
• Daily integration testing
• Rapid issue resolution
• Pre-planned contingencies for dependencies

Beta Testing Phase (Mar 1-7, 2026)

Duration: 1 week (7 days) Parallel Track: Final validation and bug fixes before production Primary Focus: Complete feature validation including all new additions

Beta Distribution

iOS: TestFlight distribution Android: Google Play internal testing track

Beta Tester Recruitment

Target: 20-50 beta testers Sources:

• Personal network
• Reddit communities (r/UAP, r/paranormal)
• Discord communities
• UFO/cryptid enthusiast forums
• MUFON contacts (mutual UFO network)

Messaging: “Help test the first cryptographically signed phenomenon documentation app with 3D globe and gamification”

Beta Activities

• Daily bug fixes and hotfixes for critical issues
• Beta tester feedback collection via in-app forms and surveys
• Performance monitoring and optimization
• Critical issue resolution with rapid deployment
• C2PA verification testing - Validate signatures work externally
• All feature testing - 3D globe, heatmaps, gamification, teams, desktop website
• Device compatibility testing across iOS/Android versions
• Network condition testing (WiFi, cellular, poor connection)
• Production deployment preparation - review store submission requirements
• EAS build distribution - Verify TestFlight and internal testing delivery working smoothly

Success Criteria for Beta Phase

• ✓ Email, Google, and Apple authentication all working
• ✓ Users can sign up with any of the three methods
• ✓ OAuth token refresh working correctly
• ✓ 100% of beta testers can complete core workflow (record, sign, upload, view)
• ✓ 100% of beta testers can authenticate successfully
• ✓ 100% of beta testers can access and interact with 3D globe
• ✓ 100% of beta testers can view heatmaps and use advanced search
• ✓ 100% of beta testers can see gamification points and achievements
• ✓ 100% of beta testers can form teams and coordinate
• ✓ Desktop website accessible and functional for all testers
• ✓ 3rd party integrations (MUFON, NUFORC, NASA) data displaying correctly
• ✓ Crash rate < 5% on production devices
• ✓ C2PA signing working on 95%+ of videos
• ✓ Signatures verifiable with external tools (c2pa-tool, Verify.org)
• ✓ No blocking bugs for production
• ✓ Performance acceptable (< 30s signing time, < 2min upload for 50MB, 3D globe smooth 60 FPS)
• ✓ All critical and high-priority bugs fixed
• ✓ Production scaling plan validated
• ✓ App store submission materials prepared
• ✓ EAS build pipeline verified for both platforms

Beta Feedback Collection

• In-app feedback form (after first 3 videos)
• Daily survey via Google Forms
• Email check-ins with beta coordinator
• Discord/WhatsApp group for real-time discussion
• Crash reporting via Sentry or Firebase Crashlytics
• C2PA verification testing - Testers verify signatures using external tools
• Feature-specific surveys for 3D globe, gamification, teams, desktop web

Production Deployment Phase (Mar 8-15, 2026)

Duration: 1 week (8 days) Activities: App Store/Play submission, approval process, production launch Primary Focus: Successful public deployment to both app stores with all features live

Pre-Deployment Preparation (Mar 1-7, overlaps with Beta)

Build Artifacts:

# Generate production builds for both platforms
eas build --profile production --platform all

# Verify builds completed and artifacts ready
eas build:list --limit 2

Deployment Activities (Mar 8-15)

Day 1-2 (Mar 8-9): Build Artifacts & Manual Upload Preparation

# Build production versions
eas build --profile production --platform all

# Verify builds
eas build:list --limit 2

# Download artifacts for manual inspection
# Note: First Android release requires manual .aab upload to Play Console

Day 2-3 (Mar 9-10): Manual Upload (First Time Only - Android)

• Android: Manual upload of .aab (Android App Bundle) to Google Play Console
  • First release on Google Play requires manual upload (cannot use eas submit)
  • Subsequent releases can use automated eas submit
  • Create new release in Play Console
  • Upload .aab artifact
  • Fill in release notes and version info
• iOS: Prepare for automated submission (no manual upload needed)

Day 3-4 (Mar 10-11): Store Submission

# Submit to both stores (iOS automatic, Android follows manual upload)
eas submit --platform all --latest

Day 4-10 (Mar 11-17): Store Review Process

• iOS App Store Review: 24-48 hours typical (can vary 1-5 days)
  • May request additional information
  • Prepare responses for common app review questions
  • Monitor App Store Connect for status updates
• Google Play Review: 3-7 days typical (longer for first submission)
  • May request policy compliance clarifications
  • Have privacy policy and data safety section ready
  • Monitor Play Console for review status
• Buffer time for rejection/resubmission cycles: 1-2 weeks contingency

Day 10-15 (Mar 17-22): Production Launch

• Phased rollout on both platforms (optional)
• Monitor crash reports and user feedback in real-time
• Production API and CDN ready for scale
• Support channels operational and monitored
• Team ready for rapid hotfix deployment

Store Submission Materials

Required Before Submission:

• ✅ App name and tagline
• ✅ App description and features list
• ✅ Screenshot gallery (iOS + Android, multiple resolutions)
• ✅ App icon (1024x1024 PNG)
• ✅ Privacy Policy (published on website)
• ✅ Terms of Service (published on website)
• ✅ Support URL and email
• ✅ EULA if applicable
• ✅ Data Safety form (Google Play)
• ✅ Age rating questionnaire
• ✅ Category classification

Production Infrastructure Setup

• API Performance: Monitor response times, scale database connections if needed
• CDN Configuration: Verify CloudFront is configured for video delivery
• Monitoring & Alerting: Setup Sentry for crash reporting, DataDog for infrastructure
• Rate Limiting: Configure API rate limits to prevent abuse
• Auto-scaling: Verify auto-scaling policies for database and API servers
• Backup & Recovery: Verify backup procedures and disaster recovery plans

Marketing & Launch Announcement

• Marketing materials finalized: Press release, social media graphics, launch video
• Social media content ready: Twitter, Reddit, Mastodon posts prepared
• Press coverage coordination: Reach out to tech/UFO researcher press contacts
• Website updates: Update landing page with “Now Available” badges
• Email notifications: Prepare email to waitlist with download links

Success Criteria for Production Launch

• ✓ All three authentication methods live in production
• ✓ OAuth consent screens approved by Google and Apple
• ✓ Authentication working reliably (99%+ success rate)
• ✓ iOS app approved and live on App Store
• ✓ Android app approved and live on Google Play
• ✓ All features from Sprint 3 live and functional in production
• ✓ 3D globe accessible and performant for all users
• ✓ Heatmaps loading and filtering correctly
• ✓ Gamification system active and rewarding
• ✓ Teams feature enabling user coordination
• ✓ Desktop website live and accessible
• ✓ 3rd party integrations (MUFON, NUFORC, NASA) data flowing
• ✓ EAS build pipeline operational for hotfixes
• ✓ Production API operational and scaling
• ✓ CDN and storage configured and tested
• ✓ Support channels ready and monitored
• ✓ Launch announcement published
• ✓ Monitoring and alerting active
• ✓ First-day performance metrics acceptable
• ✓ User feedback channels established
• ✓ Team ready for rapid hotfix deployment if needed

Target Launch Date

March 15, 2026 or earlier upon approval

Deployment Architecture

Mobile App Deployment

Platform: Expo Application Services (EAS) Stores: Apple App Store + Google Play Store

Build Profiles:

• Development: Local builds for testing and development
• Preview: Internal testing (TestFlight for iOS, Google Play Internal Testing for Android)
• Production: Public release builds

Deployment Flow:

Code Merge → EAS Build → Store Submission → Review → Production
   (Sprint)   (1-2 hours)    (automated)    (1-7 days)  (Launch)

Configuration File (eas.json):

{
  "build": {
    "development": {
      "ios": { "buildType": "simulator" },
      "android": { "buildType": "apk" }
    },
    "preview": {
      "ios": { "buildType": "archive" },
      "android": { "buildType": "aab" }
    },
    "production": {
      "ios": { "buildType": "archive" },
      "android": { "buildType": "aab" }
    }
  },
  "submit": {
    "production": {
      "ios": true,
      "android": false
    }
  }
}

Signing:

• iOS: Managed by EAS (provisioning profiles, certificates)
• Android: Managed by EAS (keystore, signing keys)

Distribution:

• iOS: App Store (TestFlight for beta, v0.9.0)
• Android: Google Play Store (Internal Testing track for beta, v0.9.0)
• Production: Both platforms public release (v1.0.0)

CI/CD Integration:

• GitHub Actions triggers EAS builds on merge to main
• Automated builds for all PRs (development profile)
• Manual submission to stores (production profile)
• Slack notifications on build status
• Crash reports aggregated in Sentry

References:

• Complete EAS Guide
• TestFlight Setup
• EAS Documentation: https://docs.expo.dev/eas/

Production Launch Feature Set Detailed

Core User Workflow (Production)

1. Sign Up: Email, Google OAuth, or Apple OAuth registration
2. Record: Single-button video recording with GPS/sensor capture
3. Edit: Advanced video editing with trim, filters, and effects
4. Sign: Automatic C2PA cryptographic signing
5. Upload: Video stored in cloud with CDN delivery
6. View: See videos in feed, on map, on 3D globe, verified as authentic
7. Verify: Confirm C2PA signatures with external tools
8. Engage: Earn gamification points, join teams, coordinate with others
9. Explore: View heatmaps, advanced search, 3rd party integrations
10. Create: Build user profiles, achievements, public profiles

User Features

Authentication & Profiles

• Email-based user registration and login
• Google OAuth sign-in
• Apple OAuth sign-in
• User profile with avatar, bio, statistics, and achievements
• Secure password reset via email
• Session management and logout
• Privacy controls for public/private videos
• Follower/subscriber system

Video Recording & Capture

• Single-button video recording interface
• Live camera preview with timer
• GPS location capture during recording
• Device sensor data collection (accelerometer, timestamp)
• Camera and microphone permission handling
• Video metadata capture (title, description, category)

Video Editing

• Post-recording video trimming
• Filters and visual effects
• Metadata editing after recording
• Preview before upload

C2PA Content Signing

• 100% of videos cryptographically signed with C2PA
• GPS coordinates embedded in C2PA manifest
• Device sensor data included in manifest
• Timestamp and device identification
• External verification capability
• Tamper detection

Video Upload & Storage

• Cloud storage with CDN delivery
• Upload progress tracking
• Automatic retry on connection loss
• Compression for optimization
• Background upload capability

Video Discovery

• Chronological video feed with endless scroll
• 3D interactive globe view with phenomena visualization
• Map view with H3 hexagonal clustering
• Heatmap layers by category (UAP, Cryptid, Paranormal, etc.)
• Location-based video search
• Category filtering
• Advanced search and filtering across all attributes
• Keyword search
• Event detail view with full context visualization
• Related videos recommendations

Gamification & Social

• Points system for recording, uploading, and verification
• Badges and achievements
• Leaderboards for top contributors
• Multi-user phenomenon detection rewards for coordinated captures
• Team formation for organized investigations
• Team coordination features for group missions

User Profiles

• Public user profiles
• User upload statistics
• Achievement and badge display
• Subscriber/follower system
• User discovery and recommendations
• Activity history and timeline

User Experience

• Comprehensive onboarding with feature tutorials
• In-app help and support
• FAQ and documentation
• Guided first-time user experience

Desktop Website

• Web-based viewing of all videos
• User account management
• Advanced analytics dashboard
• Team management interface
• Administration panel
• Search and filtering

3rd Party Integrations

• MUFON (Mutual UFO Network) data integration
• NUFORC (National UFO Reporting Center) data import
• NASA space objects and satellite data feeds
• Data synchronization and updates

Infrastructure & Operations

Backend

• Hasura GraphQL API
• PostgreSQL database with PostGIS
• JWT-based authentication with OAuth integration
• Email service for notifications
• C2PA manifest generation and validation
• Video processing pipeline
• Gamification engine
• Team management system
• 3rd party API integrators

Frontend Mobile

• React Native cross-platform app
• Responsive design for iOS and Android
• TypeScript for type safety
• Apollo Client for GraphQL
• Video capture with native modules
• 3D globe visualization library
• Advanced video editing SDK
• C2PA signing integration

Frontend Web

• React/Next.js web application
• Responsive design for desktop/tablet
• User dashboard and analytics
• Team management interface
• Administration tools
• TypeScript for type safety

Cloud Infrastructure

• AWS S3 for video storage
• CloudFront CDN for video delivery (standard S3 delivery method)
• RDS PostgreSQL database
• Monitoring and alerting
• Rate limiting and DDoS protection
• Automatic scaling
• 3D tile servers for globe visualization

C2PA Implementation Strategy

Why C2PA is Critical for Production

Core Value Proposition: PhenomApp is designed to provide undebunkable evidence of phenomena through cryptographic content authentication. C2PA signing is the fundamental differentiator.

Market Position: This makes PhenomApp the first C2PA-enabled phenomenon documentation app, positioning it as the gold standard for authentic phenomenon evidence.

Production Validation: Users will trust the complete workflow:

1. Record phenomenon on camera
2. Device cryptographically signs video with GPS and sensor metadata
3. Signature embedded in video file
4. Users can verify authenticity using c2pa-tool or Verify.org
5. Impossible to claim video is fake if C2PA signature is valid

C2PA Implementation Details

• Technology: Use c2pa-rs Rust library with React Native bridge for efficient signing
• Key Management: Generated per-device, stored securely in device keychain
• Performance Target: Complete signing within 30 seconds of video capture
• Metadata: GPS coordinates, device model, timestamp, IMU data embedded in manifest
• Verification: External tools can verify without contacting servers
• Compliance: Meets C2PA standard specification v1.3+

Risk Mitigation

High-Risk Items for Production Timeline

Success Criteria by Phase

Phase 0 Success (End of January 2026)

Administrative:

• ✅ D-U-N-S number obtained
• ✅ Apple Developer Program enrollment approved
• ✅ Apple Team ID configured
• ✅ Google Play Developer Account active
• ✅ Service Account with Release Manager permissions created
• ✅ All credentials stored securely and team has access
• ✅ EAS CLI can authenticate with both platforms

Pre-Beta Success (End of Sprint 3 - March 1)

Development:

• 100% of Sprint 1-3 issues completed
• Test coverage: 60%+ for all components
• CI/CD pipeline functional for automated tests
• All PRs reviewed before merge
• EAS build pipeline operational and tested

Product Readiness:

• Core user workflow: Record → Upload → Verify fully functional
• 100% of videos C2PA signed and verifiable
• C2PA signatures include GPS and sensor metadata
• 3D globe rendering and performing well
• Heatmaps functional and filtering correctly
• Gamification system awarding points
• Team formation and coordination working
• Desktop website deployed and accessible
• 3rd party integrations active and data flowing
• App launches without crashes on test devices
• Performance acceptable (API < 500ms, video upload < 2 min for 50MB, signing < 30 sec, 3D globe 60 FPS)
• Ready for beta testing

Beta Testing Success (March 1-7)

Metrics:

• 20-50 beta testers active
• Email, Google, and Apple authentication all working
• Users can sign up with any of the three methods
• OAuth token refresh working correctly
• 100% of beta testers can authenticate successfully
• 100% of beta testers successfully experience all major features
• 100% of core workflow completion rate
• 100% of videos C2PA signed
• 95%+ of signatures verifiable with external tools
• 3D globe rendering for 100% of users
• Heatmaps displaying correctly with category filters
• Gamification points awarding correctly
• Teams forming and coordinating successfully
• Desktop website accessible for testing
• 3rd party data displaying correctly
• 90%+ upload success rate
• Crash rate < 5%
• Performance metrics acceptable
• Clear validation that all features work as designed
• EAS build distribution working smoothly

Deliverables:

• Critical bug fixes deployed
• Production readiness confirmed
• Store submission materials prepared
• Team ready for launch

Production Launch Success (March 8-15)

Deployment:

• All three authentication methods live in production
• OAuth consent screens approved by Google and Apple
• Authentication working reliably (99%+ success rate)
• iOS app approved and live on App Store
• Android app approved and live on Google Play
• All features from Sprint 3 live and functional
• Production infrastructure operational
• All systems monitoring and alerting active
• EAS build pipeline operational for hotfixes

Operational:

• Support channels operational
• First users downloading and testing
• Performance metrics within targets
• No critical production issues
• Team ready for rapid response
• Community engagement beginning

Version Numbering

v0.1.0 (Alpha)       - Sprint 1: Foundation + EAS Pipeline
v0.2.0 (Alpha)       - Sprint 2: Integration + OAuth
v0.3.0 (Beta)        - Sprint 3: All Features + C2PA Implementation
v0.9.0 (Beta)        - Beta Testing (Mar 1-7)
v1.0.0 (Production)  - Production Launch (Mar 15, 2026)
v1.0.1+              - Production hotfixes and patches
v1.1.0+              - Future feature releases (AR modes, etc.)

Technology Stack

Backend

• Language: TypeScript/Node.js
• GraphQL: Hasura GraphQL Engine v2.x
• Database: PostgreSQL 14+ with PostGIS
• Authentication: JWT + OAuth (Google and Apple)
• File Storage: AWS S3 with CloudFront CDN
• C2PA Backend: C2PA manifest creation, validation APIs
• 3D Data: Tile server for globe visualization
• Testing: Jest
• Linting: ESLint + Prettier
• CI/CD: GitHub Actions + EAS CLI
• Containerization: Docker
• Mobile Deployment: Expo Application Services (EAS)

Frontend Mobile

• Framework: React Native
• Language: TypeScript
• State Management: Redux/Context API
• API Client: Apollo Client (GraphQL)
• Video Capture: react-native-vision-camera
• Video Editing: react-native-ffmpeg
• C2PA Signing: c2pa-rs via React Native bridge
• 3D Globe: Three.js or Cesium.js
• Mapping: Mapbox GL or similar
• Testing: Jest + React Native Testing Library
• Build & Deploy: Expo + EAS

Frontend Web

• Framework: React or Next.js
• Language: TypeScript
• State Management: Redux/Context API
• API Client: Apollo Client (GraphQL)
• 3D Visualization: Three.js or Cesium.js
• Mapping: Mapbox GL
• Testing: Jest + React Testing Library

External Services

• Cloud Storage: AWS S3 with CloudFront CDN
• Crash Reporting: Firebase Crashlytics or Sentry
• Analytics: Firebase Analytics
• Geocoding: OpenStreetMap (free tier)
• C2PA Verification: Verify.org API for external verification
• OAuth Providers: Google OAuth 2.0, Apple Sign In
• 3D Tiles: OpenTopo or similar
• 3rd Party APIs: MUFON API, NUFORC API, NASA APIs
• Mobile Deployment: Expo Application Services (EAS)
• Store Distribution: Apple App Store, Google Play Store

Assumptions & Constraints

Assumptions

1. Development team with parallel work streams available
2. No major architecture changes required
3. Beta testers available and willing to participate
4. Cloud infrastructure available (AWS or similar)
5. No external dependencies blocking C2PA implementation
6. c2pa-rs library stable and React Native compatible
7. Google OAuth and Apple Sign In available and approved
8. App store approval within 3-5 business days
9. 3rd party APIs (MUFON, NUFORC, NASA) accessible
10. Desktop web framework proven and stable
11. Phase 0 administrative setup completes by January 20, 2026
12. Apple Developer Account enrollment approved by Jan 31, 2026
13. EAS build pipeline configured and operational by Feb 2, 2026

Constraints

1. HARD DEADLINE: Must launch production by March 15, 2026
2. C2PA MANDATORY: Cryptographic signing required on 100% of videos
3. OAUTH MANDATORY: Email + Google + Apple authentication required
4. FULL FEATURE SET: All features (except AR) required in production
5. PARALLEL DEVELOPMENT: Sprint 3 requires parallel development streams
6. TESTING REQUIRED: Real device testing before launch
7. C2PA COMPLEXITY: Significant effort required in Sprint 3
8. EXTENSIVE SCOPE: Sprint 3 has extensive feature requirements
9. PHASE 0 BLOCKING: Cannot start Sprint 1 without Phase 0 completion
10. EAS REQUIRED: Must use Expo Application Services for iOS and Android deployment

Team Assignments & Responsibilities

Core Team

DevOps/Release Manager: @goldeneagle3636 (Aaron)

• Phase 0: Apple/Google account setup (Dec 2025 - Jan 2026) - CRITICAL
• Phase 0: Obtain D-U-N-S number, complete Apple enrollment, create Google Play account
• Sprint 1: Hasura GraphQL setup, EAS build profiles configuration (#33), EAS secrets management (#34)
• Sprint 2: Core API endpoints, email auth + OAuth integration, sensor data, CI/CD with EAS
• Sprint 3: Upload pipeline, C2PA metadata, AWS S3 + CloudFront, 3rd party integrations
• Production Week: Build production artifacts, manage store submissions, monitor deployments

Frontend Lead: @jonathan.hart (Jonathan)

• Sprint 1: Coordinate frontend-backend alignment
• Sprint 2: API client, auth UI (email + OAuth)
• Sprint 3: Video recording, C2PA signing, video editing

Sprint 3 Expanded Team (TBD Assignments)

Frontend Visualization Developer (TBD)

• 3D globe implementation and optimization
• Heatmap visualization
• Advanced map features
• Event detail views

Frontend Social/Engagement Developer (TBD)

• Gamification system implementation
• User profiles and achievements
• Team formation and coordination
• Leaderboards

Desktop Web Developer (TBD)

• Desktop website development
• User dashboard
• Administration panel
• Analytics and reporting

Video Processing Developer (TBD)

• Advanced video editing implementation
• Video effects and filters
• Compression optimization
• Video pipeline

Shared Responsibilities

• Phase 0 Blocking: Cannot proceed until complete
• Beta Coordination: Daily check-ins with beta testers, all feature validation
• Code Review: All PRs reviewed before merge
• Testing: All teams contribute to test coverage
• Monitoring: Track crashes, errors, C2PA success, OAuth success, feature usage
• EAS Build Pipeline: All teams responsible for maintaining build success rates

Implementation Workflow

GitHub Integration

All issues tracked at: https://github.com/Phenom-earth/PhenomApp/issues

Issue Labeling:

• phase-0, sprint-1, sprint-2, sprint-3, beta, production - Phase assignment
• critical, high, medium, low - Priority
• backend, frontend, devops, web - Component
• blocking - Critical path items
• c2pa - Content authenticity implementation
• oauth - Authentication implementation
• production-launch - Pre-launch items
• visualization - 3D globe, heatmaps, maps
• gamification - Points, badges, leaderboards
• teams - Team coordination features
• eas - Expo Application Services deployment

Communication Schedule (Phase 0 - Admin Setup)

• Weekly (30 min): Phase 0 status check on progress with Apple/Google accounts
• As needed: Escalation of enrollment delays

Communication Schedule (Pre-Production)

• Daily (15 min): Standup via Slack/Teams (critical updates across all teams)
• Wednesday (15 min): Mid-week sync across all streams
• Friday (30 min): Sprint review & planning

Communication Schedule (Beta + Production)

• Daily (30 min): Team sync (rapid iteration, all teams)
• As needed: Hotfix deployment coordination
• Friday (30 min): Weekly status update

Documentation Links

• PRD: Product Requirements Document
• Architecture: Technical Architecture
• Backend Integration: Backend Integration Guide
• Features: Feature Details
• C2PA Integration: C2PA & Metadata Signing
• EAS Deployment: EAS Deployment Guide
• TestFlight Guide: TestFlight Beta Distribution
• External Resources: Third-party APIs & Services
• GitHub Issues: View all issues
• Project Board: View roadmap board

Next Steps

Immediate Actions (This Week - January 21-24)

Phase 0 - Critical Path (First Priority):

1. D-U-N-S Number Application: @goldeneagle3636 applies at https://www.dnb.com/duns-number.html
2. Apple Enrollment Prep: Gather legal documents for organization
3. Google Play Setup: Create account and verify payment method ($25 one-time)
4. Credential Management: Prepare 1Password vault for secure storage
5. Team Communication: Brief team on Phase 0 importance and blocking nature

Concurrent Activities:

1. Team Expansion Planning: Identify and begin recruiting 6-8 additional developers for Sprint 3
2. Team Kickoff: Review this roadmap with core and expanded team, emphasize all-features sprint
3. C2PA Spike: Begin evaluation of c2pa-rs library and React Native integration
4. OAuth Spike: Begin research on Google OAuth and Apple Sign In implementation
5. 3D Globe Research: Begin exploration of Three.js/Cesium.js for visualization
6. Gamification Research: Identify proven gamification system libraries
7. Desktop Framework Research: Evaluate Next.js/React for desktop website
8. 3rd Party API Research: Begin integration planning for MUFON, NUFORC, NASA
9. EAS Research: Review EAS documentation and authentication setup
10. Environment Setup: Confirm development environment requirements
11. GitHub Setup: Create milestones for Phase 0, Sprint 1, 2, 3, Beta, Production
12. Issue Assignment: Create all Sprint 3 issues (#27-40) and assign to teams
13. Beta Recruitment: Begin identifying potential beta testers

Phase 0 Completion (January 20-31, 2026)

1. D-U-N-S Approval: Confirm number received from Dun & Bradstreet
2. Apple Enrollment Status: Check Apple Developer Program enrollment progress
3. Google Play Account: Verify account is active and functional
4. Credentials Secured: All credentials in 1Password with team access
5. EAS Readiness: Confirm both platforms ready for EAS integration

Sprint 1 Preparation (Jan 27-31)

1. Week 1 Start: Sprint 1 kickoff meeting (Feb 2 - this assumes Phase 0 complete)
2. Issue #16: Begin Hasura + PostgreSQL setup
3. Issue #17: Configure ESLint and Jest
4. Issue #33: Configure EAS build profiles (eas.json) - MUST COMPLETE
5. Issue #34: Setup EAS secrets management - MUST COMPLETE
6. Proof-of-Concepts: Complete POCs for C2PA, OAuth, 3D globe, gamification
7. Daily Standups: 15 min sync across all teams
8. Environment Preparation: Ensure all developers have working environments

First Sprint Deliverable Target

• Week 1-2: Hasura GraphQL API operational
• Week 2: Basic schema for users, videos, locations, sensor_data
• Week 2: EAS build profiles working for all three environments (Development, Preview, Production)
• Week 2: EAS secrets management operational and tested
• Week 2: C2PA, OAuth, 3D globe, gamification proof-of-concepts complete
• Week 2: CI/CD pipeline for tests with EAS integration
• End of Sprint 1 (Feb 2): Full foundation ready for Sprint 2 + Sprint 3 planning

Production Launch Preparation

• Early Feb: Begin app store submission preparation
• Feb 10: Sprint 3 team fully expanded and ready
• Week of Feb 17: Sprint 3 massive parallel development begins
• Mar 1: Beta testing begins with all features
• Mar 8: Build production artifacts and prepare store submissions
• Mar 9-10: Manual Android upload (first release requires manual .aab upload)
• Mar 10-11: Submit both apps to stores
• Mar 15: Target production launch date

Production Readiness & Administrative Features (Post-Launch Priority)

The following features are essential for production operations, compliance, and platform management. These should be implemented immediately after the March 15, 2026 launch or in parallel during Sprint 3 if additional development resources are available.

Issue #36: Audit Logging System (HIGH Priority)

Status: Todo Effort: L (Large - 1-2 weeks) Owner: @goldeneagle3636

Comprehensive audit logging system to track all user actions, administrative actions, and system events for compliance, security, and debugging.

Key Features:

• User activity logging (posts, uploads, edits, deletes)
• Authentication events (login, logout, failed attempts)
• Administrative actions (moderation, bans, content removal)
• System events (API usage, security events)
• 90-day retention for user logs, 7-year retention for legal/compliance

Why Critical:

• Required for GDPR/CCPA compliance
• Essential for debugging production issues
• Legal requirement for ToS enforcement documentation
• Security incident investigation

Dependencies: #16 (Hasura), #21 (API), #23 (Auth)

Issue #37: Content Moderation System (HIGH Priority)

Status: Todo Effort: XL (Extra Large - 2-3 weeks) Owner: @goldeneagle3636

Content moderation system to enforce Terms of Service, detect policy violations, and enable administrative actions for user-generated content.

Key Features:

• Automated content screening (profanity, NSFW, spam detection)
• Manual moderation queue for admin review
• User reporting system
• Moderation actions (approve, reject, remove, warn, ban)
• Integration with audit logging (#36)

Why Critical:

• Legal requirement for user-generated content platforms
• Protects platform from illegal/harmful content
• Required for app store compliance
• Enables ToS enforcement

Dependencies: #16 (Hasura), #21 (API), #28 (Upload), #36 (Audit)

Issue #38: Customer Support Ticketing System (MEDIUM Priority)

Status: Todo Effort: L (Large - 1-2 weeks) Owner: @goldeneagle3636

Customer support system to handle user inquiries, bug reports, feature requests, and account issues.

Key Features:

• Support ticket creation and management
• User-facing ticket portal
• Admin dashboard for support team
• SLA tracking and automated alerts
• Email notifications
• Canned responses for common issues

Why Important:

• Essential for handling user issues at scale
• Improves user satisfaction and retention
• Tracks common problems for product improvement
• Required for professional platform operations

Dependencies: #16 (Hasura), #21 (API), #23 (Auth), #36 (Audit)

Issue #39: Incident Response System (HIGH Priority)

Status: Todo Effort: XL (Extra Large - 2-3 weeks) Owner: @goldeneagle3636

Incident response system to handle security incidents, abuse reports, ToS violations, and emergency situations.

Key Features:

• Incident management workflow (detection, triage, investigation, response, resolution)
• Automated incident detection (brute force, API abuse, content violations)
• Incident actions (IP blocking, account suspension, content removal)
• Post-incident review and documentation
• Integration with PagerDuty/OpsGenie for critical alerts

Why Critical:

• Required for handling security incidents
• Legal requirement for abuse response
• Protects platform from coordinated attacks
• Essential for production operations

Dependencies: #16 (Hasura), #21 (API), #36 (Audit), #37 (Moderation)

Issue #40: Admin Dashboard & Tools (HIGH Priority)

Status: Todo Effort: XL (Extra Large - 3-4 weeks) Owner: @jonathan.hart (Frontend) + @goldeneagle3636 (Backend)

Comprehensive admin dashboard for managing users, content, moderation, support, and platform operations.

Key Features:

• Platform overview and real-time metrics
• User management (search, view, suspend, ban)
• Content management (browse, remove, feature)
• Moderation dashboard (queue, reports, actions)
• Support dashboard (tickets, SLA tracking)
• Incident dashboard (active incidents, history)
• Audit log viewer
• Analytics and reporting

Why Critical:

• Required to use features from #36, #37, #38, #39
• Essential for platform administration
• Enables efficient operations at scale
• Professional interface for support and moderation teams

Dependencies: #36, #37, #38, #39 (all admin features)

Deployment: admin.thephenom.app (separate subdomain with OAuth + 2FA)

Implementation Strategy

Option 1: Parallel Development During Sprint 3

• If 2-3 additional developers available
• Implement #36 (Audit) and #40 (Admin Dashboard) in parallel with Sprint 3
• Deploy alongside March 15 launch
• Advantage: Fully operational admin tools from day 1

Option 2: Post-Launch Sprint 4 (Recommended)

• Focus all resources on Sprint 3 features for launch
• Implement admin features in 2-week sprint immediately after launch (Mar 16-29)
• Advantage: All hands on deck for successful launch
• Risk: 2 weeks of production without full admin tooling

Option 3: Phased Rollout

• Implement #36 (Audit Logging) during Sprint 3 (critical for compliance)
• Deploy #37, #38, #39, #40 in post-launch sprint
• Advantage: Audit logs from day 1, other admin tools follow
• Recommended approach for balanced risk/resource management

Minimum Viable Admin (Launch Day Requirements)

Must Have on March 15:

• #36 (Audit Logging) - For compliance and debugging
• Basic user management (view users, ban users)
• Basic content removal capability
• Emergency incident response procedures documented

Can Deploy Post-Launch:

• #37 (Full moderation system)
• #38 (Support ticketing)
• #39 (Incident management system)
• #40 (Full admin dashboard)

Resource Requirements

Backend/DevOps: 3-4 weeks of work across 5 issues Frontend: 3-4 weeks for admin dashboard (#40) Total Team Weeks: 6-8 weeks if done sequentially, 3-4 weeks if parallelized

Recommendation: Allocate 1-2 backend developers and 1 frontend developer for post-launch Sprint 4 (Mar 16-29) to deliver all 5 features.

Questions & Support

For specific feature questions, see GitHub issues. For timeline or resource questions, contact:

• @goldeneagle3636 (Backend/DevOps/Release): Backend architecture, C2PA implementation, OAuth integration, infrastructure, 3rd party integrations, Phase 0 administration, EAS deployment, store submissions
• @jonathan.hart (Frontend Lead): Frontend architecture, video capture, C2PA signing integration, OAuth UI
• @matt (Product Manager): Overall roadmap, timeline, team scaling, production launch coordination

Phase 0 Status: ✅ COMPLETED

Phase 0 administrative setup has been completed successfully.

All blocking tasks for Sprint 1 development are now complete:

• ✅ Apple Team ID obtained - EAS build profiles can now be configured
• ✅ Google Play service account created - EAS secrets can now be generated
• ✅ Both platforms ready for Sprint 1 EAS integration (Jan 20, 2026)
• ✅ No delays to Sprint 1 schedule
• ✅ iOS and Android deployment ready for March 15 production launch

Sprint 1 can begin on schedule (January 20, 2026) without any Phase 0 blockers.

Status: Q1 2026 Full-Feature Production Launch with EAS Deployment - Ready for Implementation Created: January 21, 2026 Last Updated: January 21, 2026 Target Production Launch: March 15, 2026 Key Differentiator: First C2PA-enabled phenomenon documentation app with 3D globe visualization, heatmaps, gamification, teams, desktop website, and 3rd party integrations with cryptographic content authentication and multi-method user authentication, deployed via Expo Application Services (EAS) Scope: ALL features (except AR modes) delivered in 8 weeks through parallel development Deployment: iOS App Store + Google Play Store via EAS build and submission pipeline