If you’ve been following us, you might have noticed that we are a developer-led team. As such, we put a high emphasis on tech. We are proud of the fact that we support both Android and iOS. It is a badge of honor.
The case for 2 codebases
Having both Android and iOS available allows us to tap into a larger base of users. It gives us the reach needed to grow our community. As a product with international aspiration, all the shoes fit.
Then why stop?
Although it is fun to support 99.999% of users, we are only 2 guys. The more we stretch our resources, the more mediocre our app becomes.
Each codebase is an average of our efforts
Switching between iOS/Swift and Android/Kotlin is exhausting. They may have their similarities, but Apple and Google have very different philosophies when it comes to an ecosystem (differences that warrant a blog post all on their own).
We are always experimenting with new features, switching and trying until we find what our users like. With 2 codebases, we’d have to program each feature twice. This means twice the wasted work when we move on. This means we’re twice as slow. This means something has to change.
So why not iOS?
Through doing a lot of field work and cold approaches, we found that for every 10 users we approach, only 2 are on Android. From a developer perspective, the iOS environment allows for much more rapid prototyping. The workflow and aesthetic of Xcode simply works better.
Plus, sometimes Android Studio can be… difficult
Perfecting what we have
So yes, we are halting production for Android at the moment. No we have not forsaken our Android users for good. We are simply taking a hiatus to give our codebase the attention it really needs. Once we’ve found the core set of features that our users really love, we’d once again revisit Android to maximize our reach.
Sometimes you have to prune away the dead branches for a tree to grow.