Beyond App Stores: Weaving Apps into the Web
blog.gaborcselle.com
Beyond App Stores: Weaving Apps into the Web
1–10 of 34 posts
Re: Beyond App Stores: Weaving Apps into the Web
#2Re: Beyond App Stores: Weaving Apps into the Web
#3I don't know how else to put this but local, compiled apps run faster than web apps. And the problems laid out in the article are indicative of development choices, for example not being able to pick up where one left off in a local app as opposed to in a browser app in the NYT example.
The central theme of the post is that the local app and the webpage are disconnected - the fact that you can't pick up where you left off in the other is not a development choice.
Re: Beyond App Stores: Weaving Apps into the Web
#4Re: Beyond App Stores: Weaving Apps into the Web
#5Re: Beyond App Stores: Weaving Apps into the Web
#6Isn't NaCL supposed to in part solve this?
Re: Beyond App Stores: Weaving Apps into the Web
#7Re: Beyond App Stores: Weaving Apps into the Web
#8I don't like apps anymore. Why would I want Hotel Tonight (for example) on my iphone from a trip to Dallas two months ago. The constant updating, notifications, etc. Apps are a mess. I don't have a solution but I do know I'm tired of apps.
I only use email/rss and twitter apps. Everything else I always try to do in the browser.
Re: Beyond App Stores: Weaving Apps into the Web
#9Automatically downloading and executing binary code from the web. What could possibly go wrong? Isn't NaCL supposed to in part solve this?
Re: Beyond App Stores: Weaving Apps into the Web
#10we can call them "applets"!