Teams gets the App Launcher

%3CLINGO-SUB%20id%3D%22lingo-sub-207061%22%20slang%3D%22en-US%22%3ETeams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207061%22%20slang%3D%22en-US%22%3E%3CP%3EI%20saw%20a%20tweet%20from%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F210%22%20target%3D%22_blank%22%3E%40Anne%20Michels%3C%2FA%3Ethat%20the%20browser%20version%20of%20Teams%20has%20the%20App%20Launcher%20now%2C%20but%20I'm%20not%20seeing%20it%20yet%20in%20my%20tenants.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%2C%20MS%20still%20has%20not%20figured%20out%20how%20to%20use%20the%20Message%20Center%20for%20all%20of%20the%20relevant%20announcements%20(%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-207061%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChange%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-211825%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-211825%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20you%20are%20on%20the%20Teams%20team%2C%20it%20would%20be%20nice%20if%20those%20devs%20could%20work%20with%20the%20other%20dev%20teams%20to%20use%20consistent%20controls.%20I%20don't%20understand%20why%20there%20are%20so%20many%20different%20file%20pickers%20and%20people%20pickers%20across%20the%20workloads.%20The%20desktop%20office%20team%20was%20able%20to%20standardize%20on%20basic%20controls%20like%20this%20many%20years%20ago%2C%20but%20the%20web%20dev%20teams%20can't%20seem%20to%20figure%20out%20how%20to%20share%20code%20and%20avoid%20reinventing%20common%20user%20experiences.%3C%2FP%3E%3CP%3EFor%20example%2C%20adding%20a%20member%20to%20a%20Team%2FGroup%20should%20be%20the%20same%20in%20Teams%2C%20SharePoint%2C%20Outlook%20Web%20App%2C%20and%20the%20Office%20365%20Groups%20admin%20page%2C%20but%20it%20is%20not.%20The%20UI%20looks%20and%20behaves%20differently%20in%20each%20of%20these%20applications%20that%20were%20supposedly%20created%20by%20the%20same%20company.%3C%2FP%3E%3CP%3EUnfortunately%2C%20the%20efforts%20by%20the%20Office%20UI%20Fabric%20team%20to%20provide%20standardization%20across%20the%20platform%20have%20not%20been%20as%20successful%20as%20I%20had%20hoped.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-211541%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-211541%22%20slang%3D%22en-US%22%3E%3CP%3EWell%20I%26nbsp%3Breally%20like%20brutally%20honest%20and%20so%20thanx%20for%20the%20directness%20of%20your%20comments.%26nbsp%3B%20As%20I'm%20sure%20you%20know%20I%20can't%20speak%20for%20anyone%20else%20but%26nbsp%3BI%20can%20empathize%20with%20what%20seems%20so%20simple%20from%20the%20outside%20of%20our%20company.%26nbsp%3B%20All%20I%20can%20say%20is%20that%20it%20is%20a%20O365%20wide%20initiative%20to%20improve%20our%20usage%20of%20this%20channel%20and%20we%20in%20Teams%20know%20how%20important%20it%20is.%26nbsp%3B%20Keep%20the%20feedback%20coming%20and%20I'll%20do%20what%20I%20can%20to%20get%20the%20job%20done.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-211539%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-211539%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20acknowledgement%20that%20you%20are%20going%20to%20be%20improving%20your%20efforts%20in%20this%20area%2C%20but%2C%20to%20be%20brutally%20honest%2C%20we%20have%20been%20hearing%20this%20from%20many%20people%20at%20Microsoft%20for%20several%20years.%20It%20is%20really%20hard%20to%20understand%20why%20it%20is%20so%20difficult%20to%20get%20all%20of%20the%20apps%2Fservices%2Fworkloads%20to%20use%20this%20communication%20tool.%20The%20fact%20that%20key%20executives%20tweet%20and%20blog%20about%20new%20changes%20and%20that%20same%20information%20does%20not%20show%20up%20in%20the%20official%20message%20center%20is%20inexcusable.%20Posting%20a%20message%20to%20the%20o365%20message%20center%20should%20be%20part%20of%20the%20release%20cycle%20checklist.%3C%2FP%3E%3CP%3EI%20am%20quite%20sure%20that%20there%20are%20many%20global%20admins%20that%20don't%20follow%20all%20of%20the%20various%20twitter%20account%20and%20blog%20feeds%20and%20are%20relying%20on%20the%20Message%20Center%2C%20because%20that%20is%20what%20they%20were%20told%20to%20use.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-211493%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-211493%22%20slang%3D%22en-US%22%3E%3CP%3EHI%20Dean%20and%20thanx%20for%20your%20feedback%20on%20this.%26nbsp%3B%20I%20can't%20speak%20for%20all%20of%20M365%20but%20in%20Teams%20we%20are%20working%20to%20snap%20all%20major%20announcements%20to%20the%20Message%20Center.%26nbsp%3B%20You%20should%20see%20improvements%20in%20this%20over%20the%20next%20quarter.%26nbsp%3B%20We%20know%20it's%20an%20important%20channel%20to%20keep%20everyone%20aware%20of%20what's%20coming.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207083%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207083%22%20slang%3D%22en-US%22%3EAgree%20here....the%20Launcher%20has%20been%20there%20for%20at%20least%20two%20weeks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207082%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207082%22%20slang%3D%22en-US%22%3E%3CP%3EThey%20need%20a%20King%2FQueen%20of%20Office%20365%20to%20dictate%20that.%20Jeff%20Teper%20is%20obviously%20the%20top%20person%20for%20SPO%2C%20but%20I%20have%20no%20idea%20who%20oversees%20all%20of%20the%20O365%20Suite.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20been%20struggling%20with%20this%20for%20years%20and%20the%20inconsistencies%20between%20the%20groups%20responsible%20for%20each%20workload%20are%20getting%20worse%20instead%20of%20better.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207073%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20gets%20the%20App%20Launcher%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207073%22%20slang%3D%22en-US%22%3EBy%20coincidence%20Dean%20I%E2%80%99ve%20been%20having%20the%20same%20issue%20over%20Office%20365%20Analytics%2C%20specifically%20My%20Analytics.%20Microsoft%20does%20need%20to%20mandate%20all%20it%E2%80%99s%20teams%20to%20use%20the%20Message%20Center%20as%20a%20%E2%80%98single%20source%20of%20truth%E2%80%99%20With%20the%20advent%20of%20Microsoft%20365%20doubly%20so.%3C%2FLINGO-BODY%3E
Highlighted
Respected Contributor

