> but the marketing/blog posts speak of the feature like it's already launched.
Yeah, seemingly tons of companies do this in a very weird way. Either make the switch 100% once you publish the press release, or wait until you reach 100% then publish. Starting the experiment with gradual rollout and then making the press release immediately seems like asking for potential problems and confusion among users.
But consider what the alternative looks like: People randomly see unexpected options in their apps, go to look for information about them, and don't find anything, or find some random Reddit discussion where no one is sure what's going on.
If the new feature looks random and unexpected and causes users to go to Reddit -the developer is doing terribly bad UX, and equally bad marketing and customer support.
A proper announcement done the day of the release, or an embedded notification like what Firefox already does (a "What's new" tab) that can be easily dismissed without any "Reminder me later" cr*p solves the issue.
Yeah release notes, in-app help, intuitive UIs, and version documentation hosted on your own website are definitely not possible. Gotta instead cater to the LCD of people who won't be using Firefox in the first place, it's reddit spam or nothing.
Yeah, seemingly tons of companies do this in a very weird way. Either make the switch 100% once you publish the press release, or wait until you reach 100% then publish. Starting the experiment with gradual rollout and then making the press release immediately seems like asking for potential problems and confusion among users.