The reality of HTML5 is that it is extremely processor intensive, radically different from mobile browser to mobile browser, and simply not supported at all on 4 of the 8 platforms I create for.
Building a XML-based object architecture and then interpreting it into ObjC and Java, then standardizing the data structure it accesses ends up being far better than hacking together a series of poorly performing HTML-based apps.
In short -- native is still best, by far. Put of the contents of an app itself in a standard database that all the native apps can access, to minimize your native code dev time.
I'm curious how you deploy to the non-smartphone devices with Unity, as it only has iOS and Android target support built in.
Do you use the output of some other target's build with your own glue libs for each supported device? Or are there Unity plugins for this kind of thing? Or is it some other kind of wizardry?
Building a XML-based object architecture and then interpreting it into ObjC and Java, then standardizing the data structure it accesses ends up being far better than hacking together a series of poorly performing HTML-based apps.
In short -- native is still best, by far. Put of the contents of an app itself in a standard database that all the native apps can access, to minimize your native code dev time.
Or just use Unity.