The awful agony of the app store: When software delivery goes wrong
summary
A hobby iOS project that spent five years in development becomes a Wordle-like game used to test App Store delivery and hits bureaucracy: first attempt two months after picking a guinea‑pig app, then six submissions over eight months with repeated rejections for couldn't test in-app purchases, missing US EULA link, UI fitting on one device and copycat look‑and‑feel claims. Outcome: app never reaches the store, manual IAP checks and up to 100 beta testers only partially salvage it.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:10Building iOS apps without App Store
- 3:57Wordle clone project
- 7:03First submission rejected
- 11:36New game after rejection
- 16:13Months of rejections
- 18:22Final rejection impact
- 19:23Hope with beta testing
- 21:09New game and solution
- 23:18Good product development
- 24:41Message of hope
related talks
38mWhen Software Delivery Goes Wrong
10mI am done -
26mThe Hurdless of Releasing and Maintaining a Mobile App
35mFrom fear to air: embracing over-the-air app updates
41mImplementing Continuous Delivery with IOS
46mContinuous Delivery for Native Apps
40mHow to fail a software project fast and efficiently?
28mHow to ship apps better, faster, stronger
