Comment

On the contrary, the rate of mobile app updates being high is more of a red flag of an app development team not having the situation under control, being forced to panic-ship fixes.

source

Sort:hotnew top

vivalapivo@lemmy.today ⁨20⁩ ⁨hours⁩ ago
Why? I genuinely think that daily delivery in my field (b2b specialized software) would be a very good practice. Why in mobile apps it’s not the truth?

source
- GissaMittJobb@lemmy.ml ⁨19⁩ ⁨hours⁩ ago
  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.
  
  source
  - vivalapivo@lemmy.today ⁨19⁩ ⁨hours⁩ ago
    Ahhh… now that makes sense. Thank you, kind stranger!
    
    source
- Jiggle_Physics@sh.itjust.works ⁨19⁩ ⁨hours⁩ ago
  Because the rate is more a sign of how often problems are found, rather than how many better new things you are applying.
  
  source
  - SketchySeaBeast@lemmy.ca ⁨12⁩ ⁨hours⁩ ago
    And has nothing at all to do with the AI part of the app getting better.
    
    source
    Jiggle_Physics@sh.itjust.works ⁨11⁩ ⁨hours⁩ ago
    Yes, that was my point.
    
    source