Cracking the Code to Mobile Productivity medium.com3 years ago in #UX Love336

In Seattle, an engineer thumbs through a Mumbai-based coworker’s edits while walking between meetings. In rural China, an artisan uses their phone to sell their creations. In Johannesburg, a lawyer texts back a client before catching the bus. These real-life snapshots show the diverse and evolving workflows of today’s 5 billion mobile users worldwide. In many ways, mobile productivity is still a code waiting to be cracked. Beyond mobile-first and mobile-only markets where necessity mandates it, we can rarely accomplish as much on a phone as we do on our PCs. However, we believe in empowering everyone to be fully productive on any device. Our teams’ focus on emerging markets, inclusive design, and accessibility has broadened our aperture as we create more tailored, intelligent experiences across Microsoft 365. Today, we’re excited to unveil redesigns to our flagship mobile apps! We’ve redesigned Outlook, OneDrive, Word, Excel, and PowerPoint. You can also expect new versions of Teams, Yammer, and Planner soon. These redesigns contribute to broader company efforts to take mobile productivity to the next level. At Microsoft Ignite, we publicly previewed our beta Office app and Fluid Framework. Office combines multiple Microsoft 365 mobile experiences in one app, and Fluid is a new technology that breaks broad experiences into dynamic, real-time components ideal for mobile scenarios. Beyond the public eye, we’re also conducting global research, designing a mobile-born version of Fluent, exploring scenarios for dual-screen experiences, and creating mobile UI toolkits for external developers to build this mobile future alongside us. Read on for a behind-the-scenes look at our research, design process, and future vision for Microsoft 365 mobile experiences. URL Out – – medium.comDate – 2019-12-09 19:40:35

Like to keep reading?

This article first appeared on If you'd like to keep reading, follow the white rabbit.

View Full Article

Leave a Reply