2 ms·
I think a lot of this comes down to exactly what you're doing. For instance, if you're doing networking, getting fancy with the camera, or doing even slightly l
by rsynnott 12y ago
I think a lot of this comes down to exactly what you're doing. For instance, if you're doing networking, getting fancy with the camera, or doing even slightly low-level OpenGL stuff, Android's likely to be more painful, especially in terms of testing, and old-version quirks.
Fun minor example; before Android 4.3 or so (and only about 25% of Android users are on >=4.3), if, using the default HTTP library, you make a request to a server that uses HTTP compression, and the request returns a successful no-content result, like 204, that'll trigger a null pointer exception in the guts of the HTTP library. There are lots of these quirks; by themselves they're minor, but they build up.
With things like the camera, it's worse, as vendor customisation comes into play.
- BugBrother 12y agoBut if you're not doing anything fancy, wouldn't a JavaScript variant be better? [E.g. potentially X-platform.]
- rsynnott 12y agoI've yet to use a mobile web app (or phonegap thing, etc) which didn't make me want to tear my hair out. I mean, it may be possible to make such a thing, but people generally don't.