WTF is this shit....was this a joke?
No, just PR material from a company with a horse in the race, targeted at people who are too poorly informed to see through it.
This is so wrong at so many places. Web App vs Native App (Infographic)
31–40 of 41 posts
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#32This avoids the one major reason that I think most developers choose to develop native apps - how much easier it is to charge for it.
It also sidesteps many of the shortcomings associated with going the HTML5 route. In short, it's not an fair, objective comparison of the two.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#33its 100% amateur hour in here
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#34If 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.
This is the blog that linked to it and that's how I got to it:
http://blog.utest.com/mobile-app-or-web-for-mobile-infograph...
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#35And 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 shou…
The App Store offers exposure to a few hundred applications that are at the top of their category due to intentionally difficult to predict algorithms; relying on this mechanism for users discovering your app is asking for failure and makes about as much sense as making a web page and hoping that it appears on the front page of a website catalog/portal like Yahoo for the lifetime of the product. For 99.99% of the applications in the store, people are going to be finding out about it from online reviews, word of mouth, and search engines.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#36Earlier quoted context omitted.
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)
This question is only going to be relevant if the application is already open: if you close your browser windows and then re-open the application it will use the latest cache and evict the older ones. In essence, this mechanism is designed to allow an application to operate with an atomic version of the resources it requires for operation, and is not designed to allow the user to manage old versions.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#37HTML5 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.
Web applications can be icons on your home screen (at least on the iPhone): just click (+) and "add to home screen". If the application is setup correctly, when spawned in this manner it will also appear without any browser chrome, allowing it to be a truly full screen application.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#38Earlier quoted context omitted.
Should add a few, too, like "hope wireless connection works well or that developer properly prepared manifest," or "hope the developer didn't just assume 'web app' meant 'test in Safari Mobile only,'" etc.
And not just that but not all the native apps have-to-have-an-active-internet connection vs. a web based app.
Not all web apps do, either, thanks to HTML5 Manifests and the like. That said, not everything plays along well with offline web apps, sadly.
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#39Apps may contain viruses? FUD pure FUD
Re: This is so wrong at so many places. Web App vs Native App (Infographic)
#40This is useless flamebait.