8 ms·
That they can spend the time and effort to optimize each platform should surprise absolutely no one. The first point is that you're doing this anyway with an a
by matwood 14y ago
That they can spend the time and effort to optimize each platform should surprise absolutely no one.
The first point is that you're doing this anyway with an app that has any complexity. Each mobile browser and device has its own quirks. If you're going to spend optimization time for each device you might as well go native and make the most of that time.
That this tiny team of six developers that apparently needed to fracture to start building iOS, Android, etc, clients. It was utter insanity, and of course LinkedIn and Facebook both appeared as if they were the benchmarks we should follow ("See, they abandoned HTML! So should we").
Our first mobile app was native iOS and built by 3 of us in about 8 weeks. One of the team had some iOS experience at the time. I prototyped the Android version in a weekend and we had a releasable version ~6 weeks later with 2 of us working on it. Neither of us had any prior Android experience and that other guy had never done Java.
My point is that iOS/Android apps are not hard to build natively. That time spent means you can get the best the device can offer. Of course if you're only showing a simple web page opposed to an app then html5 may make more sense, but the discussion here is about apps.
- corresation 14y agoThe first point is that you're doing this anyway with an app that has any complexity. Enormously complex application with widgets, dynamic graphs, etc. Close to nothing had to be customized for those targets because it used standardization and shims where possible, and already was built to work across the major desktop platforms. I read this "you'll have to dramatically rewrite anyways" claim a lot and it simply doesn't ring true. My point is that iOS/Android apps are not hard to build natively. That time spent means you can get the best the device can offer. Is it possible for you to point to the app? I've done a significant amount of Android development (no iOS dev to this point) and my natural assumption is that a short effort app by people new to the platform would generally be terrible (which is sadly the case for most apps on the platform).