How We Built FeedingUp: iOS App From Idea to App Store in 14 Weeks

This is a straightforward account of how we scoped, designed, and shipped FeedingUp — a native iOS app that helps parents track their child's first foods, allergens, and feeding schedule. From first call to live on the App Store: 14 weeks. No fluff, no agency storytelling. Just the actual sequence.

The Problem We Were Solving

When parents start introducing solid foods to babies (typically around 4–6 months), the process is surprisingly stressful. Which foods have been tried? Did any cause a reaction? Is the schedule on track? Most parents either keep a paper notebook or use a generic notes app — neither of which is built for the specific patterns of baby feeding.

The core product insight: parents don't want a complex tracker. They want something they can update with one hand, at 3am, while holding a baby. The setup flow had to take seconds, not minutes. That shaped every design decision we made.

Discovery: Scoping the Real Product

Week one was a structured discovery. We don't start with wireframes — we start with questions. What does the user do in the first 60 seconds? What's the one thing they must not lose? Where does the current solution (paper, notes app) break down?

By the end of week two we had a written document with:

• Three user flows (add food, view history, check allergens)
• A fixed feature scope — what's in v1, what's explicitly out
• A build sequence: which screen ships first and why
• A budget range and timeline with contingency built in

The Build Sequence

The Technical Stack

• Language: Swift 5.9
• UI: SwiftUI with custom components
• State management: Combine + ObservableObject
• Backend: Firebase Firestore (real-time sync), Firebase Auth (Sign in with Apple)
• Analytics: Firebase Analytics
• CI/CD: Fastlane → TestFlight → App Store Connect

What Made the Onboarding Work

The 92% onboarding completion rate isn't an accident. Most apps lose users in setup because they ask too much, too early. Our onboarding flow is three screens:

1. Baby's name and date of birth (pre-fills age and milestones automatically)
2. One tap to set the feeding start date
3. First food logged — immediately useful, no empty state

No account required before seeing value. No long permission dialogs. The user is in the app and tracking within 90 seconds. That's the benchmark we designed to.

What We Learned

A few things worth writing down from this specific engagement:

• Firebase Auth with Sign in with Apple adds real friction to the initial Firebase setup — budget an extra 2–3 days for the Apple entitlements and capability configuration.
• SwiftUI animations on older devices (iPhone SE 2nd gen) need explicit optimization — don't assume smooth means smooth everywhere until you test on the actual device.
• App Store Review flagged our food database as requiring a medical/health disclaimer even though it's not a clinical app. Worth checking the App Store guidelines for your category early, not after submission.
• The friday demo cadence kept the product focused. When you show something every week, it's immediately obvious what's confusing or incomplete. It's the best substitute for a dedicated QA phase.

The Result

FeedingUp is live on the App Store. 4.8★ average rating. Parents in the US, UK, and Ukraine use it daily. We shipped it in 14 weeks, on the timeline we quoted in week two, with the feature set we locked in discovery.

That's the goal every time: a real product in users' hands, on a date that was predictable from week one.