Ask HN: How do you handle iOS app submissions?

2 points by tedmundy 59 days ago | 3 comments

I'm part of a small team and none of us really have any experience in a "solid" release workflow for iOS. The initial idea was to submit a build for Apple review every 2 weeks, but with the increase in review times we're almost looking at a build-up/queue of builds which isn't ideal. That's not even accounting for any bounce-backs/rejections Apple give us.

How do you all handle third-party "blockers"/Apple reviews as part of your day-to-day planning?

phony-account 59 days ago |

I’m part of a team of six iOS developers and we already have a 2-week cycle without any major problems.

Most of our publishing cycle is automated except for the inevitable last stretch in AppStoreConnect where we need to submit releases manually.

Management wants us to reduce the diff between releases so we’re considering two releases per week instead. This will mean an increase in ‘submission anxiety’ balanced by a reduction in the scale of changes made (so rollbacks should be easier).

One member of our team came from a very prominent game platform that made new releases every weekday. So a two week cycle is nothing to worry about.

tedmundy 58 days ago | |

Thanks for responding!!

This is what we currently are going for. How do you guys handle bounce-backs from Apple? Are those handled in the next cycle, or picked up urgently: e.g they don't like X feature, take it out or adjust it

CafeRacer 59 days ago |

subsequent reviews are almost always faster than the first one in my experience