samyndriss

Oh no! Sorry to hear that! Is this happening even after selecting your genre filters?

Thanks for your feedback! Hmm, that is odd that it's making those suggestions for you. We received the opposite feedback which we were looking to include in a latter release - currently, the search doesn't leverage locale to carry out the search.

Thank you so much for your feedback! I really appreciate it!

And thanks for letting me know about the go back button. It should "rewind"/show you the last disliked/skipped track assuming at least one track has been disliked/skip.

Can you please let me know what browser you are using and if you are coming in on mobile/web. I will take a look and see what the issue could be.

Happy discovering! :)

Thank you for your feedback! Will take this on board! If I've understood correctly:

1) The tracks that are presented to you should be a mixed bag based on your preferences? Currently the application showcases 50 random tracks for ONE genre at a time.

2) The mixed bag of tracks should also provide you with some tracks that are outside of the genre/year preferences you have specified?

Just wanted to circle back, the massive logo issue on FF's been resolved :)

Issues' been resolved. Thanks again for brining this up.

Thank you for bringing this up. This has been mentioned in another thread as well - I have created an issue and will be looking into this.

Sorry about that. This is the case even after setting the genre/year preferences in the sidebar?

Many thanks! And really appreciate your feedback. This is indeed a challenging proposition but I really like the idea.

If I've understood correctly:

1. Assuming, your filter is set to ["country", "latin"], you would like the application to "take the hint" (for lack of a better expression) as you are disliking a certain genre (let's say country) and provide results that do not include the genre you're not in the mood for.

2. Further, you would like to have the results mixed i.e. currently, it provides you 50 tracks of a specific genre at a time.

3. Finally, you would like an option for "keeping a track on ice", that is, I don't want to listen to this right now but might later so don't completely eliminate it from the poll of options.

Thank you! Appreciate your feedback. I agree, the filtering piece is non-existant in its current state. Ultimately it's a client side application and there's no server component except to handle the OAuth flow. Per Spotify T&C I can't store user data so won't be able to track your likes/dislikes per se.

That said, I will file an issue and definitely look to add some "smarter" filtering client side within the current session so you're not seeing the same tracks again, as this issue has popped up on an other thread.

Thank you! Oh wow, I did not realize it was not working on Firefox. I will definitely take a look at this. Thank you for bringing this up!

Thank you! I'm assuming you're coming from iOS correct?

Unfortunately, Apple disables the html <audio> autoplay field. Ultimately a business decision (some context on this here: https://stackoverflow.com/questions/3009888/autoplay-audio-f...).

This is why there is a play button for each track, I'm afraid :( Should that change, I will push an update. That said, autoplay is enabled and works for Desktop web as well as non-ios devices (as far as I'm aware see https://caniuse.com/?search=autoplay).

Agreed. The rational was not to "pollute" Spotify with a bunch of public Trackafind playlists. But I've received this feedback elsewhere. Plan is to add flexibility to make the playlist private/public cause I've received feedback for wanting that ability. Alternatively, drop the private scope altogether and have all playlists public by default.

Edit: it needs the create, edit permissions to create the Trackafind playlist and add tracks to it. The follow just comes as part of that auth scope.

Thank you for your comment. And I understand the concern. Will be opening up the code once I finish refactoring and do some code clean up. I'll take a look at the login button issue. Do you happen to know what your devices' screen dimensions are?

Hello HN!

My partner and I built out a web app (mobile responsive) that integrates with Spotify API. They designed the UI, I built out the front end. Long story short, just as the title suggests, it's a tool that helps you discover new tracks on Spotify by way of swipe cards.

Built using the good ole' front end fundamentals: HTML, CSS, JS using Next.js deployed on Vercel.

Please feel free to provide feedback, happy to take anything on board. Happy discovering y'all!

Note this app will always be free (i.e. no ads, no user data collection, no payment walls) and I'm just happy my partner and I were able to deliver something that hopefully will help others discover music and have fun along the way .