Reply to thread

Message: <blockquote data-quote="Scythe42" data-source="post: 1105239" data-attributes="member: 95833">Got you, a classic "Textbar" at the top screen location, where you can filter different categories. When you select them the below details automatically update.I see that makes sense for touch usage as well. Though if automatically update on selection makes sense or something like an "OK" is required to change where you are has to be prototypes, which in the end actually feel better. Both are viable options.Popout Windows (aka Hamburger Menu you know from phones) should be avoided as much as possible in general, they are just horrible in any usage context. Sure an option for usage with only cursor keys, as there cannot be much done.So we already have small usage difference between touch and remote. For Touch you really have to touch it, for remote usage a simple selection should be enough.Such navigation details on different forms of input have to be prototypes, no other way to actually find out what feels the most natural. No, not a ton of options because we cannot decide. That is never a good way to do things.Various animations are of course needed to show a selection to give a user feedback where he is or what is about to happen.Like that in general. It takes the classical StreamedMP approach for a large menu bar, but it will not wrap around, nor is the information displayed only a fanart. Means we are leveraging the screen estate.Classic remote as well as touch interface can leverage the same way of filtering content.Instead of a fanart actual content is displayed based on the selection. The details of selections of course have to be tested what works best in the long run.I like that so far.A navigation like top bar doesn't have to be text. Icons can as well be used. With PSD mockups alone you can play around a lot just with the top bar.So far we have for ideas:- Non wrapping consistent navigation bar and dynamical update of related content that can be used for remote as well as for touch interfaces <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up    (y)" loading="lazy" data-shortname="(y)" />Let's stay with the navigation bar for a moment.What do we actually need inside it? We need to get our categories down next and these should have extensibility in mind as well. Sure, can be flexible, what will we give users as well. There should be hardly any need to change it for mosts users ever.This brings us directly to a related topic: What content filtering categories do we actual need? How far can we reduce it?</blockquote>

Verification