![]() I don't think the overview panel should expand before the extra tools, which are part of the basic panel. Hi Bram, feedback regarding the abstract. Let me know what you think of these? If it’s helpful, I’d be happy to revise these designs and/or continue adapting more pages. These examples may not sufficiently capture the full complexity of uBlock Origin, but hopefully they can still give you a taste of the flexibility that our Android layouts can offer. We have a scrollable tab bar design that can fit all of them. It has enough space to contain almost anything you want. To view this domain information, the user can tap the domain name. I want not only to preserve them, but give them ample space so you can explain as much as you’re able to. One thing that was missing from the Overview panel is +++. Allow/block controls are presented as status to the right of each domain name, and can be modified via a dropdown menu (if “Advanced mode”) is switched on. In the example above, Global and Local Rules are modes that you switch back and forth from/to. My main concern was to have sufficiently large tap targets (48dp) while not losing any feature or complexity. The Overview panel has a high information density, so adapting it was challenging. When users tap “Overview panel”, a familiar-looking table appears. In the example above, it opens in a sub-page. It’s up to you whether this panel is expanded downwards and upwards, or whether it opens as a sub-page. Main user interfaceįor starters, I thought that the entry point for the Overview panel should be clearly labelled. This means that no new feature or change in functionality is required. The good news is, I found that these adaptations can, for the most part, be mostly visual. I was able to adapt them and address some of your thoughts around information density. I spent most of today taking a deep dive into features and sub-pages within uBlock Origin. How does the overview panel fits in there? I’m not sure if this will impact clarity, though! Instead of saying “Enter element zapper mode”, we may be able to say “Element zapper”. But a good alternative is to shorten some strings.įor example, instead of saying “Open the logger”, we may be able to say “Logger”. I’d advise limiting the amount of items in this category. Hopefully this can help rectify the language-fitting issue.įor icon + label items, the space is more limited, so they’re not as ‘stretchable’. Our text list items can scale up to 2–3–4 lines. I wonder whether the text will neatly fits for all languages such that the layout stays the same in all languages. I’d be happy to assist you in doing an audit of features that are okay to excise for mobile, but I must first confess that I’m not a domain expert! Generally, the more buttons we can take out, the less touch targets we’ll have per page. Maybe some buttons are not really needed on mobile?Īgreed. So glad to hear from you, and to have a chance to work together. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |