> "Begin rollout of feature <foo>" "We are rolling out <foo> in <timeframe> to ensure <x> about <y>, and rollback if <z>. You will notice you have <foo> when <bar>."
That’s a guaranteed way to get users complaining that they don’t have a new feature that you “promised” that they may never receive. It also isn’t appropriate for multivariate testing and just isn’t going to be understood by most users anyway.
There are way to do this in a decent way, but you have to do it within the application using your own logic. The change log provided by the platform is inadequate.
> If you don't put anything about new features, don't be surprised when users don't use them (because why would they know)
If you need to tell your users about new features in the App Store change log, then you’ve already failed because almost nobody sees it. Users know about new features because either a) it’s obvious when you use the application, or b) you tell them about the new features somewhere they will actually see it, at an appropriate time.
> or complain what something "breaks" (or just changes on their workflow) because your changelog communicates nothing.
A change log does not prevent this. You are attributing a lot of power to the platform change log that it simply does not have.
That’s a guaranteed way to get users complaining that they don’t have a new feature that you “promised” that they may never receive. It also isn’t appropriate for multivariate testing and just isn’t going to be understood by most users anyway.
There are way to do this in a decent way, but you have to do it within the application using your own logic. The change log provided by the platform is inadequate.
> If you don't put anything about new features, don't be surprised when users don't use them (because why would they know)
If you need to tell your users about new features in the App Store change log, then you’ve already failed because almost nobody sees it. Users know about new features because either a) it’s obvious when you use the application, or b) you tell them about the new features somewhere they will actually see it, at an appropriate time.
> or complain what something "breaks" (or just changes on their workflow) because your changelog communicates nothing.
A change log does not prevent this. You are attributing a lot of power to the platform change log that it simply does not have.