↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Ex-Microsoft Designer Explains the Move Away from Metro

Microsoft’s former design lead argues that Windows Phone’s original Metro interaction model was strong for exploration but weak for organizing information. He says the system had to move toward more standard navigation patterns, with actions on the bottom and navigation on top, because the old swipe-heavy approach hid content and became awkward in real use.

He also ties the redesign to app complexity, one-handed use tradeoffs, One Windows, and Microsoft’s broader move toward consistency across platforms. In his view, the old design gave Windows Phone a distinctive look, but the interaction model did not hold up as well as the platform’s fans wanted.

Reading notes
#

  • The original Windows Phone model placed actions on the bottom and navigation on the sides, but the design lead says that was not a strong pattern.
  • Panoramas and pivots worked for exploration, yet they were poor for organizing information.
  • Swiping hid content and became inefficient when users needed to move through several tabs or sections.
  • The hamburger menu became a common pattern across platforms, while Windows Phone had lacked that model.
  • The placement of the hamburger menu in the top left followed an industry standard, and the designer says design should be invisible rather than unusual for its own sake.
  • One-handed use is a tradeoff, but he says people are less committed to it than is often assumed.
  • For complex apps like Office, a hamburger menu makes more sense because the command set is large and screen space is tight.
  • Simpler apps, like Twitter, do not need the same kind of menu.
  • One Windows also shaped the work, because the design language had to function across devices and screen sizes.
  • Microsoft’s push to put its apps on popular mobile platforms affected design choices on Windows Phone too.
  • The new Windows 10 and Windows Phone UX is described as less distinct, and he says the visuals still need work.
  • He thinks the interaction patterns in Android and iOS are better designed than the old Windows Phone 7 patterns.
  • He says the change is not about copying Android, but about using established interaction research and mainstream patterns.
  • Microsoft moved from a Windows-first stance to supporting iOS first because the older strategy no longer fit the market.
  • The radial menu in OneNote Modern had strengths, but it did not fit the broader system’s right-angle design language.
  • He thinks Windows 10’s redesign is necessary even if it looks less striking.
  • He says Windows Phone should not be killed because it still sells units and Microsoft cannot afford to have no mobile OS.
  • If he could change one thing in Windows Phone, he would change the interaction models.
  • Marketing was not the main problem; users struggled with the device when they tried it.
  • He says Windows Phone’s biggest problems were apps and lack of relevance.
  • He does not think Windows Phone failed in absolute terms, since it outlasted earlier mobile platforms and reached meaningful share in some markets.
  • He sees the future in Microsoft software that works across platforms, including ideas like Sway.