flinchbot

I'll jump in: Having to hover to find anything. Bug riddled patches (The September one already has 2 identified). The Lync client randomly freezing and being non-responsive. Backtracking on changes to the notification area icon. Is it supposed to be more finger friendly? Because it is only barely better than the 2010 client on a Surface. Tracing files buried 242 directories deep which is tedious to talk end users through for log collection.

When joining a meeting with a presentation (PPT, Desktop share) it always defaults to Presenter view. This view is pointless and the first thing I do every time is switch to Content view. (Problem with presenter view: Static, low-res picture blocks part of the shared screen. I don't need to see their face. I know who is presenting). An option to set default sharing view would be really swell.

Those are the ones off the top of my head. I blame the Office team for most of this, not the Lync team. The 2010 client was solid and reliable. Once the Office group got their paws on it, it's been a mess.

And being able to add custom emoticons. Seeing a beer icon is fine. Seeing an animated smiley drinking a beer? Full of win.

For Hangouts, Google dropped the open protocol XMPP for something proprietary. http://www.zdnet.com/google-moves-away-from-the-xmpp-open-messaging-standard-7000015918/

Until Google publishes their specs, Lync <-> Hangouts is a dead issue.

Have there been any thoughts or discussions internally in at least moving the AutoAttendant feature out of Exchange UM and into Lync? Having to bring up Exchange UM for a pass-through automated answering service seems a bit much while it would be a perfect fit as a native Lync feature. (Think of SBA's and small office survivability who rely on an AutoAttendant).