I saw a tweet from @Anne Michels that the browser version of Teams has the App Launcher now, but I'm not seeing it yet in my tenants.

 

Unfortunately, MS still has not figured out how to use the Message Center for all of the relevant announcements (:

7 Replies
Highlighted
By coincidence Dean I’ve been having the same issue over Office 365 Analytics, specifically My Analytics. Microsoft does need to mandate all it’s teams to use the Message Center as a ‘single source of truth’ With the advent of Microsoft 365 doubly so.
Highlighted

They need a King/Queen of Office 365 to dictate that. Jeff Teper is obviously the top person for SPO, but I have no idea who oversees all of the O365 Suite.

 

We've been struggling with this for years and the inconsistencies between the groups responsible for each workload are getting worse instead of better.

Highlighted
Agree here....the Launcher has been there for at least two weeks.
Highlighted

HI Dean and thanx for your feedback on this.  I can't speak for all of M365 but in Teams we are working to snap all major announcements to the Message Center.  You should see improvements in this over the next quarter.  We know it's an important channel to keep everyone aware of what's coming.  

Highlighted

Thanks for the acknowledgement that you are going to be improving your efforts in this area, but, to be brutally honest, we have been hearing this from many people at Microsoft for several years. It is really hard to understand why it is so difficult to get all of the apps/services/workloads to use this communication tool. The fact that key executives tweet and blog about new changes and that same information does not show up in the official message center is inexcusable. Posting a message to the o365 message center should be part of the release cycle checklist.

I am quite sure that there are many global admins that don't follow all of the various twitter account and blog feeds and are relying on the Message Center, because that is what they were told to use.

Highlighted

Well I really like brutally honest and so thanx for the directness of your comments.  As I'm sure you know I can't speak for anyone else but I can empathize with what seems so simple from the outside of our company.  All I can say is that it is a O365 wide initiative to improve our usage of this channel and we in Teams know how important it is.  Keep the feedback coming and I'll do what I can to get the job done. 

Highlighted

Since you are on the Teams team, it would be nice if those devs could work with the other dev teams to use consistent controls. I don't understand why there are so many different file pickers and people pickers across the workloads. The desktop office team was able to standardize on basic controls like this many years ago, but the web dev teams can't seem to figure out how to share code and avoid reinventing common user experiences.

For example, adding a member to a Team/Group should be the same in Teams, SharePoint, Outlook Web App, and the Office 365 Groups admin page, but it is not. The UI looks and behaves differently in each of these applications that were supposedly created by the same company.

Unfortunately, the efforts by the Office UI Fabric team to provide standardization across the platform have not been as successful as I had hoped.