1. What’s the app’s overall purpose?
For my original and main purpose, was to build an app that functions as a browsable menu. The ideal layout is widescreen tablet/desktop. Originally the menu was for in-store, but changes in rules, regulations, and laws, has pushed me to consider also hosting a separate version on our website. Either way, big screen real estate is what I’m looking for.
2. What types of tasks / flows are desktop views being used for?
I’ll just use pictures.
Looks good overall. Maybe a couple cosmetic tweaks could happen, but I have no major complaints here.
The second Inline tends to add additional unneeded space at the bottom. After fiddling with it sometimes it snaps up where it should be. But overall, there should be no reason for me to scroll down at all, because all of that information can and should fit on the screen being used for this example without scrolling. Both Inline and full versions of their views should appear identical. For example, an Inline Card List should
look 100% the same (padding, outline, flex positioning). They don’t look as clickable as the full view versions - which is why I tried using only 1 out of 3 actions but can’t format it, so it’s black on gray. And stretching the Card’s width to match the Detail just looks silly. Coding the Inlines to function the exact same as their full version allows the UI team to play with width and layouts of the Detail view without need to worry about the impacts on Inlines (as much), since they can be flexible to their parent container.
3. Are desktop users different from mobile users, or do the same users switch devices according to context / task?
Small screens will almost never be used, but the thought that they can be used is always good.
4. What are some of the current pain points your users are experiencing?
A few UI bugs that are still waiting to be fixed (only using 1 out of the 3 action slots on Card Lists doesn’t respect dark/light theme or format rules). Certain Inline views looking vastly different to the full versions. And the white-space on the screen not being utilized.
5. What types of desktop views are seemingly not available in your current apps that would better address your current use cases?
Can’t think of a specific view type, other than just every view always making the most of whatever real estate is available. I feel like Card view nails this, mostly. The widths of each card and number in each row is variable to screen width. Every view should be built in this style. Detail views should start to rearrange some things more horizontally before going down vertically. Or, perhaps, Detail views should be built more drag n drop style. More control of the size/layouts of Labels/Descriptions when shown on Details/Forms. More control how confirmation messages look (easy to edit and format the yes/no options and also customize the header instead of just “Confirm” - yes, I could change this is localization, but maybe I only want to change it for just one).
I made this super quick and crappy mockup of the direction I think Detail views should go. Obviously, with some better cleanup than my copy/paste screenshot collage can do. With maybe a more square-able Header image.