Senior iOS/SwiftUI engineer — one-time architecture review, written findings only (~4–6 hrs)

I'm a solo founder (senior product designer, non-engineer) building a native iOS app in SwiftUI with AI coding tools. The scaffold is built and compiles: feature-first folder structure, SwiftData persistence layer behind repositories, a design-system token layer, and one working vertical slice. Automated quality gates (SwiftLint, SwiftFormat, a custom architecture checker) are live and verified. I'm hiring for a **one-time written review of the foundation** before feature development scales on top of it. This is a review engagement, not a build — you will not write code. **What you'll review:** - SwiftUI and Swift idioms: state management, view decomposition, retain cycles, concurrency - Repository/persistence boundary: is it sound, and is SwiftData fully contained (nothing leaking into Views)? - A spaced-repetition scheduler that must be a pure function (no hidden `Date()` calls; timestamps injected) - Module boundaries and the dependency rule — and whether the automated architecture checker would actually catch real violations - An API-provider seam and its cache-key design - Anything else a non-engineer founder building with an AI agent would plausibly miss at the foundation level **Deliverable — written findings in this format:** For each finding: severity (blocker / should-fix / nice-to-have), file and line reference, and a plain-English explanation of *what breaks or gets expensive later if this isn't fixed*. That last part is the core of what I'm paying for — I need to understand the consequences, not just the recommendation. A short summary verdict on whether the foundation is sound to build on closes it out. **Process:** 1. **Paid trial (fixed price, ~30 min):** I'll share one file — the pure-Swift scheduler plus its spec — and you review just that. If the feedback is specific and useful, we proceed to the full review. 2. **Full review (fixed price):** Private GitHub repo access (read-only), a written review brief with the checklist above, and a codebase small enough to hold in your head — this is an early scaffold, not a legacy monolith. Estimate 4–6 hours. 3. Findings delivered as a written document. I may follow up with clarifying questions on individual findings; brief async answers included in scope. **Requirements:** - Shipped SwiftUI apps on the App Store (link them — under your name or verifiable client work) - Hands-on SwiftData experience (or Core Data with a clear grasp of SwiftData's differences) - Strong written English — the deliverable is a document, and clarity is the product **To apply, answer these two questions** (applications that skip them will be declined): 1. Link one shipped SwiftUI app you worked on and name one architecture decision in it you'd make differently today, and why. 2. In 2–3 sentences: what's a failure mode you'd specifically look for in a codebase written primarily by an AI coding agent? Timeline: I'd like the trial done within 3 days of hiring and the full review within a week after.