u/IzumiMiyamuraDev

Hi guys, MiyaDevs here. It's been a few days, but I have some new updates. First of all, I've now completed support for downloading tracks at the highest quality in Hi-Res Lossless, including lyrics and canvas. Another implementation completed is the songs recommendations based on the playlist content which are taken directly from Spotify, so we have the same songs recommendations that we would have on the Spotify app. Another new addition is the ability to search for an artist's concerts, complete with all the associated information such as ticket purchase details, location, lineup, etc. Then we also added the integration with the artists' official stores thanks to the Shopify API, thus showing the artist's official merchandise so you can buy it and support the artists. And lastly I studied how Spotify Codes work and I was able to decode Spotify Codes and now Soundlify can read them. Another major update is the addition of new Hi-Res music APIs that now allow the app to start songs almost instantly. And aside from that there have been some general improvements to the interface. I'm also working on a Discord channel where I hope to release a first Open Beta by the end of the month to do large-scale testing and identify any bugs or issues. That's all for now, I'm going back to work now. Byeeee!

(P.s There is more than one photo in the post)

Hey guys, MiyaDevs here, I'm posting this as a general update on the project's progress. Android Auto support is 80% complete! This version of Android Auto can now stream Hi-Res Lossless audio without any problems. And meanwhile, the import of playlists, artists and albums from Amazon Music has also been implemented, now by logging into your Amazon account via the Soundlify app You can choose which playlists, artists, and albums to transfer, and they will automatically transfer to your connected Spotify account by syncing to Soundlify. A bit like TuneMyMusic, but without the paid limitations, and you can also pass the official Amazon Music playlists that you follow. I also implemented song suggestions based on the songs in a playlist, using Spotify's direct API, and added audio previews to the edit playlist section. That's all for now. The project is progressing steadily, and I hope to publish it as soon as possible. I'm back to work now. Byeeee

Hi guys, MiyaDevs here, it's been a few days, but I have some news for you. The project is progressing with the implementation of all the sync features related to Spotify. Thanks to the study of the GraphQL API and the REST API I managed to have a very good synchronization for the modification of the playlists, with previews of up to 30 seconds of the song In the playlist editing screen, sync song positions, add and remove songs, and for the past 2 days also recommended songs based on the contents of the playlist. And in the meantime I'm also working on importing your library from third-party services like Amazon Music, Apple Music, Qobuz, etc... At the moment I'm testing the import of the library from Amazon Music, making sure that by logging into your Amazon account it automatically creates identical playlists on Spotify, Save all your favorite albums, artists, and more. And that's all for now, now I'm back to working on the project, I'll keep you updated, byeee

Hi guys, MiyaDevs here, it's been a while since I posted, but these days I've had a lot of personal commitments, but I'm slowly getting back to the project's progress. In the past 7 days, I've been working on implementing synchronized lyrics and test translation, and this is all possible thanks to the BetterLyrics project. So I want to thank the original creator and any collaborators for this wonderful project. And after much trial and error, I managed to integrate it into Soundlify, adding Apple Music-inspired graphics for the lyrics. So now many of the lyrics will not only be synced by phrase but even by syllable, in a karaoke-like style.Then I worked on solving problems regarding the waiting time for a song to play, and I'm slowly reducing the startup time more and more with excellent results. And while I'm here, I also want to talk about something. I've seen some people in the comments asking if there will ever be an iOS version. I'd love to create an iOS version in the future, but there's one small problem...I don't have a Mac...or even an iPhone. So I made the decision that if I see that the project is going to be really good, I will consider purchasing an Apple device to create an iOS version of the app. And who knows, maybe even a Desktop version for Windows, Mac and Linux distributions. But time will tell. That's all for today. I'll keep you updated. Byeeee

