4 ms·
Just wait until you have to manually type "what's new" in each release in each different language your app supports that perhaps adds an invisible fix the user
by collaborative 5y ago
Just wait until you have to manually type "what's new" in each release in each different language your app supports that perhaps adds an invisible fix the user couldn't care less to know about. Oh, and appstoreconnect is designed to prevent you from automating this. This huge time waster is what really makes my blood boil when I think of Apple
- reayn 5y agoNot to be the devil's advocate here but... that seems fine to me? Lots of more technical people complain about terrible changelog entries (I've seen quite a few posts on HN about it too iirc), so I guess no matter what Apple does in this case they'll be a target; just that kind of situation. Maybe it could be a per-project toggle whether having a "what's new" section is necessary (though on second thought toggling that off might become the new norm leading back to the good old useless changelogs).
- collaborative 5y ago90% of updates change things that users would be offended to be told about. They would say "why do I need to know this?" Example: changing width of buttons x y and z under sub menus a b and c to support x y and z device edge cases. In these updates, devs just paste the same "what's new" they wrote for the previous release (which has the info that actually matters, like something new users want to hear about). Releases don't go from 1.1 to 1.2 in mobile, they go from 1.1.43.1 to 1.1.43.2. Having to manually type the same thing in 32 different languages for such small changes is what makes you really dislike the process. You can just select your release notes from the last release on the Play Store