Building an app is one thing; shipping it is a completely different discipline. After working on multiple iOS apps (flashcards, investment tracking, vocabulary learning), I realized that “done” is not when the UI looks good—“done” is when the build is stable, the user journey is consistent, and the App Store review process is satisfied.
The first hard lesson was Apple’s ecosystem: certificates, provisioning profiles, bundle IDs, and the difference between “it runs on my phone” and “it’s a valid release artifact.” I learned to treat code signing like part of the product, not a last-minute obstacle.
Second, the review process forced me to think about edge cases and clarity. Small things like permissions copy, privacy policy links, and consistent in-app wording matter. I started keeping a release checklist: test account readiness (if needed), permission prompts, subscription/cancellation flows, and screenshot correctness for multiple device sizes.
Third, I improved my debugging workflow. Once real users arrive, crashes and weird device-specific issues appear. I got better at reproducing issues, reading logs, reducing uncertainty, and shipping fixes quickly without breaking other features.
What I’m improving next: more automation in the release pipeline (build + versioning + changelog), and stronger pre-release testing habits. Shipping taught me that consistency beats hero coding.