3 ms·
I don't understand where there is confusion: mobile website = run in mobile safari, assets loaded over http hybrid app = run in a webview, most assets stored
by thatthatis 13y ago
I don't understand where there is confusion:
mobile website = run in mobile safari, assets loaded over http
hybrid app = run in a webview, most assets stored locally, some data optionally loaded over http
native app = written in the officially supported language of the platform
- yesimahuman 13y agoWell, what was Facebook back when it used HTML5 in the news feed? The lines are blurring quite a bit. Just because you are abstracting one part of the app to the browser runtime (that can still easily access the native layer) doesn't change the fact that you are shipping a native binary at the end of the day. We have decided to go with Hybrid since it is causing confusion, but I disagree it's so cut and dry.
- thatthatis 13y agoA quick perusal of the comments here makes me think that the issue is more cut and dried than you'd like it to be. What _should_ the terms mean is a very different question than what _do_ the terms mean. As far as end users are concerned there are only two categories: native and mobile websites (though they're more likely to describe them as "apps" and "websites"). Hybrid is a term used by developers to communicate a particular technology stack, it is a subset of end-user native.
- yesimahuman 13y agoDon't get me wrong, I agree with you. which is why we are making the change. I'm merely throwing out the other question because I find it interesting.