Managing an app, after it is first ready for release, is like fighting a dragon that gets stronger every time you attack it. It’s really just the beginning of a list of repetitive tasks that keeps getting longer and longer.

Development environments are not suited to managing these tasks. Developers are therefore forced to step outside of their familiar environment to tackle this growing list of tasks.

Don’t go out there alone!

Here be dragons!

Outside of the safe, familiar confines of the development environment, exists a dangerous and unpredictable world. You don’t want to find yourself out there unprepared! … (hang in there for the good news below 🤓👍)

There are many common set-up and repetitive tasks involved in delivering a mobile app. Every developer goes thru some variation of a core set of tasks. It’s almost like a rite of passage.

No matter if you are a native or hybrid developer, we all have to create screenshots, deal with signing, upload to one, or the other, or both, Apple and Google stores and navigate each store’s respective beta testing and release tracks… And that’s like the minimum number of tasks.

For the more adventurous, there are tasks related to unit tests, integration tests, regression testing, beta testing, A/B tests, monitoring/analytics… the list goes on.

Then there are tasks related to new features, bug fixing, repeated uploads to beta testers and releases to users, and version control of the resulting source code.

It’s like a snake eating it’s own tail!

Then there are the native platform-specific versions of these tasks (which is especially relevant to native developers).

Add to that the fact that each of these tasks often cascade into other tasks and inter-relate in sometimes unanticipated ways.

Before you know it, the tasks look endless.

There’s no avoiding it.