4 ms·

I think native apps will continue to have significant advantages over the time frame you mentioned. The biggest reason is the following: Steps to open the Face

I think native apps will continue to have significant advantages over the time frame you mentioned. The biggest reason is the following: Steps to open the Facebook web app- 1) Click on browser 2) Type in Facebook.com 3) Sign in Steps to open the Facebook native app- 1) Click on Facebook HTML5 (and other web languages, but mostly HTML5) apps may be more prevalent in the future than they are now due to cross-compatibility advantages, but it is still difficult to use phone functionality in comparison to native code.

bmelton 14y ago
Your second scenario relies upon credential caching, or "saved logins", and is just as doable for an HTML5 app as it is for a client app. Facebook still has credentials (vs. some apps that are tied to just the phone number or native Google account tied to the phone) and as such, still requires a login for that initial run, just as an HTML5 app does. In that regard, it's possible that the non-Facebook app has an advantage in that they can use Google oAuth to authenticate the user which, on an Android phone, already contains an active session, so their login method can be even leaner than the Facebook app (until and unless Facebook changes something, or releases their own hardware).
- hiddenstage 14y ago
  I realize that but I for one clear my cookies/cache pretty regularly in my browsers while I hardly ever do so for my native apps. I may not be the majority, but my point remains that there is still a higher barrier to entry for browser-based apps.
  - bmelton 14y ago
    Perhaps it was just a bad example, but your minority use case rivals my own, which is that I do not save credentials on my Facebook app. Again though, if app_x implements login-less transactions, perhaps using phone number or phone SSID, or Google oAuth, then they're ahead of the Facebook app, login-wise.

bmelton 14y ago

Your second scenario relies upon credential caching, or "saved logins", and is just as doable for an HTML5 app as it is for a client app. Facebook still has credentials (vs. some apps that are tied to just the phone number or native Google account tied to the phone) and as such, still requires a login for that initial run, just as an HTML5 app does. In that regard, it's possible that the non-Facebook app has an advantage in that they can use Google oAuth to authenticate the user which, on an Android phone, already contains an active session, so their login method can be even leaner than the Facebook app (until and unless Facebook changes something, or releases their own hardware).

hiddenstage 14y ago
I realize that but I for one clear my cookies/cache pretty regularly in my browsers while I hardly ever do so for my native apps. I may not be the majority, but my point remains that there is still a higher barrier to entry for browser-based apps.
- bmelton 14y ago
  Perhaps it was just a bad example, but your minority use case rivals my own, which is that I do not save credentials on my Facebook app. Again though, if app_x implements login-less transactions, perhaps using phone number or phone SSID, or Google oAuth, then they're ahead of the Facebook app, login-wise.