> they said I should check the App Store release notes, which routinely includes the ambiguous line “bug fixes”
The trend of putting just "bug fixes" or "performance improvements" into release notes drives me mad. Your users are not stupid. They know what bugs there the app has and will be happy to know if those specific bugs have been fixed.
"Performance improvements" is equally lame. It could mean that you cleaned up some code and now a function call is 0.05 seconds faster without any visible user benefit. Tell us how the app is faster.
HTML5 apps are sometimes sold on the promise of being able to update themselves without going through an app store review, but you would also lose the standard way of delivering release notes unless you build that functionality yourself.
The trend of putting just "bug fixes" or "performance improvements" into release notes drives me mad. Your users are not stupid. They know what bugs there the app has and will be happy to know if those specific bugs have been fixed.
"Performance improvements" is equally lame. It could mean that you cleaned up some code and now a function call is 0.05 seconds faster without any visible user benefit. Tell us how the app is faster.
HTML5 apps are sometimes sold on the promise of being able to update themselves without going through an app store review, but you would also lose the standard way of delivering release notes unless you build that functionality yourself.