We know the frustration as an Android user that many apps are released on the iOS platform before they are released on the Android platform. We are seeking to minimize that frustration for asensei customers.
We made the same decision to launch on iOS first, so that we can focus on getting the product experience right and bring a variety of coaching programs to our first customers.
Would be interested in helping to Beta test the Android app when it does become available? If you sign up at www.asensei.com/android you'll be notified as soon as we release our Android build of the app. The more signups we get, the quicker we'll likely do so.
One option in the meantime - the asensei app will work on almost any recent iOS device, iPhone, iPad, iPod touch, so if you happen to have access to an older device it may well work with our app. You can also purchase a secondhand/reconditioned iPad -- all asensei requires is that it supports Bluetooth 4.0. You can find a list of such models here - https://www.iphonefaq.org/archives/973945
So when are you going to release the Android app?
tl;dr - as soon as we can, and as soon as we can't not.
Our approach to product development, and feature prioritization in general, is to be pulled by our customers. The more Android customers sitting on our waitlist for beta, the more urgency we're going to feel.
So if you want to accelerate the release of the Android app, you can help us by inviting others to sign up for asensei on Android and share this link with them: www.asensei.com/android
I'm curious, why don't you develop for Android and iPhone at the same time? More people?
Since you asked...
Product engineering is all about trade-offs, and one of those trade offs is how can you get your product into the hands of enough customers, quickly enough, to get the feedback we need to make the product one you can't believe you used to practice without.
A hard, but easy decision is to start by only developing for one platform. Rather than spend twice the time designing, twice the time coding, twice the time testing and twice the time maintaining and supporting a set of features, it's ultimately quicker to build the right product for everyone across all platforms, if we launch to a single platform where many but not all of our customers are.
And while it's true that there are technologies and approaches that make it easier to develop at the same time on multiple platforms at once, there's a tremendous amount of complexity to asensei in how we connect to sensors on rowing machines, and how we connect to sensors in forthcoming smart apparel, that isn't so easy to develop for multiple platforms at once.
We appreciate how keen you are to try asensei, and wish we could have targeted all rowing machines and phones at once.