locked
Filter button aside Sort in AppBar

    Question

  • Referring to : http://msdn.microsoft.com/en-us/library/windows/apps/hh868273 / "Your app’s hub page" paragraph

    1.- Is it permitted to add a "Filter" function to the AppBar, aside the Sort Button. An example would be "High Budget, Medium Budget, Low Budget" that would have effect across all Sort options.

    2.- If yes, would the Filter functionality and layout be subject to any restriction

    Thank you

    Tuesday, July 17, 2012 5:02 PM

Answers

  • RE: 1.  Those guidelines are language agnostic (they don't have anything to do with the implementation language).

    RE: 3.  There is nothing preventing you from doing this, just may not be easily discoverable.

    Again Afro... If you have some unique question, please post a new question in the forum.  Thanks!

    -Jeff


    Jeff Sanders (MSFT)

    Friday, August 03, 2012 6:01 PM
    Moderator
  • Sure!  What kind of restriction are you talking about?

    Jeff Sanders (MSFT)

    Wednesday, July 18, 2012 2:36 PM
    Moderator

All replies

  • Sure!  What kind of restriction are you talking about?

    Jeff Sanders (MSFT)

    Wednesday, July 18, 2012 2:36 PM
    Moderator
  • So far, we saw the following 2 possible drawbacks for this approach.

    --- Confusing UX experience between Application Filter/Search and Charm Search ---

    1.1.- Functionality 'Filter'

    Here are some 'filtering' scenarios by our Marketing Department:

    - to the basic "Budget Flyout" above, add an option 'Other...'
    - it would cause a panel to display, to let the user choose amongst options like ...
      - different ranges of budget: above $ 1.000, above $ 500, etc.
      - offer monetary conversions (foreign currencies <-> reference currency set by user)
      - choose from offers that are less than a 'month/quarter/year' old
      - etc.

    2.- Functionality 'Search'

    We have also been requested to add a Search facility on top of the filtering akin to:

    - interactively display offers that mention some country names (one or more) that the user enters into a field

    3.- Layout

    In a 'MainPane split screen (3/4-1/4)' scenario, we would have the above flyout (1/4) remain open aside the given result
    in such a manner that the user can adjust the filter and visually experience the feedback (3/4)

    4.- I can now explain the first possible restriction that prompted my question:

    UX people were quite reserved about the scenario because _application-bound_ 'Filter' and 'Search' capabilities
    could be easily confused (by the user) with the _system-wide_ 'Search' present in the Charms/Search.
    Hence the hesitation that some form of UX integration might be required between these two capabilities.

    --- Confusing UX experience  between Filter Settings and Charm Settings ---

    5.- The application would also offer the possibility to memorize interesting Filter patterns, whenever the user formulates them and receives pertinent information results. These patterns could then be recalled - days later - by him using (e.g.) a drop down list.

    6.- This prompted a second possible restriction:

    UX people told us that this would conflict with a 'Default Settings for Filter' concept and a corresponding implementation in the Charm Settings pane.

    ---

    Thank you.











    • Edited by ForInfo Wednesday, July 18, 2012 8:58 PM
    Wednesday, July 18, 2012 6:05 PM
  • I have similar questions - but why is this thread "answered" ?

    Tuesday, July 31, 2012 11:31 AM
  • Because it was answered and marked that way by the person who started the thread.  If you have further questions, please post a new detailed question in a new thread.

    Thanks!

    -Jeff


    Jeff Sanders (MSFT)

    Tuesday, July 31, 2012 12:10 PM
    Moderator
  • hm - but why didn't he post the solution? :(

    Wednesday, August 01, 2012 9:24 AM
  • Hi afroDeluXe,

    Guidelines and checklist for search (Metro style apps) provides an answer to most questions, admittedly with the following considerations:

    1.- the equivalent guidelines have not been published for CSharp/VB

    2.- the usage of the Filter button is not mentioned (does not mean it cannot be used as Jeff answered)

    3.- the memorization of the Searches (to be done 'taking Settings into consideration' (whatever that means)) is not addressed.

    Hope this answer helps somewhat.

    Friday, August 03, 2012 2:24 PM
  • RE: 1.  Those guidelines are language agnostic (they don't have anything to do with the implementation language).

    RE: 3.  There is nothing preventing you from doing this, just may not be easily discoverable.

    Again Afro... If you have some unique question, please post a new question in the forum.  Thanks!

    -Jeff


    Jeff Sanders (MSFT)

    Friday, August 03, 2012 6:01 PM
    Moderator
  • RE 1. The reservation  is made because for CSharp/VB the subtitle is grayed out. I will interpret this as a small documentation glitch and not being done on purpose.

    RE 3. I'd rather wait for somewhat firmer guidelines on this subject, as Metro UX style is still in evolution.

    Thanks!


    • Edited by ForInfo Saturday, August 04, 2012 5:35 AM
    Saturday, August 04, 2012 5:12 AM