-
Notifications
You must be signed in to change notification settings - Fork 126
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
Search redesign #616
Comments
|
I've added a mockup for Compact Results. I think it looks a lot more tidy, and it's more in line with what Spotify does. |
For the separator, I used the bullet • character from the Typography design tool. |
Thanks for working on this already! It looks good! I think I am more partial to having consistently sized search result (compact one). Not sure I would be able to provide a top result however (the API gives me results split up by artist/album/tracks/etc, I can't really know which one "scores higher" in relevancy across all categories). Oh and to give some more insight into what I had in mind for the filtering, here's what the initial search could look like (rough design in Workbench, don't pay attention to the sizes/fonts/spacings etc) : and upon "pinning" an artist, the results would be refined to include results relevant to that artist, while still allowing the same level of interaction with the artist card (ie you can still browse to the artist if you've filtered the search): (Oh and technical note: I don't think I'll ever implement that star everywhere in the app, at least not for tracks, as knowing whether something is liked of not requires a lot of requests to the Spotify API) |
Doesn't that make the current mockup hard to implement in general? How will you determine the order to put the results in if they are in one monolithic list? Will you iterate between artists, songs, albums and playlists consistently?
Ah, ok, makes sense. |
I can swap out the star symbol with a pin icon and create a new mockup for filtered search. |
that's... a good point ahah. I'll look more closely at the API to see if there's anything that would help. Otherwise I guess the results will appear in a consistent order which might not be so bad.
sure but take your time! I probably won't personally get started on this soon |
I have a few questions about this new search:
|
I’m not sure about this either. Might have to do another iteration on the design if @xou816 decides that it should follow how the API works. From a pure design perspective, I think ordering them arbitrarily works better because what people look for is always different, and can’t really be represented in a static order. We can allow filtering (playlists, songs, albums), etc. One possible way to order the results might be to fetch the play count of songs and albums, and the listeners/month for artists, and stack things this way? Is that possible? |
I am not a rust developer, however since there has been no progress on this issue as far as I know, I will give my two cents on this issue. Thanks to these lines of code, I am fairly certain that @xou816 uses the Spotify Web API (also because src/api/client.rs is an entire file that uses the isahc http client to do network requests to the In the Spotify Web API reference, I am still partial towards listing them separately, because I like the layout of the Spotify webapp search results. |
As discussed in #611, we want to give the search view new functionality and a facelift, making it more usable and beautiful.
The initial suggestions sound good to me! I'm a little unsure about the pinning feature, as you can e.g. easily search for "Beethoven symphony" if you're looking for all symphonies made by Beethoven anyways. Might be something I don't understand properly there, though, so I have created a mockup for that as well 😅
Initial mockup
Compact results
The text was updated successfully, but these errors were encountered: