1–5 of 5 posts
How do you all handle third-party "blockers"/Apple reviews as part of your day-to-day planning?
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.
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…
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
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…
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