It’s a bit different with mass market mobile applications because of the supply chain constraints - most notably the Apple reviewing process. Your next app release may for whatever reason they feel like unexpectedly take an additional week, so do ensure that your QA is in order before releasing.
Another significant factor is the lack of control you have over the software once released - any bugs you ship may potentially be out there for a long, long time.
Web applications don’t have these constraints and can as such be deployed an infinite amount of times per day. The same goes for backend services, deploy to your hearts content.
This basically means that most larger mobile applications have adopted approximately weekly release cadences, and that we’ve had to get very good at using feature flagging to control our software in the wild, and avoid large impact of shipped bugs.
It’s a bit different with mass market mobile applications because of the supply chain constraints - most notably the Apple reviewing process. Your next app release may for whatever reason they feel like unexpectedly take an additional week, so do ensure that your QA is in order before releasing.
Another significant factor is the lack of control you have over the software once released - any bugs you ship may potentially be out there for a long, long time.
Web applications don’t have these constraints and can as such be deployed an infinite amount of times per day. The same goes for backend services, deploy to your hearts content.
This basically means that most larger mobile applications have adopted approximately weekly release cadences, and that we’ve had to get very good at using feature flagging to control our software in the wild, and avoid large impact of shipped bugs.
Ahhh… now that makes sense. Thank you, kind stranger!