Apple Confirms New App Store Policies on Bug Fix Updates and Challenging Guidelines Are Live

[AndiG]

It's as simple as saying "Fixed __ bug that caused app to crash when using >iOS13"

Ok let’s take this to reality - 15 little bugs fixed equals 15 lines of Changelog really no one reads.

- Fixed a race condition that could lead to a crash during app startup
- Fixed horizontal spacing in AutoLayout of Messenger view
- Fixed a memory leak in ..
- Improved error message
- Adapted new guideline from Apple saying
- Workaround a bug Apple introduced with ...
...

vs

- Improved stability
- New feature that lets you ...

This what the user wants to know. I even doubt Apple would accept this technical kind of release note - imagine 5 updates in a row ....

 

[FaustsHausUK]

How so? It's transparant for the developer, which is literally all that's needed.
Are you implying the end user should know what % goes to the developer and what % goes to Apple?

I don't know what % goes to who from anything I buy because it's literally not my business. Imagine going to a store and asking who gets what % off your bill lmao.

No, I mean: what exactly is that 30% for? What is the breakdown? They are being hammered from all angles right now, and the seemingly arbitrary 30% cut is a big focus of that. This update addresses their rules and a developer’s ability to challenge them, which is the other big focus. I like the App Store, but I’m worried it’s going to see an app exodus if they don’t improve quickly.

 

[Jeaz]

They want suggestions on how to revise the guidelines?
Here’s one: allow cloud gaming services!
So incredible offbeat to block innovation that could help propel iPhones, iPads and aTVs from okish gaming distraction to full on console competitors. Sorry, a bit OT but can’t stop myself ranting about this

 

[PSeg90]

Ok let’s take this to reality - 15 little bugs fixed equals 15 lines of Changelog really no one reads.

- Fixed a race condition that could lead to a crash during app startup
- Fixed horizontal spacing in AutoLayout of Messenger view
- Fixed a memory leak in ..
- Improved error message
- Adapted new guideline from Apple saying
- Workaround a bug Apple introduced with ...
...

vs

- Improved stability
- New feature that lets you ...

This what the user wants to know. I even doubt Apple would accept this technical kind of release note - imagine 5 updates in a row ....

@AndiG Thanks for telling other people what they should and shouldn't read. However, I do read every single line of a change log for new updates. If the developer is too LAZY to list the new features or fix an actual bug that I have experienced, then I have no reason to update the app. I need to know what you did to make this version different than the previous version. That's not too much to ask.

 

[Snownoob]

I didn’t know you could price an app $5.49...?

You price your app in tiers, for example you can price an app at the first tier, which in the US is US$0.99, but in Australia, would be AU$1.49

 

[recoil80]

It's as simple as saying "Fixed __ bug that caused app to crash when using >iOS13"

Look at the latest iOS update, they don't even mention the new COVID API in the changelog, there are a couple of features and then "bugfix".
If they don't bother putting everything in the changelog, why should developers?

Anyway, if there is a huge bug fixed, I write it in the message. But it has to be something affecting the majority of users, while most bugs in apps only affect a small user base.
If your app crashes all the time, chances are it doesn't even pass the app store review.
The example you give could actually be one of the few cases I'd write in the changelog, because if the bug is specific to an iOS version, especially a new one, I want to point it out it is fixed because users with a particular iOS version may wait to download the update due to the bug.

 

[TimFL1]

Only non-devs complain about the generic „bug fixes“ changelog line.

Most of my daily patches are about library fixes and performance improvements, nothing the end user would care about or understand.

 

[Madonepro]

They want suggestions on how to revise the guidelines?
Here’s one: allow cloud gaming services!
So incredible offbeat to block innovation that could help propel iPhones, iPads and aTVs from okish gaming distraction to full on console competitors. Sorry, a bit OT but can’t stop myself ranting about this

Have you thought that Apple, as a business may not want to pursue that channel, and would rather stick to the prosumer and consumer personal computer lines. They have never shown an appetite to go after gamers, but have long attached themselves to those in the creative arts, and the education market.
Rule of business, pick your enemy well and don't commit to a battle that is unlikely to be won.

 

[alien3dx]

I've been a Software Engineer for about a decade. I understand the development cycle. Yet, I still value communication to end users. You can both say "WE LAUNCHED FEATURE XYZ!!!" and "We fixed a crash that could occur on workflow XYZ". Like I said, it doesn't have to be exhaustive, but if it's a bug affecting a lot of users, it might be worth point out. To a large portion of customers, I'm guessing saying a generic "We fixed bugs" seem lazy, and it looks like some users on this forum agree.

even some bosses dont have any idea flow and concept. i want fixed by tommorow!

 

[alien3dx]

Agreed. If a user is experiencing a specific issue, having it listed (or not) in the release notes is informative and can determine a course of action.

it more on patch note , not technical note request. Let see i got ticket i create a patch note. What miss confuse is something like " Repair bugs suddenly appear on new update xcode, has to change everything because new update xcode is a mess again and we need to support new mess ios14 which in beta version. To many depreciate function because apple freakin lazy"