@3RaylFan posted:Here is an article that discusses why BlueRail develops on iOS, then ports to Android:
http://bluerailtrains.com/why-...ions-before-android/
There are 50,000 types of Android devices to support (many of them old and buggy) as opposed to 2 iOS devices (iPhone and iPad). When you make a bluetooth app for iOS you can develop all of your energy on getting the app functionality right. Once you release to Android, people expect it to run on 50,000 different types of devices, so you better be prepared to release lots of updates over the course of months to work around all the problems that arise on obscure poorly supported old devices.
You must be an Apple enthusiast. There's a whole lot of 'facts' based on here-say in your analysis. Have you built any apps yourself? Your argument reads like an emotional one, not a technical one.
It's true that it was once the case that builders started with the iOS but in today's world it's no longer typical to start there and then add Android later. Now, there's only one set of functionality, i.e., one set of functional code. Interface code is different as you would expect, but the core is not.
For most app builders it's too expensive, and much more time consuming, to do it the old way.
BlueRail apparently doesn't believe so however.
I wish them luck but I believe that most people in our hobby have Android phones. Maybe not all of us but most. We may not prefer them but they are more affordable, and on a budget in seriously bad inflationary times money is very, very important.
Generally we spend our big bucks instead on locomotives, and maybe rolling stock, a little track, and a power source, but not on anything else, especially phones.
Mike
