I may have missed a memo or something, and correct me if I'm wrong, but isn't the web app way that the Palm Pre went?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Laying Groundwork for Advanced Mobile Web Apps?
- Thread starter MacRumors
- Start date
- Sort by reaction score
I may have missed a memo or something, and correct me if I'm wrong, but isn't the web app way that the Palm Pre went?
Software should always be compiled to machine code and run natively on my hardware.
There is no benefit to running my software on a server and having a html/javascript UI in a web browser or embedded browser app. Its ridiculous and not very efficient. Users must wait for the servers response during peak hours while their own processor sits idle. Desktops now are more like super computers and that power is just being wasted translating HTML into an interface and using an interpreted language (Javascript) to modify the content of that page. It carries more disadvantages than advantages (if any [though i fail to see any]). If the only goal is interoperability/platform in-dependancy then open API's/SDK's are all that web apps need provide, and let the software devs of various OS's develop software to pull/push only the data from the service and let the UI and the logical functions run in machine code.
Web apps are a fad and are an inefficient use of computing power.
Just how i feel though.
There is no benefit to running my software on a server and having a html/javascript UI in a web browser or embedded browser app. Its ridiculous and not very efficient. Users must wait for the servers response during peak hours while their own processor sits idle. Desktops now are more like super computers and that power is just being wasted translating HTML into an interface and using an interpreted language (Javascript) to modify the content of that page. It carries more disadvantages than advantages (if any [though i fail to see any]). If the only goal is interoperability/platform in-dependancy then open API's/SDK's are all that web apps need provide, and let the software devs of various OS's develop software to pull/push only the data from the service and let the UI and the logical functions run in machine code.
Web apps are a fad and are an inefficient use of computing power.
Just how i feel though.
jQTouch
Why not rally behind jQTouch? Seems a lot more robust than PastryKit. Okay, so it doesn't allow the pinning of the header or footer (yet)... but it seems to do much more than PastryKit.
http://www.jqtouch.com/
Why not rally behind jQTouch? Seems a lot more robust than PastryKit. Okay, so it doesn't allow the pinning of the header or footer (yet)... but it seems to do much more than PastryKit.
http://www.jqtouch.com/
There are tons of advantages.
It takes up less space on your hardware. Webapps can be constantly updated, ensuring that everyone who accesses the app is using the same exact up to date version as everyone else. All the information is stored on the server so no matter what device you are using, you are accessing all of your info. These three points, for me at least, make web apps MUCH more valuable than native apps.
Right now the only issue is speed, native apps are faster (most of the time, if they are written well enough) than web apps. As the web continues to grow, things like HTML5 are bridging the gap between web apps and native apps. Soon enough we'll have the speed and offline capabilities of native apps in web apps (we already do with google gears and html5 and such, but it's clear that there's room for improvement) and it is my personal opinion that soon enough there won't be a difference between native and web apps.
Not web based, but written in common web languages that millions of developers understand.
Interestingly, Palm has come out with a web-based SDK that allows anyone to create a Pre app.
Palm Ares Web Based SDK article
Power to the people! Sure wish Apple had something like Hypercard for the iPhone.
The transmission web interface doesn't remove the address bar, it hides it initially. You can already see the bar if u scroll to the top. What is explained in this article and PastryKit is far more advanced than that.
a wired article from today on app stores vs web apps
http://www.wired.com/gadgetlab/2009/12/firefox-mobile-vs-app-stores/
http://www.wired.com/gadgetlab/2009/12/firefox-mobile-vs-app-stores/
Thanks for posting.
Analyst Michael Gartenberg seemed to have the smartest quote from that article:
Couldn't agree more.
People who claim "web apps are the future" are crazy. But then so are the people who say "web apps are dead." Both native and web apps are here to stay, and people need to embrace both platforms -- and not shun one because it's "not for them."
Just agreeing with Rojo
The whole point is to explore what the device can do for you. being limited solely to native apps is as foolish as the opposite.
Increased connectivity and processing should sort of be the point right? More versatility.
I for one welcome more web apps (because it's important for what I do). I like native apps and think some are incredible, I just want more in the longterm from technology no matter what it is.
because, I'm greedy like that.
The whole point is to explore what the device can do for you. being limited solely to native apps is as foolish as the opposite.
Increased connectivity and processing should sort of be the point right? More versatility.
I for one welcome more web apps (because it's important for what I do). I like native apps and think some are incredible, I just want more in the longterm from technology no matter what it is.
because, I'm greedy like that.