Comment on Updates that don't tell me what is being updated
GissaMittJobb@lemmy.ml 3 weeks ago
Modern mobile app development almost always releases features gradually behind feature flags, so changelogging things is not necessarily practical to do.
5A7A@feddit.org 3 weeks ago
Why not? Put “added feature XY, staged rollout in the coming X days” in the changelog.
Certainly better to know that there is a new feature and you might get it now or some time later, than some nonsense like “nothing says fall like financial progress”
GissaMittJobb@lemmy.ml 3 weeks ago
Well, you might be inclined to not roll the feature out at all, depending on the results you see from the rollout/an A/B-test. Also, having it written out with a date in the changelog binds you to that date, unless you want the embarrassment of not shipping on a promised time. Maintaining a changelog for very large app development organizations is also a pretty damn hard task, trying to coordinate whatever all teams are releasing in a particular build.
I agree that getting cute with the changelog messages is a bit stale. Might as well not add anything at that point.
IMALlama@lemmy.world 3 weeks ago
I feel this in my bones. Our biggest device contains hundreds of apps and firmware. We generally update the apps and firmware together. It’s nearly impossible to summarize the changes in a meaningful way. What issues were fixed? Likely a few hundred. What new features were added or improved? Another big list. Management thought AI would magically solve this problem, but it turns out that it has no idea which things are worth mentioning vs which should be glossed over.
It sucks both internally and externally.
brbposting@sh.itjust.works 3 weeks ago
Thank you – I will be less frustrated next time I scroll through the iOS App Store change logs.