-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
My concern about media page #70
Comments
Additional improvement
|
I was the one who recommended that grouping layout , u are right I was only thinking about making it consistent with feed page i didnt think about that it needs to be different . I strongly support ur idea , I wish it came to my mind earlier , I made the dev to work he should not have done, sorry |
I agree with you , I have felt the need always , i had plan to make an issue about download button in bottom bar later . |
This is something that should be urgently done , I have always wanted it. And Google also recommended using 3-5 navigation buttons so it will also not violate this . |
"Use Download Page as a Bottom Navigation Bar Destination" is difficult to realize. This is because it is important to consider that opening an external magnet link should automatically jump to the appropriate tab, but the navigation component currently provided by Google may cause the home screen to be instantiated more than once, and this problem cannot be solved at the moment. |
Can we have sheet type external download handler , it will help us add downloads withought quitting our current activity or going inside the app saving time and not interpreting the current app thats running . and it should also handle "home screen to be instantiated more than once" better |
First of all, a great praise to the dev for making such a great app. This is one of the best app executions I have seen so far, and it has great potential to grow. I have been daily driving Tachiyomi and Aniyomi for the past 3 years, and I seriously think AniVu has the potential to surpass them and become my daily driver. However, I think the media library part of the app is going in the wrong direction, so I'm here to give my suggestions about it in early development before it goes horribly wrong.
So what is actually wrong
I installed the latest beta AniVu 1.1-beta53 and noticed the app media library has changed. In previous versions, it only displayed videos without any kind of categorization, but when I installed this version, it had a default "group" which I didn't have. With every brain cell in my head, it clicked right there that the media library is now going to look like the Feed page (I'm a big fan of the Feed page; whoever suggested that is a genius), but that is not ideal for a media page. The media page should never have that layout; that layout will only work on the Feed page. If you take a look at media library layout inspiration from the biggest rivals out there like Aniyomi, Tachiyomi, Jellyfin, Plex, and even official libraries like Netflix and Crunchyroll, you will understand why this is wrong.
You are probably thinking, after all that work you have done, am I telling you to just ignore all your hard work?
-> Heck no. It's just the group part that is wrong; everything except it is good, and I love and think it is suitable for a media library page.
What can be done
I will be honest - just remove groups for the media library as expandable cards. Cards are not an ideal form of separation in a media page. The media page should be more distinct and straightforward in what it contains. But I'm not telling you to completely remove the groups; you can keep them but in a better way. Use navigation groups as navigation tabs. MATERIAL.IO describes it well:
Tabs organize groups of related content that are at the same level of hierarchy.
Some popular examples of media library using tabs:
Aniyomi
Crunchyroll
Improvements over the current approach
Everything else is correct
I respect and like the choices made by the dev and all other contributors. Their work is commendable, and the app is shaping up to be a fantastic tool.
The text was updated successfully, but these errors were encountered: