Forum Discussion
New app launcher / home mixed experience
- Nov 29, 2017
I've learned that the flighting for Office.com has some cookie context, so an individual user experience could vary based on machine/browser. We are working to change this mechanism to a true user - based flight moving forward, so the experience for an individual user does not vary.
From the O365 app launcher perspective, a user outside of First Release should NOT be seeing the new experience. If you could message me directly with tenant information I am happy to investigate. This is unexpected behavior as the new launcher is only exposed to First Release.
Agreed! We have been talking about some of these things here as well. I've got the app gallery, new app launcher and the old office home experience on selective FR. Changing web browsers for me doesn't make a difference.
The new web experiences shouldn't be crossing over to standard users as I understand it. The Office 365 App launcher is designated as a major update and has 16 days to go (at least) before it goes into general release, according to the Message center.
Just tagging Brian Levenson in case there is anything we are missing!
- Anne MichelsNov 22, 2017Former Employee
Adding Tom Batcheler and BinduPillai to help with this.
- Benoit FournierNov 27, 2017Iron Contributor
Now that Thanksgiving is over, I was expecting a reaction from MSFT. From what I read here, I am not the only one affected by this strange behavior.
Is it a bug or it is working as expected? It's not the ideal situation when updates are visible outside of first release users before official availability date.
Thanks
- Cian AllnerNov 28, 2017Silver Contributor
It is strange that we are left guessing when just a bit of clarity would easily set thing right. I've used this example and a couple of others in a new post on what could improve situations like this - More precision with Message center.
One of the points I've made is that this is a 'major update' and now with 9 days to go until potential GA but we haven't got all the components in place to properly evaluate this change. This countdown should only begin once everything is ready, not while parts of it are still rolling out to FR or are glitchy.
Hope we hear what's going on soon!