Back to corpus
architecturetechnical paper candidatescore 56

BrewsWithBeats - Three-App Architecture Implementation Plan

This document outlines the comprehensive plan to restructure BrewsWithBeats from a unified app into three separate components:

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This document outlines the comprehensive plan to restructure BrewsWithBeats from a unified app into three separate components: 1. **BWBCore** - Shared Swift Package (models, services, networking, theme) 2. **BWB-Customer** - Customer-facing iPhone/iPad app (ordering, rewards, dance) 3. **BWB-POS** - Staff iPad app (order queue, inventory, analytics, admin) | Current Location | New Location in BWBCore | Notes | |-----------------|------------------------|-------| | `Models/User.swift` | `Models/User.swift` | Shared user model | | `Models/Order.swift` | `Models/Order.swift` | Order model with all states | | `Models/MenuItem.swift` | `Models/MenuItem.swift` | Menu item model | | `Models/Customization.swift` | `Models/Customization.swift` | Drink customization | | `Models/Event.swift` | `Models/Event.swift` | Events model | | `Services/Auth/AuthService.swift` | `Services/Auth/AuthService.swift` | Authentication service | | `Services/Supabase/SupabaseManager.swift` | `Services/Supabase/SupabaseManager.swift` | Supabase client | | `Services/Repository/*.swift` | `Services/Repository/*.swift` | All repositories | | `Services/CartService.swift` | `Services/CartService.swift` | Cart management | | `Services/RewardsService.swift` | `Services/RewardsService.swift` | Rewards system | | `Services/PushNotificationService.swift` | `Services/PushNotificationService.swift` | Push notifications | | `Utilities/Logger.swift` | `Utilities/Logger.swift` | Logging utilities | | `Utilities/Haptics.swift` | `Utilities/Haptics.swift` | Haptic feedback | | `Utilities/Config.swift` | `Utilities/Config.swift` | Configuration | | `Components/BWBDesignTokens.swift` | `Theme/BWBDesignTokens.swift` | Design tokens | | `Components/BWBComponents.swift` | `Components/BWBComponents.swift` | Shared components | | `Voice/*.swift` | `Voice/*.swift` | Voice ordering services | | Feature | Description | Priority | |---------|-------------|----------| | Menu Browsing | Browse coffee menu with categories | P0 | | Voice Ordering | Order via voice commands | P0 | | Cart Management | Add/remove/modify items | P0 | | 4-Step Checkout | Review → Payment → Pickup → Confirm | P0 | | Order Tracking | Real-time order status | P0 | | Rewards System | Points, tiers, redemption | P1 | | Dance Challenges | Earn rewards through dancing | P1 | | Events Calendar | View upcoming events | P2 | | Profile Management | User settings, preferences | P1 | | HealthKit Integration | Sync dance data | P2 | | Push Notifications | Order updates, promotions | P1 | | Feature | Description | Priority | |---------|-------------|----------| | Order Queue | Real-time order management | P0 | | Queue Stats Dashboard | Live metrics display | P0 | | Dual-Cart Checkout | Walk-in customer orders | P0 | | Staff Authentication | Rol

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.