Amazon and Walmart launch iPad web apps to evade Apple's app policies
theinquirer.net
theinquirer.net
I think Apple wins when people make HTML5 apps that run everywhere. Unlike hte “old” Apple, the Apple is winning on price and obviously people like its design choices. At this point, apps that lock people down into the Apple ecosystem are a nice-to-have for Apple, but if everything is cross-platform, Apple still wins. The only way they lose is if somebody invents a “killer app” that is locked into another platform.
So allowing or even encouraging HTML5 apps is a great defensive move for the leader to make.
However, with Android rising everywhere, and Google spending billions on developing Chrome, ChromeOS and Android HTML5 capabilities, they may feel it's dangerous to cede the playing field of native apps.
HTML5 apps can and will exist for iOS devices, but I posit they will always have a shittier experience than native, and some apps will never be possible as HTML5 only.
It always stroke me as strange that Google didn't do anything like that on Android and honestly it looks like everybody is doing better mobile web apps than Google these days (Amazon, Twitter, even Facebook), which is pretty surprising as well.
One note: iTunes music files haven't had DRM anymore since 2009.
I disagree about the mobile web apps though. I think the Google+ (and formerly Google Buzz) web app is just as good as the counterparts. I actually don't like the Twitter mobile app too much. If I click an outside link to a Tweet why in the world aren't you rendering it on the server side?
RDIO did the smart thing and adopted in-app purchasing w/ a surcharge if you do it in-app. The intention seems to be "pay for the convenience" as well as making sure their ARPU is intact regardless of method.
That being said: has anyone calculated what the per-transaction overhead would be if a developer wanted to institute in-app purchasing themselves? Considering Apple handles CC processing, chargebacks, customer service on the purchase, verification, etc?
One of the biggest obstacles for marketing a web app is breaking the notion that you must be online to use it. If people on HN think that web sites can't be used offline, what must the common end user think?
I told my Dad to switch from the FT app to the FT webapp when it came out a couple of months back, which he did - hee doesn't know it's a webapp, he doesn't care. As far as he is concerned, after setting it up, he clicks the FT logo, it gets the news from the internet, and he can read it on his device. Is it coming through a browser or a different piece of software? Who cares.
I think that's the wrong approach. Let the browser do the things it does well. Use javascript to enhance the browsing experience, not to fill holes.
We're undergoing a shift in web design where the purpose is to make web applications look like native applications. I think in a couple of years we'll see a rejection of this and instead have web applications which look like websites but have the capabilities of native applications.
Let scrolling work the way it's worked since the web was created. Instead of hacking a page flip animation, precache the next page. Instead of capturing every click event, use cache.manifest and smart pre-caching to let your app look like a single page app even though it's not.
Honestly, Apple should come to their senses on subscription content and just lower their take to something like 10% because they have make no significant contributions to facilitate the sale. They clearly don't get publishing as well as Amazon.
But Apple is doing more than "simply hosting their app" they are facilitating payments as well.