How our app release process works

Reply
6 people liked this

How our app release process works

Community Manager
Community Manager

Our product owners have been reading your feedback here in the Community and in our Beta boards. In doing so they've realized there's quite a few questions from you all about how our release process works. One of our POs @henka has drafted this post for you all to help outline our process at Spotify and hopefully answer some questions you all might have. 

 

Hello,

 

We’d like to quickly introduce you to how we deliver our Spotify client software and experience to you. There are key three points we’d like to share:

 

1. Releases are time-based, rather than content-based

 

Instead of delivering a fixed set of improvements and cutting the release when all the content criteria have been met, we generally deliver on a fixed schedule. This schedule is currently two weeks.

 

What this means is that with every release, in addition to all the issues that get fixed in that two week duration, you will also get whatever feature set improvements we can deliver to the deadline.



2. New features are rolled out incrementally

 

So, while we do deliver new features and improvements with most client releases, some users will experience new features in Spotify quicker than others. This is because most of the feature set can be controlled from within the Spotify service itself. We call this incremental or gradual rollout and this is a means for us to make sure that the new features are of top-notch quality when they are shipped to all users.



3. We do A/B tests.

 

At Spotify, we commonly employ a technique called A/B testing to try out tweaks to our product. The point of A/B testing is to ship a particular change to a small enough test group and then evaluate performance against a control group.

 

If the A/B test is successful, with respect to the metrics important to that specific test, we may opt to roll out the change to the full user base.

 

If the A/B test is unsuccessful, we will most likely not pursue that change any further. This is why sometimes you’ll have a friend with a feature that hasn’t reached you yet. Users can also reach out to us if they would like to be removed from a specific A/B test at any time. 

 

Regards,

Henrik Österdahl Djurfelter

14 Replies
8 people liked this

Re: How our app release process works

Webbyrealist
Casual Listener
Why has Spotify gone utter **bleep**?? Nothing works? Can't shuffle and when you take off shuffle it plays from the top !! I want my money back so I can go to iTunes !!!! Your rubbish now
2 people liked this

Re: How our app release process works

Leonardo121
Newbie
Hi

Re: How our app release process works

bzysko
Newbie
Its prety nice isnr it

Re: How our app release process works

didneydallas
Casual Listener
 
3 people liked this

Re: How our app release process works

PJEC
Roadie

Spotify should really allow people to opt out of A/B testing. A lot of people lost their cool over the testing of the (removal of) the notification bell.

Re: How our app release process works

Caleve
Newbie
Would like to save the song More by Silk and can't find it anymore. It's off my playlist.

Re: How our app release process works

user-removed
Not applicable
I would like to have the bottom Navigation bar at iOS rather than the **bleep**ty hamburger design...
4 people liked this

Re: How our app release process works

properwicked
Casual Listener

Same! I'm really sick of not having that update rolled out to the masses. It's been a month already.

2 people liked this

Re: How our app release process works

twinlight
Casual Listener

Yeah this is **bleep**. I read about the navigation bar over a month ago, or is it even two months ago now maybe. Yet I have the hamburger **bleep**. Its really hard navigating. 

 

But I guess since we dont have landscape view yet its not a priority to roll out features for iOS anymore. Landscape has only been available for two years now on the phone..

SUGGESTED POSTS