Mobile releases are broken. But maybe they're fine?

You may not realize it, but mobile engineers are probably treated as second-class citizens within your org. This isn’t because your company thinks less of mobile engineers, it’s just that the complex, cumbersome tasks required to get an app shipped to customers are a huge time and resource sink that gets shrugged off by management because this is just how things work.

Is sticking with this status quo enough? It can’t be all that bad, right? It’s the status quo for a reason. It’s fine. Lots of teams get by doing things that are just fine. 

But the status quo actually is not enough and, in fact, it is not fine.

Mobile release processes aren’t necessarily completely broken, but for many teams release management exists somewhere on a continuum between ungovernable chaos to a frustrating annoyance. This is bad! Why is it bad? Because your org is: 

• Spending time and engineering resources on process instead of features   
• Relying on what could be a fragile Rube Goldberg release machine to get app updates out, risking delaying and breaking a significant number of your releases
• Putting extra stress on engineers to build and manage ever-changing, bespoke systems 
• Wrecking your developer experience all in the name of saving money, while simultaneously wasting significantly more money by shipping your app through a half-broken release process

Mobile releases are broken, but that’s probably fine... right? 

You may not realize it, but mobile engineers are probably treated as second-class citizens within your org. This isn’t because your company thinks less of mobile engineers, it’s just that the complex, cumbersome tasks required to get an app shipped to customers are a huge time and resource sink that gets shrugged off by management because this is just how things work.

Is sticking with this status quo enough? It can’t be all that bad, right? It’s the status quo for a reason. It’s fine. Lots of teams get by doing things that are just fine. 

But the status quo actually is not enough and, in fact, it is not fine. Mobile release processes aren’t necessarily completely broken, but for many teams release management exists somewhere on a continuum between ungovernable chaos to a frustrating annoyance. This is bad! Why is it bad? Read on to find out. 

Download the white paper

Please enter your email and we'll send it to your inbox.