This is an interestingly timed article. We're building our Android app right now, and its certainly more annoying than when we built out iOS app.
As an app developer, in Canada (not Canadian however) i'm excited that RIM have attempted to prevent further fragmentation by sticking close to the Android stack, however i really don't want to deal with the distribution and other issues (such as screens, OS bugs etc) that i'm sure will come with releasing on a 3rd platform.
I feel like we're dealing with the issues similar to what were encountered during the 17-1800's with different size railway tracks. Is it just a matter of time until we agree upon a standard?
> however i really don't want to deal with the distribution and other issues (such as screens, OS bugs etc) that i'm sure will come with releasing on a 3rd platform.
Is this better or worse than developing for a completely different platform (i.e. BB<10, WP7/8, etc)?
I think its better for sure, but i'm sure there will be bugs that only exist on Blackberry and those that only exist on Android. I suspect that eventually we would (will...) end up with two builds anyway.
Overhead, it would be great if Blackberry could just start making Android phones...
As an app developer, in Canada (not Canadian however) i'm excited that RIM have attempted to prevent further fragmentation by sticking close to the Android stack, however i really don't want to deal with the distribution and other issues (such as screens, OS bugs etc) that i'm sure will come with releasing on a 3rd platform.
I feel like we're dealing with the issues similar to what were encountered during the 17-1800's with different size railway tracks. Is it just a matter of time until we agree upon a standard?