4 ms·
> If you're only targeting iOS and nothing else, then I would agree with you. That's becoming outdated. We've got a native iOS app and we're doing the Android
by erichocean 13y ago
> If you're only targeting iOS and nothing else, then I would agree with you.
That's becoming outdated. We've got a native iOS app and we're doing the Android port with Apportable, which provides native iOS APIs and features on Android. The dev version (which we're using) implements its own Core Animation subsystem on top of OpenGL ES 2.
It's not perfect, but it's a hell of a lot better than maintaing two separate codebases and it's far easier to fix whatever platform issues there are than the equivalent "long tail of details" you encounter working with web views.
- marknutter 13y agoCool, so that covers iOS and Android (with its own long tail I'm sure). You still have Web and Windows mobile to worry about assuming that platform continues to gain popularity.
- alttab 13y agoOnly Microsoft is worrying about Windows Phone.
- erichocean 13y agoApportable could be ported to run on Windows Phone, there just hasn't been any interest (or so I'm told). Much of it could also run via NaCl as a Chrome Packaged App, including the UI stuff. That's a much bigger change though, since you'd be supporting mouse events, not touch. But it's still doable.