Mac apps and web apps:

• Make code change.
• Release to customers.

iOS apps:

• Make code change.
• Wait for Apple to approve TestFlight beta.
• Wait even longer if the build is stuck “processing” for unknown reasons.
• Wait for Apple to approve final version.
• Release to customers.

Just a stark difference. ☹️

@manton I wish we still had a third choice. iOS and Android duopoly isn’t great. We needed Microsoft or Palm to have a polished Apple alternative to keep them honest!

@manton I recall there being a sidetrip in there for “Resubmit after Apple doesn’t approve for some unknown reason.” Perhaps things have improved since I last did iOS development.

@manton you can skip the TestFlight part of that trip. 😀

@cheesemaker I used to skip it but then people on the beta would never know about the update! So now I do both for every release.

@manton I usually do both simultaneously fwiw

@manton I’m sure everyone does that these days, but when I worked on building the backend APIs for a massive iOS app in the past, I remember, we devised our own DOM-like syntax for the responses, so that the app would more or less tender the UI based on that alone.

It was a ton of work to do the praying and all, but we could go by without a full release for most things. We still kept a release cycle for major updates, and as a sort of way to show customers we were still active.