Web-based Apps vs. Apps Built on Web Standards
http://www.youtube.com/v/VmjxmOtNZCk&color1=0xb1b1b1&color2=0xcfcfcf&feature=player_embedded&fs=1
I continue to get e-mails from readers that have already dismissed the Palm Pre for one main reason. What is it? Folks believe that you won’t be able to run applications without connectivity. Bzzzt, wrong answer… thank you for playing! Palm never said that WebOS applcations were “web apps.” They said that the WebOS appliations were built on web standards like HTML, CSS and JavaScript. In contrast, “web apps” are generally provided to you from a remote server to your web client, which would require a connection. That’s very different.
Want to see where all of this is heading? Have a peek at the above video from iPhoneBuzz that shows an experimental version of Gmail on the iPhone and G1. The application is based on HTML5, a web standard, and works offline with a local database cache.
I couldn’t find a video of the Pre working in offline mode, but let’s think about it for a second. Palm said that all of the native apps on the Pre are built using the same web standards. Do you really think that if you turned off the Pre’s radio, you’d be carrying a useless piece of plastic? Nope. WebOS is based on a Linux kernel, and you can be darn sure there’s some type of web server in it. That would allow the Pre to run apps based on web standards even when there’s no connection. Make sense?
This embracing of web standards for apps doesn’t just make it easier for web developers to create apps for the Pre. I expect a total paradigm shift in both online and offline application capability over the next few years. One that will take us far beyond today’s limitations of hunting for a wireless or mobile broadband signal.
Where does that place the competition in the smartphone market then? Let’s assume for just a second that I’m right and that mobile apps based on maturing web standards are the future. Apple, Google and Palm are all in a position to take advantage of that future. Where does that leave Windows Mobile, Symbian S60 and the BlackBerry platforms? Hmm… All of a sudden the browser engine and underlying services just became more important than ever, no?
Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.
I thought that the developer community rejected the notion of web-standard apps. Didn’t Apple propose that web-standards be the basis for iPhone apps when they announced the iPhone at MacWorld 2007? Didn’t developers reject web-standard apps in favor of Cocoa apps?
Are developers now going to have a change of heart because Palm has climbed on board the web-standard apps bandwagon?
For these same reasons, I also believe modern open engines based off new standards will begin to over take proprietary run-times such as Java, AIR, SilverLight and Flash.
You also don’t need a web server to run the web-apps if all you are using is standard browser technologies such HTML, CSS, and JavaScript, which are all implemented client-side. The web server is [was] used to serve pages, store data and do pre-processing, none of which is needed when viewing (running) local pages (applications).
Steve, the notion of “web apps” was rejected, not “apps based on web standards”. That’s the core difference that I tried to outline above.
Those rejected “apps” weren’t apps at all. They were links to server-side web pages & apps that required connectivity. Perhaps I’m not explaining the difference well.
I think WebOS on the Pre will be successful if the make enough of the underpinnings of the phone available for developers. When I think of apps I run most on my WM device most could be available through html and java script. The things that would keep me from switching would be the availability of offline gps apps(like TomTom and Topo!)and offline divx video players.
“Are developers now going to have a change of heart because Palm has climbed on board the web-standard apps bandwagon?”
This is not the same thing. Web based apps are not the same thing as web-standards based apps.
Apple wanted developers to create web-based apps that would run off a web server somewhere on the Internet, which means the user had to be connected in order to access and use those applications and the developer had to have a server hosting the pages. The Palm Pre will run local web-standards based applications, in much the same way Dashboard currently runs widgets in OS X. Dashboard is basically just a layer for running local web-standards based applets (with a few non-standard hooks).
What’s the bennifit of a webos app? If there is no difference to the end user what’s the point other than allowing any Kid who can make a web page to make a palm app?
“What’s the bennifit of a webos app? If there is no difference to the end user what’s the point other than allowing any Kid who can make a web page to make a palm app?”
There isn’t really a benefit, other than the sheer number of people who know how to write web pages and are already familiar with those standards, languages and environments.
It really wouldn’t take much on Apple’s part to allow developers to being writing similar web-standards based applications for the iPhone. The underlying technology is already present in OS X.
Any word if the application would be able to update itself through App Cache? I would presume so. If the update process could be made interaction free, transparent to the user, it would be another advantage compared to regular apps and put it on par with web-based apps.
I’d want a side-slider form factor to get bigger keys and reasonable two-thumb ergonomics. The landscape screen in that mode allows a bigger font.
My ppc 6700 has an on-screen phone pad in candy-bar orientation. Why can’t this desirable configuration be replicated?
I fully understand the distinction you are making but safari was supporting HTML 5 when iPhone 1.0 shipped (mobile safari did not yet). Developers knew that local data/database access would become available and yet they didn’t call to Apple to get HTML 5 support in mobile safari they asked for a full development platform. WHY? Well for one thing compiled code is much faster than interpreted code!!! For another, even though you can do TONS of things with current web standards you can still do TONS more with lower level API’s.
I’ll put it this way… You will not see Doom on the Pre any time soon.
Now on the other side you do finally have write once and run on multiple devices as long as you don’t use any OS specific hooks which everyone will need to do to write really cool applications. Even something as simple as location services will be device dependent. So, it is interesting but IMHO it will not generate the buzz of the current iPhone App store. And if I’m wrong, the good news is that all of these applications should be available for the iPhone too. :-) Ether way, it seems like the Pre has a tough fight ahead of it.
Well ya know…one good thing about the good ol’ Windows Mobile platform, as broken as many people think it is, is the fact that there are great developers out there like Torch Mobile. They are bringing the latest Webkit browser to Windows Mobile that has one of the highest Acid scores of any other mobile browser. Their latest release has the foundation to support HTML5. So, I think Windows Mobile will cope if this is the direction that developers choose to go.
http://www.torchmobile.com/blog/