Ongoing Operations

Your app is live. Now the work shifts from building to monitoring, updating, and growing. This doc covers the operational tooling you'll want in place from day one.

Crash reporting

Crashes without reporting are invisible. Set up at least one of these:

• Xcode Organizer (free, built in): After launch, Xcode Organizer → Crashes shows symbolicated crash reports from users who have opted into sharing with developers. No SDK required.
• Firebase Crashlytics (free tier): More detailed, real-time, includes breadcrumbs. Add via SPM: github.com/firebase/firebase-ios-sdk
• Sentry (free tier): Good SDK, excellent error grouping, works well with Claude Code for diagnosis

Analytics

• App Store Connect Analytics (free, built in): Downloads, redownloads, active devices, sessions, crashes. No SDK.
• Firebase Analytics (free): Custom events, user properties, funnels, retention
• Mixpanel (free tier): Better funnel analysis and cohort tracking

For a v1 app, App Store Connect Analytics is often enough. Add custom analytics when you know what questions you need to answer.

App updates

Unlike web apps, iOS updates go through App Store review every time. Plan your release cadence:

• Bug fixes: Submit as quickly as possible. Include "Bug fixes and performance improvements" in release notes (users expect this). Review is usually 24-48 hours for fixes.
• Feature updates: Batch features into releases. Pushing every feature individually creates review overhead.
• Expedited review: If there's a critical bug (crashes on launch, data loss), you can request an expedited review through App Store Connect.

# Before every release:
# 1. Increment build number
# 2. Archive
# 3. Upload to TestFlight
# 4. Test on TestFlight for at least 24 hours
# 5. Submit for review

Push notifications

Push notifications require setup on both the iOS side and a server side. For v1, consider whether you truly need them — many apps don't.

If you do need them:

1. Enable Push Notifications capability in Xcode (Signing & Capabilities → + → Push Notifications)
2. Request permission from the user at the right moment (not on app launch)
3. Register with APNs in AppDelegate or using UNUserNotificationCenter
4. Set up a backend service to hold device tokens and send notifications (Firebase Cloud Messaging simplifies this)

App Store reviews

Respond to every review, even negative ones. The App Store shows your responses publicly and it signals to Apple that you care about the app.

• Use App Store Connect to respond
• For negative reviews: acknowledge the issue, tell them you're working on it, ask them to contact support
• For 1-star reviews without text: still respond with something helpful
• Never argue with a reviewer

Version deprecation

Apple periodically requires apps to be updated or face removal from the store. Watch for:

• SDK requirements: Apple sets a minimum Xcode/SDK version each year (usually announced at WWDC)
• Privacy manifest: Required since iOS 17.x — your app must declare what APIs it uses
• App Store Review Guideline changes: Subscribe to Apple Developer news