The documentation for the iOS Sdk is terrible. It's also in Obj-c. The Web API is pretty clear and we all love JSON. The only thing I could see myself using the iOS Sdk for is remote playing.
I think this conversation would best be continued by email, which is in my bio.
To answer your questions, I will be interning at a company starting January. I worked on this project for less than a month. Since I'm a 1st year in college, I also have my studies but I try to code at least 2 hours a day.
In that case, what license should I change to? As long as others who want to release an app based on my source code consults me about it, I will let them.
Thank you for the comment. I learned a few things about licensing. The main reason I chose GPL was because I don't want someone else building a commercial closed source application based on my app; others can still fork the project and modify it.
I don't intend to release this app on any other platform but others who want to may feel free - I think GPL allows for this. In the end, I don't really care what others do with my app as long as they consult me about what they want to do with it, which MIT is too loose for. If others want to release an app based on mine, they can feel free.
Right. Once again, never really thought of that. It could be a useful tool for others to learn off of: the app employs a MVVM and Coordinator architecture with reactive bindings. It's also a good example of using the Spotify Web API for Swift since there aren't many examples out there.
That was one of my intentions. I also started this project to learn more about reactive programming and exploring the technical sides of creating views in Swift.