Back to corpus
architecturetechnical paper candidatescore 52

Expo Migration Overview

**Document ID:** EXPO-OVERVIEW-001 **Version:** 1.0.0 **Created:** 2026-01-04 **Status:** ACTIVE **Parent Document:** README.md

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Document ID:** EXPO-OVERVIEW-001 **Version:** 1.0.0 **Created:** 2026-01-04 **Status:** ACTIVE **Parent Document:** README.md This document provides a high-level overview of the migration strategy for converting the **Milk Men** iOS application from Swift/SwiftUI to Expo (React Native). **Primary Goal:** Achieve complete feature parity with the Swift iOS application while establishing a foundation for future Android and Web deployment. **Secondary Goals:** - Leverage JavaScript/TypeScript developer ecosystem - Maintain or exceed Swift app performance and UX - Preserve all existing Supabase backend infrastructure - Enable parallel development without disrupting production ### 1. Platform Expansion Readiness - **Current State:** iOS-only (Swift/SwiftUI) - **Future State:** iOS (initial), Android, Web (architecture-ready) - **Benefit:** Single codebase for multiple platforms reduces long-term maintenance

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.