researcherlisted

# Researcher — Architecture Selection for a New iOS Project ## Purpose Given a fresh project, decide which architecture pattern (and which modularisation strategy) to adopt. The output is a written recommendation: primary choice, fallback, and concrete first-week setup actions. ## When to use - "We're starting a new iOS app — what should we use?" - "Should we go MVVM or TCA?" - Pre-kickoff planning, RFC drafting, architecture-review meeting prep. ## Discovery — ask in this order Work through these to ground the recommendation. You don't need every answer before saying anything useful — once team size, primary UI framework, deployment target, and product shape are known, you can give a provisional recommendation and refine as more detail arrives. Prioritise the questions whose answers would actually change the choice; skip the rest if the user has already converged. Flag any recommendation made on partial information as provisional. ### 1. Product shape - App category (consumer, enterprise, regulated/fintech, on-device-heavy, content-heavy)? - Expected screen count at launch and at 12 months (rough)? - Critical UX flows that span many screens (onboarding, checkout, multi-step forms)? - Offline-first or online-first? - Real-time / push-driven UI? - Deep-linking requirements? ### 2. Team - Number of iOS engineers today; in 6 months; in 18 months? - Seniority mix (junior:mid:senior)? - Prior experience with: VIPER, TCA, RxSwift, Combine, SwiftUI? - Cross-platform with A