Whereas I would ... and did
... use a cross-platform development tool,
. This enabled me to write and to maintain one
program, and to deploy it simultaneously to: Flash, Android, HTML5 and
the server-side pieces that all of these apps ultimately talked to. In the case of browser-based deployments, I also could remain blissfully unconcerned(!) about browser versions!
No, this isn't a silver-bullet (of course, nothing is ...)
. But all of us simply have to recognize that we can't afford to field two, three, four, or even five parallel development-teams, maintaining as-many source code bases (all different), in order to do what is ... for us and for our customers ... fundamentally "the same thing." We also can't try to shoehorn "a great big wad
of a tries-to-do everything language" (which is what Java is
and what Flash became
...) into all of these variously-shaped holes.
But what we can
do, and what haXe and a few other languages do,
is to write one source-code base in a strongly
-typed language that can on-the-fly transparently generate native
apps for all of the target platforms that we need to hit.
In the case of this project, one
source-code base generated all
of these apps and their various requisite components, and all of the deployments ran natively on their target platforms. In my opinion, none of them was a compromise. None of them looked as though they didn't belong.