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

How to organize the new homepage? #362

Open
lGuillaume124 opened this issue Feb 2, 2019 · 8 comments
Open

How to organize the new homepage? #362

lGuillaume124 opened this issue Feb 2, 2019 · 8 comments

Comments

@lGuillaume124
Copy link
Contributor

The next major release of Sonerezh (2.0.0) will offer a lot of new possibilities to implement new features, and I would like to refactor the home page (the page where you are redirected to once you're logged in) for Sonerezh 2.1.0.

By now this page only displays a list of songs but it is unusable when you have hundreds (or thousands) of tracks in your collection…

In place, I think we could have a page with data related to the current user:

  • A block with his playlists
  • A block with the last played song
  • A block with the more listen songs, albums or bands
  • Maybe custom settings?
  • etc

Feel free to propose your ideas and I'll try to implement the best of them for Sonerezh 2.1 or 2.2. :)

@MightyCreak
Copy link
Contributor

Personally I'm only on the album page, but it's not perfect for two reasons:

  • It doesn't load all the albums, so every time I load this page, I scroll all the way down in order to load all of them.
  • When searching something, it brings me to another page. I would have preferred to simply filter the album page in real time.

I know this is not very scalable since loading all the albums could be very long in huge DB, but I hope it can give you some ideas.

@Nizhile
Copy link
Contributor

Nizhile commented Feb 5, 2019

How about this kind of home page? The last imports are taken from album, and the last tracks played by the user from a stat/log table. The main motivation is that using smartphone browser, the two blocks seems to remain valuable for the user.
image
Note: I currently add the Played table to a dev instance, but failed to populate the table as using SongController.download() is not the right place after all.

@fcharlier
Copy link
Contributor

When using Sonerezh, I mostly use:

  • the "recently added albums" list from the albums (which size I increased to show ~60 recently added albums).
  • the search which works well.

I find the artists page is useless without at least a way to filter artists by the first letter (or a quick filter textbox).

I like @Nizhile idea to have recently added/played items on a user homepage.

@Nizhile
Copy link
Contributor

Nizhile commented Feb 7, 2019

I like @Nizhile idea to have recently added/played items on a user homepage.

@fcharlier , if you're a bit adventurous, you can use this patch on a clean 1.2.5 install. It works only with Mysql database.

Note that once patched, you need to use Console/cake schema update SonerezhMysql to create the new table.

This patch replaces the list of all songs by the list of latest five songs played. Hence users will at first have an empty homepage.

Note also that there is no limit on the played table: if you have a lot of users, it might become very big without any mechanism to purge it. Moreover, the request to the database is rather not optimal.

@Nizhile
Copy link
Contributor

Nizhile commented Feb 8, 2019

If you want to get a feel of what last imported albums looks like on home page, you can use this patch on a clean 1.2.5 install.

Note that the patch currently remove pagination on the songs list: only the first page will be available.
Anyway, clicking a song in the list will add all songs to the queue; clicking on a song in an album will replace the queue by this album (the same as in album page).

WARNING If you use it with the patch from my previous comment you will probably mess up your sonerezh install (files index.ctp and SongsController.php).

@MightyCreak
Copy link
Contributor

I like the Spotify/Deezer UX. Everything is in one page.

In Sonerezh, we could remove all the pages and, by default display the most played songs/albums, have a list of a few albums that weren't listened that much (maybe a random of 5 albums in the lower 10% albums).

Then a menu on the left that allows to efficiently search for anything (song, artist, album), as well as all the playlists created.

@techexo
Copy link

techexo commented Mar 8, 2019

Hi, I'm glad to see that there is some discussions about what's missing or what's weird on Sonerezh 👍!
To add my two cents:

  • as mentioned by @fcharlier, the Artists page is useless in it's current implementation. IMHO, a two page interface (one with all the artists, then clicking on one displays its album(s)) or a way to jump directly to the first letter of the artist (with nice ABCDEF....XYZ links at the top of the page, foe example) is mandatory to make this page usable;
  • the same "jump links" could be added to the albums page;
  • I would indeed like to see on the home page:
    • my last played playlists;
    • the most listened tracks and/or albums.

Anyway, great soft and keep up the good work 😄

@manichardtiger
Copy link

Most listened songs or bands would be nice, but to be honest, on of the best features of the gui is its lovely simplicity
I really enjoy simply logging in, clicking random playback, selecting one of the first songs and then just following the dynamic playlist that is created from ALL your songs

No other player really does this.

I would suggest a filtering of sorts in the Artists and Albums pages as noted by MightyCreak above.
A nice feature would be a button that takes you to the currently playing track, as sometimes you can really get lost in the playlist viewer
Also, maybe the ability to selectively remove items from the playlist viewer?

Maybe the playlist viewer could be a more integral part of the first screen?

keep up the good work :)

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

No branches or pull requests

6 participants