Skip to content
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

Use Download Page as a Bottom Navigation Bar Destination #87

Open
onnesoom opened this issue Aug 14, 2024 · 4 comments
Open

Use Download Page as a Bottom Navigation Bar Destination #87

onnesoom opened this issue Aug 14, 2024 · 4 comments

Comments

@onnesoom
Copy link

onnesoom commented Aug 14, 2024

  • There are times when I add a download from the feed page and want to go directly to the download section, but I need to go to the media page first, which is inconvenient.
  • In the latest beta, the position for accessing the download section changed from a FAB (Floating Action Button) in the media page, but the issue remains. I still need to go to the media page first.
  • The media page should be focused solely on media content without any distractions.

Use Download Page as a Bottom Navigation Bar Destination

  • The download page satisfies the material.io guideline: Navigation bars should be used for: Top-level destinations that need to be accessible from anywhere in the app.
  • Additionally, it would be a more user-friendly position since the app is focused on downloading media. The optimal layout would include a feed section (already available), a media section (already available), a download section (moved from the media page to the navigation bar), and a more options/settings section (already available).

Example: Cloudstream (One of the biggest apps to download and stream media)

cloudstream example 1 cloudstream example 2

Example: Ketsu (iOS)

Ketsu example 1 Ketsu example 2

Many more apps utilize quick access to the download page, saving users time and clicks.

Feedback on the New FAB Button in the Media Page

The media page now has a new FAB (edit button), which I don't think is a good choice for a FAB. The action can be easily triggered by long-pressing any entry, and the edit button is not something users will frequently use. I suggest using a resume/play button instead of the edit button as the FAB. This will help users continue from the last played media and will be used more frequently.

Top Bar Buttons

Currently, the media page top bar has a refresh button and a download page button (which should be moved to the navigation bar). The refresh button is fine, but the download button should be replaced with a files button, allowing users to navigate to media files outside of the Anivu folder. Additionally, a search button to search for global media (both in the Anivu folder and on the device) should be added.

Originally posted by @onnesoom in #70 (comment)

@Buxuna
Copy link

Buxuna commented Aug 14, 2024

I didnt notice this before , but since i did ->
I completely agree with the points raised in the feature request. I've had some of the same problems with needing to go to the media page first before accessing the downloads, which is inconvenient. Moving the download section to the Bottom Navigation Bar would be much more user-friendly and accessible. This change would really improve the experience for those of us who use the app primarily for downloading media. I’d love to see this implemented!

@onnesoom
Copy link
Author

Res This doesnt solve the problem we still have to go to more to acces downloads , what i proposed is the downloads as a direct acces , just like feed,media etc . please consider this -> thi will help me reduse a lot of steps . i download so many torrents everyday and seed then , for managing then the position of downloads is very inconvenient now

@Buxuna
Copy link

Buxuna commented Aug 17, 2024 via email

@SkyD666
Copy link
Owner

SkyD666 commented Aug 17, 2024

#70 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants