Could you share any evidence that would demonstrate the productivity, quality of work, or impact of the engagement?
With the custom app, we weren’t making any changes unless there would be a crash or we needed an operating system update. The V4 platform allows us to stay on the curve. iOS came up with a new version, which caused our app to malfunction. If we’d been managing it ourselves, we would have gone into crisis mode and worked with jācapps’ developer to get it back up. We would have probably been competing for attention with all their other clients. The V4 platform supports a sweeping improvement from which all users can benefit.
We are sometimes inhibited from making custom changes like branding elements and stylistic details. The main reason people open the app is to stream our content, but the player does not have very robust functionalities. One thing we are lacking, compared to the original app, is the ability to see what’s playing at the moment. We would like the ability to upload an XML file with this information or use products like NPR’s Composer. There are some challenges which we can’t work around without hiring developers.
We track crashes for Apple devices, which are a bit more frequent—about 60 per month, compared to 2 per month on Android. We have around 2,500 users on iOS.
How did jācapps perform from a project management standpoint?
jācapps’ team is very helpful. I’ve worked with 3 different customer reps since the beginning, and each has been very responsive. We’ve reinstated our fiduciary, which involves certain procedures for updating the application. jācapps has been more than willing to be flexible, and they’ve always gotten clarification on our needs and requirements.
What did you find most impressive about jācapps?
Their responsiveness is key. On some occasions, we had podcast launches that needed to be uploaded to the app but only made visible at a certain date. jācapps had no problem assisting us, and they’ve been accessible overall.
We would appreciate having our own CMS for making changes to the app’s content in terms of links, RSS feeds, and so on. Even without this ability, it’s easy to work with jācapps.
Are there any areas jācapps could improve?
The aesthetics and some user functionalities on the app could be improved. We would like having a static player while navigating through the app, which would show users what they’re listening to. Listening is our main function, and the app’s functionalities tend to be a bit clunky and basic. I would also like the ability to like and share content on the app.
What tips or recommendations could you share that might increase the likelihood of success with jācapps?
A lean organization that doesn’t have development as a part of its core services will benefit from jācapps’ product. We don’t necessarily need the knowledge for building and maintaining it and can focus on managing the content.