2 ms·
> Additionally, the idea that you can "write once, deploy everywhere" is ludicrous. It has been disproved time and time again, as the market chooses native apps
by untog 15y ago
> Additionally, the idea that you can "write once, deploy everywhere" is ludicrous. It has been disproved time and time again, as the market chooses native apps over apps that have been crippled to the lower-common-denominator of the range of platforms it supports.
I'd argue that it has been disproved time and time again because it hasn't been done right. The ideal is native UI with platform independent backends. I get that Android and iOS have different UI paradigms, but what's going on behind the scenes is exactly the same in a lot of cases.
Appcelerator sort of provides that, but last time I tried it, it made huge bloated apps. Not good.
- nupark2 15y ago> I get that Android and iOS have different UI paradigms, but what's going on behind the scenes is exactly the same in a lot of cases. Sure, it's the same, if you call being turing complete the same.
- SeoxyS 15y agoThe traditional way of doing that has been to write a low-level C library with the core functionality, and write a native app for each platform that leverages the library. This is how the best cross-platform apps are made. I can see a bright future tho in JavaScript-based game engines, so long as they're wrapped in a native app (written by a developer, not generated by an SDK).