Hi everyone, MiyaDevs here. I’m writing this post to update you on the Soundlify project. Lately, I’ve been working on one of the app’s biggest issues: song matching. As many of you know, in FOSS music clients, when a song starts playing, it often plays an acoustic version or a cover instead of the original version. Additionally, with the Hi-Res Lossless APIs, there was a matching issue with songs whose titles weren’t in the Latin alphabet—for example, songs with titles in Japanese or Korean. Well, after four days, I’ve managed to achieve a practically perfect match, which I’m still testing. In the meantime, I’m also integrating and optimizing the lyrics page using projects like BetterLyrics, and I’m finishing up the Android Auto interface. Meanwhile, while I was in bed, I sketched out a mockup for the app and created the image you see above. That’s all for now, byeee

Hi guys, MiyaDevs here, bringing you new updates on the Soundlify project. I've managed to implement a lot of features these days, In fact, the Last.fm and Discord integrations are already working, as you can see in the images I'm attaching. Not only that, I also managed to get the Playlist Blend creation working via Spotify. Also currently in the works is importing playlists from music streaming services other than Spotify, such as Amazon Music, Apple Music, Qobuz, etc. And among the ideas for the future I also added the idea of creating the Soundlify Wrapped like Spotify at the end of the year. That's all for now. I'll keep you updated. Byeeee

Hi guys, it's MiyaDevs again, here to update you on the progress made on my Spotify-like FOSS music client project. In the last few days I've been able to implement Spotify Canvas and sync with Spotify for playlist imports and home screen, which will display all the Spotify-created playlists created for your account (for example, Daily Mixes). Additionally, after 3 days I managed to introduce the listening functionality via 16-bit Lossless Audio and 24-bit Hi-Res Lossless. Today, I started Android Auto support; it's still basic, but I'm working on it. And most importantly, I chose a name for the app, even if it's temporary (I don't know if I'll keep that one). And that's all for today, I'll keep you updated on the project... Soundlify (temporary name, maybe, you tell me). Bye

Hi guys, I'm MiyaDev, the guy who a few days ago published a post on the subreddit about a project that involves the creation of an app with a Spotify-like UI and the YT Music Backend. I'm making this post to let you know that I'm moving forward with the project. I'm attaching some screenshots of some beta screens that I'm slowly developing and improving. But I'm not just writing to inform you, but also to ask for your opinions. Last night I was looking into publishing the project on GitHub and encountered some obstacles. As you may know, there are many FOSS music clients with YT Music as a backend, but that's not the problem. The problem would be the similarity of this project to the real Spotify app. Obviously this app is a Spotify-like project so it has to resemble it, even if obviously it will have some things different to avoid running into copyright issues on icons, fonts, etc... Inquiring I saw that Spotify might require a take down of the repository for Trade dress, and because the app might "confuse the end user and make the user believe that that is the original Spotify". Now I ask you, are there any legal loopholes you think could be used? For example, by declaring in the app upon startup and also in the repository that this project is not Spotify and is not affiliated with it? I don't know, honestly I'm not a lawyer and above all I don't have enough experience in the open source world and GitHub to know. I will continue the project, both because I am passionate about it and because I would use it first, but I am hesitant about publishing it, and especially about the means of publication, since GitHub might take it down. So, that's all for now, let me know. Bye bye 😉

Hi, a few days ago I read a post from a user on this subreddit who was sharing an idea for a music client with a Spotify-like UI and a YT Music backend. Well, since I recently canceled my Spotify subscription and upgraded to YT Premium, I wanted to start this project, especially considering I'm an app developer. I've already started the basics of the project by implementing the main features and I've also started creating the graphics. It would be my first open-source project that I'd publish on GitHub, but I'm not 100% sure I want to continue it yet. So I decided to make this post to see if this project would actually be of interest. I'm attaching some photos of the beta interface of the app I've already created. What do you think? Should I continue? (The photos are in Italian, since I'm Italian, but I'm attaching them to give you an idea of ​​the project. If I were to actually continue it, I'd make the app multilingual by adding languages ​​like English, French, German, etc.)