02-23-2015 09:25 AM
153 ... 567
tools
  1. tiziano27's Avatar
    You're absolutely right. No matter what happens, Microsoft should always ignore feedback because the majority of users would not vote anyway.
    Publishing a website to recollect feedback assuming that the data comes from a representative sample of the target market is even more stupid than ignoring the feedback.
    Few people use UserVoice. The results can be skewed for small organized groups with the weirdest motivations.
    02-23-2015 07:37 AM
  2. jasqid's Avatar
    Simple solution. Hamburger goes to the bottom, opposite the ...
    Speaking of ... why don't they just put all those setting features in the ...?
    02-23-2015 08:53 AM
  3. manicottiK's Avatar
    Simple solution. Hamburger goes to the bottom, opposite the ...
    Speaking of ... why don't they just put all those setting features in the ...?
    Who is the "they" in your sentence? It can't be Microsoft because they just provide the capabilities to put 4 buttons in the app bar and any reasonable number of things in the app menu that appears below the icon buttons.

    Microsoft is pretty vague about purposes. Here's Microsoft's current word on app bars: App bars provide users with easy access to commands...App bars can also be used to show commands or options that are specific to the user's context...They can also be used for navigation among pages or sections of the app. So, they are functions or navigation related to the app or its content.

    Let's assume that pivots will continue to exist for apps that need multi-section pages. It seems likely that the section headers will get smaller, just as the "Hub" section headers (see People, Xbox Music, etc.) are smaller than "Panorama" headers (see Baconit). This provides us with in-page navigation.

    The question is, does primary navigation go on pages, as it typically has with "list based" apps (i.e., WP apps and many, many, iOS apps), or does it go in a separate UI element that we currently call a "hamburger menu"?

    Hamburger can be designed to be available on every page and to provide direct access to all pages/functions within the app, but it doesn't need to be accessible from everywhere, it doesn't need to provide direct access to everything, and it doesn't need to look like a vertically scrolling menu.

    Thought exercise: imagine an app bar button shaped like a house. When pressed, a multi-tab page of app sections is displayed. Tapping an item brings the user to the selected page such that pressing the hardware Back again returns the user to the page that he was on before pressing the app bar's house button. While looking at the multi-tab page of app sections, pressing the house button again (or the hardware Back button) makes that page disappear so that the user can see the page that he was looking at before. This house button is available in the app bar of every page and it provides direct access to everything. Is it a "hamburger"? Do we care?
    02-23-2015 09:25 AM
153 ... 567

Similar Threads

  1. still no double tap to wake??
    By ZezzeX in forum Nokia Lumia Icon
    Replies: 6
    Last Post: 02-16-2015, 11:06 PM
  2. Changing Microsoft accounts
    By ReconVirus in forum Ask a Question
    Replies: 1
    Last Post: 02-14-2015, 09:21 AM
  3. not able to download some apps
    By sagarmore9904 in forum Windows Phone 8.1
    Replies: 1
    Last Post: 02-14-2015, 02:08 AM
  4. Why am I unable to get Project Spartan Browser to work?
    By Windows Central Question in forum Ask a Question
    Replies: 1
    Last Post: 02-14-2015, 01:53 AM
LINK TO POST COPIED TO CLIPBOARD