The only valid negative point I see here is "update app", which is really the web-as-deployment-platform's killer feature from a user's perspective. I do hate having to update 20+ apps on a regular basis, it should just be on-demand.
This is so wrong at so many places. Web App vs Native App (Infographic)
21–30 of 41 posts
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#22Never had any of the problems on the left with my iPhone. Seems like FUD to me.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#23If it's so wrong, then why do you post it?
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#24HTML5 support for things like geolocation / camera usage is inconsistent across models and generally brittle. The upside is that mobile web is really low friction and allows for instant deployment, but there's functionality and no good management system like the home screen.
I've used the Quora web app occasionally. But if I had actually had a Quora app on my home screen, I'd use it far more frequently.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#25The only valid negative point I see here is "update app", which is really the web-as-deployment-platform's killer feature from a user's perspective. I do hate having to update 20+ apps on a regular basis, it should just be on-demand.
The problem with invisible updates is sometimes you don't want to get the update at all. This is especially true if you work in a corporate environment and you need to re-certify each version of the app for use on your work-provided devices.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#26The only valid negative point I see here is "update app", which is really the web-as-deployment-platform's killer feature from a user's perspective. I do hate having to update 20+ apps on a regular basis, it should just be on-demand.
The problem with invisible updates is sometimes you don't want to get the update at all. This is especially true if you work in a corporate environment and you need to re-certify each version of the app for use on your work-provided devices.
HTML5's Application Cache can solve that to some extent. I believe you can prompt to user to ask if they want to update (though once it's updated there's no going back, or installing previous version initially, unless the site provides mirrors of old version)
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#27WTF is this shit....was this a joke?
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#28If you try to view the post in a mobile browser, you get:
"Article not found"
Or at least, I am, on my iPhone right now.
There's definitely a touch of irony there.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#29This is just an excuse to drop a semi-cool design on the web using a hot topic, very typical these days.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#30And of course, this whole thing ignores an entirely different entry point "Discover new app". It assumes you are specifically searching for the app in question. What the app store and it's ilk offer is exposure. Angry Birds has been near the top of the top 25 on the app store since launch, and that alone drives continuous sales.
If you're an incredibly well-selling web app, you STILL have to market and spend and shout to get yourself known. No matter how well you're doing, your word of mouth still probably doesn't beat Apple's Top 25 board.