@Don Jon :
I like your updated mockup.
having the cover on the list view is nice (it could even be in real 3D later, driven with right stick or touchscreen)
Your flow idea is standard, it's just flow at bottom half + reflection + background.
Except that the background you used doesn't exists and the users will have to make a background repository. We thought using the pictures in the meta folder would be easier and everybody already have them.
if users want custom picture, they can change it.
it's nice to see a TV+gamepad at the same time.
Like I suggested previously, I think users should be able to select both display independently (given the controls are the same, like "dpad right->next game on flow" which will not be natural on a list view, unfortunately)
flow : right/left to change games
list : up/down to change games
grid : up/down/left/right to change games
I think it should do the same : right=down, left=up, so changing a game on a display is also selecting it on the other one.
event on one display should affect the other one, like scrolling the flow on TV automatically to center the selected game when touching a game on the pad.
That will also be an issue when using grid+list, with a grid you might want to press down to change rows, but it will select only the next game from the list view.
Down will be used for two different thing here.
list : down = next game
grid : down = 6th next game (if 5 games per line)
That's what I meant with "We need to decide the button behavior first". having different themes with different controls will not be practical.
Change view mode is unnecessary. it should be a setting.
I know it was an option to switch grid/list from the "same concept", but it could be two different views that the user select : one on TV, one on gamepad, and use the "swap" option to change the display.
it's not one view, but two different view to code. so why not make them independent and let the user choose if he wants grid+list or flow+list or flow+grid?
the "change view mode" can become "swap"
You only placed a (-) in the corner, I suppose it's the settings?
I feel it looks better at the place of "change view mode"
it's the global setting, or it will open a choice "global or current game" ?
or will the individual setting be placed on a "launch game" popup screen? Select game -> option & Start. (I prefer this model)
The (-) is not displayed on your flow mockup.
users need to know how to access the settings from all views.
I would like a WiiU design on that view. For example, go to the download queue program, and at the bottom you have "Back (B)" and "(-) I don't remember the text here"
I think this kind of buttons are nice, in the corner, and it can be touched easily when the design is on the pad.
Keep in mind we haven't seen the mockup for our other member. we don't know yet which design to choose and what to do.
I only think it would be nice to have "swap display" and "independent display selection", but we haven't talk about it yet. Dimok is the one coding all this, the difficult task is his.
It's a lot of text in my post, but we need to talk about it together, see everyone ideas before starting something.
Edit:
I thought about it since I wrote this post.
I think we should limit the D-pad control to TV and touch control to gamepad.
One design should be both controllable with Dpad and touch, but the current selected input must be based on its location (as it's swappable!). The gamepad should be
only touch controllable, not button controllable. it will prevent conflicts with the designs.
when you create a design, think how it could be used from a tablet, and how it could be used with buttons.
flow : touch to scroll the games and can touch a game not in center to center it, dpad right/left to change game. (a setting should be used to control the direction of the move when pressing "right")
grid : touch any icons to open the game, or arrows to scroll game list. dpad to move an overlay cursor, L/R to scroll full pages.
list : touch to scroll up/down to move the list (not using the arrows), dpad to move a cursor to select game.
if a game is not selected, touch = select it.
if a game is already selected, touch = open the game window. (option, start, game info)
for settings (there's not a lot of mockups, only Exlipse did one), I think we need to decide if it's best to "click an option" to scroll the choices, to display all choices on screen and press on the one we want.
like this :
server : ON (press to switch to OFF, or press A)
or
Server : [ON] OFF (click on ON or OFF to change the selection, dpad right/left to change, or press A to edit and then right/left to change then A to confirm or B to cancel)
Second option looks nicer when dealing with touch screen, but not when there's more than 3 choices. too much choices will clutter the setting screen. maybe a scrollable dropdown popup could be used like on android.
