When Software Delivery Goes Wrong
summary
Starts a hobby iOS project that sat in development for five years, then builds a Wordle clone (one month) and adds help, EULA and in‑app purchases (another month). Submits repeatedly over eight months, hits three initial rejection reasons, spends five rounds on a missing locale EULA field and ends up at the 13th rejection for “leveraging Wordle’s popularity.” Uses TDD for game logic but can’t automate or test in‑app purchases, lacks continuous integration, abandons App Store and pivots to beta testing and Android.
AI-written summary · about
chapters (7)
related talks
27mThe awful agony of the app store: When software delivery goes wrong
10mI am done -
41mImplementing Continuous Delivery with IOS
26mNo Whiteboards Allowed
46mContinuous Delivery for Native Apps
40mHow to fail a software project fast and efficiently?
41mAutomating mobile applications from dev to production
26mThe Hurdless of Releasing and Maintaining a Mobile App