iOS Reality Check

Ideal fit

• Non-technical founder about to commit real money to building an iOS app and wanting an outside read before they do.
• Technical founder without iOS experience (web, backend, ML, anything not Apple platform) planning their first iOS launch.
• Early-stage team at the "should we really build this?" moment, before a design or engineering hire.
• Indie developer with a big idea that might collide with Apple platform constraints they don't know exist yet.
• Investor or partner doing a quick technical gut-check before backing a founder's iOS play.

Scope

Seven angles, each pulled through a go / no-go / pivot lens:

• 1. Technical feasibility: what iOS actually can and can't do once you try. Background execution limits, Bluetooth scanning intervals, location-in-background, push deliverability, keyboard extension sandboxing, share sheet and widget constraints. Most concepts have at least one hidden platform ceiling. I name them before you hire for them.
• 2. App Store publishability: will Apple even let you ship this? Categories that are effectively closed to new entrants (new dating apps without major differentiation, most crypto and trading apps, generic VPNs, MDM-based parental control), categories with hard compliance bars (medical and health with diagnostic claims, gambling, kids apps under COPPA, user-generated-content apps without real moderation), and business models that collide with guidelines 3.1 (commerce), 4.2 (minimum functionality), and 5.1 (privacy). I flag the dealbreakers before they cost you three app review rejections.
• 3. Complexity and timeline sizing: realistic MVP and v1 effort in weeks and people. First-time founders consistently underestimate by 3 to 10 times. The number will not be what you hoped, but it will be defensible.
• 4. Build vs buy vs no-code: what's genuinely custom versus a Firebase, Supabase, RevenueCat, or Superwall-shaped line of code. Where no-code (Glide, FlutterFlow) will actually get you to a testable MVP, and where it will trap you. What shouldn't exist at all.
• 5. MVP definition: the smallest possible product that proves your riskiest assumption. Not a feature list. A single hypothesis and the minimum surface area that tests it honestly.
• 6. Go-to-market sanity check: ASO ceiling for your category, realistic App Store pricing and subscription psychology, paid acquisition economics (ATT prompt conversion, target CPI, LTV floor), distribution and wedge channels. Does the math close, even optimistically?
• 7. Founder gap-finding: what a first-time iOS founder doesn't yet know to ask. Privacy manifest and required reasons API, ATT prompt design, app review operations, StoreKit 2 subscription posture, localisation cost curve, in-app purchase tax handling. The unknown unknowns list.

Deliverables

• Written concept audit with a go / no-go / pivot call per angle, plus an overall recommendation.
• MVP scope definition: the smallest build that answers your riskiest open question, with a concrete feature list and a rough week estimate.
• Risk register: technical risks, Apple platform risks, and GTM risks, each with a likelihood, an impact, and a mitigation.
• Report calibrated to your primary reader: deep-technical, cross-technical, or executive. Most reports for founders land at executive level; technical co-founders get cross-technical.
• 60-minute walkthrough call to answer questions and pressure-test the recommendation.

Timeline

3 to 5 days from kickoff. One-shot engagement, not a retainer, not an ongoing advisory relationship. The goal is to give you enough truth to decide what to do next, then get out of the way.