ResearchKit VS Spotify

Might want to check out ResearchKit. I haven't used it, but it does support bars and graphs

It was inspired by ResearchKit Surveys on iOS and allows you to create many types of surveys. You can check them in the really good comprehensive documentation with examples.

Requirements (please don't apply if you don't have this experience): -Must have developed an iOS app that uses the Spotify API/SDK (https://github.com/spotify/ios-sdk) for playing Spotify music and have fixed this particular "Lock Screen" issue.

We're looking for an iOS Developer that has experience with using Spotify API/SDK (https://github.com/spotify/ios-sdk) to play/access Spotify music on the app. This is a part-time/contract role.

I did my best to not make this post one long rant so I'll say this about the whole situation: I think that the way Spotify handled this whole situation is embarrassing and totally hostile towards us, developers. They only gave us one and a half months of notice about the change, they purposefully ignore any discussion about this change on their own forums, they left us with half-working SDK which is poorly documented and which could potentially break with new updates to Spotify and has over 170 open issues on Github, which mostly have not been addressed in any way by Spotify staff. We basically have to figure everything out by ourselves.

They advise developers to start using the "modern" SDK but unfortunately in its current state it is not a viable replacement for the tools we've been using for years. It offers no direct access to music stream which is a dealbreaker for apps offering any kind of EQ or apps which want to enhance the playback in any way, for example mix with other sounds. It also has a lot of issues on its own, for example it requires the Spotify app to be always running in the background which forces user to having to switch between the two apps constantly to keep the connection alive. On Github there are currently more 170 open issues and only few have been addressed by Spotify staff in any way. Most problems are being figured out by the community itself because the official documentation covers only the basics and doesn't provide any help when dealing with errors, which as I said appear very common when using the "modern" SDK.