-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion] UI Overhaul #1950
Comments
I hate hiding shit in dropdowns. Why hide it when you have more than enough space to show it right there? Anyways that's just my opinion you can do whatever the maintainers want. |
I agree with you that there's definitely enough space to omit the dropdown. However, the main reason for using one is not to conserve space but rather to categorize the elements and in turn inform the end user of its functionality. While some people would be able to infer the functionality based on terms like "newest" or "oldest", others can not. In order to increase the general privacy of everyone Invidious has to be able to appeal to these clueless and tech illiterate users. This means that we have to label almost everything. For a horizontal design like the prototype I have above, its rather difficult to do so. Here's some low effort mark ups as an example.
1
2 3 All of these look rather ugly. I'm no way skilled in UI design but I feel like no matter what we do it'll look roughly the same. Using a dropdown menu is just easier. |
I'd have to disagree here. Both of the two inline mockups look decent and explain their function well. |
this looks like a broad enough topic, to perhaps also add a request to add a separate button (perhaps a 'search' lens icon) next to the search field. It will help with devices where one needs to press select to activate the text field to enter search term but that button is also used to send a Return. so trying to press that again, to execute the search, just activates the text input again. Just a small request. |
Looks like the dropdown issue is settled then. I'll go ahead and include an inline label for them.
Like this? Not sure how I can implement the second part of your request though. |
Any objections to moving the channel description information to a dedicated about page? |
|
is this because currently it pushes down the videos much further? any other reason to move it? |
Yes: IME the description is usually short/one line long, so that would just If the problem is with lengthy descriptions (e.g.: longer than 5 or 10 lines), But regardless of the default channel page, I would still like to see the an
|
I like having the entire description on the channel page as things are now, including when the descriptions are long (example). When I'm evaluating whether I'm interested in an unfamiliar channel, I find it convenient to have all of that information on the same page as the video listing. I'd prefer that the description just be there without my having to click an extra button or hover over something. |
Pretty much. I personally find it annoying having to scroll down so much in order to find the contents on Mobile though it seems like the consensus here is that nobody wants to move it. |
maybe collapsing it like the filters in search page, could be an option. maybe about can show say one line of text and then have a Read more or Show more. or have a jump link to jump to the videos section. |
My bad, I didn't consider mobile.
Either of these sounds fine. If @syeopite goes for the former, I assume the entire channel description will already be preloaded (as opposed to being loaded on-demand the way comment replies on video pages are). |
@syeopite commented 7 hours ago:
@dentistformyeye commented 2 hour ago:
I had not considered mobile either (I usually use NewPipe for that) and I agree The simplest way might be to put the description inside There appears to be no way to do that with css[1], so the page would have to be If that's not feasible, the next best thing would probably be to either hide it Nice. By the way, how did you get the icons in the upper right corner to show |
Apologies for the late reply everyone! I got slightly sidetracked with implementing another tab (see below).
Certainly, though imho it looks a bit odd having it appear in two places at once; especially with them being so close to each other. I'll recommend we remove the upper description when a user is on the about page. Something along the lines of this:
Yeah that's probably the only option we can actually do here. I'll go ahead and put that on the todo list. In other news I've implemented full support for featured channels. The details box is mainly there to allow for easier scrolling on channels that feature massive amounts of other channels. Any thoughts about the design? |
Most likely just this discussion. The PR is also unlikely to be finished anytime soon since I have way too many plans for it. Plus, this PR uses #1920 and #1985 so those would have to be merged before this one as well. If you'd like I could just go ahead and make a quick PR for just that.
Yep! |
I am fine with waiting for it to get done in this PR. Lots of new stuff and concepts to learn here for me. I just know I will be using the search much more from my firetv once this is available. 😁 |
This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked. |
I think the current user interface could use some improvements. Here's some of the ideas I've been playing around with.
Stacked hyperlinks should be replaced with pure css menus instead. This would have the advantage of making them look more like tabs as well.
Trending
Anything related to sorting could be condensed into a dropdown menu.
Channels
For the filters box perhaps we should change it to be more like Youtube.
Example 1
Or maybe just the normal detail widget.
Example 2
Either way the looks of the frontend needs to be improved. Any particular thoughts or ideas about this?
The text was updated successfully, but these errors were encountered: