[...] continue to debate if mobile apps are here to stay and Google continues to improve their mobile services. Over the past couple of months, the Gmail [...]

[...] Are mobile apps here to stay? Page 1 of 2 | Next pagePosted in Android, androidandme | No commentsPrevious post: How-To: Remove unwanted applications on your new HTC Evo 4G [...]

[...] Are mobile apps here to stay? [...]

Yea but do you realize that adobe can’t even make Flash run right on dual core desktop! I cant even watch a low quality utube video without my cpu peaking like 40%. You also have to remember that Google is a search company that makes it’s money from selling Ads. They can deliver more Ads if everyone is using programs in their cloud. That is why they push “web apps” and “cloud computing” on everyone. Like others have said, Web apps are good for some things but not for everything. There will always be a reason to have both EVEN if web apps can match native app performance.

One tech you have all forgot is the coming of AIR 2.0 for mobile, with Flash Player 10.1 for mobile as well. This is really the one differentiating factor. When this arrives it will be available for all smarphone OS’s except iPhone, but i got a feeling in order to not lose market share Apple will have to bring it to the iPhone. This is the one place where fragmentation does not play a part with the possiblilty for local specific functionality like currently available in each native OS framework.

Good time to be a Flash Dev :)

This argument is not new, and is a pretty religious argument between web vs. local/native developers. Local mobile apps are here to stay, for a long time. Web runtimes will help the transition, once all access to handset capabilities are possible (and standardized), but I am believer that both classes will remain and co-exist. Where web apps suffices, web will do fine, but when wanting to build very rich apps, local apps is the way to go. Also, a better way to monetize mobile web apps is needed.

ceo

As phone hardware and web standards continue to advance more _network based_ applications will become web based, that’s for sure, others never will, like the Compass app – even if you could make that web based (which would require someone to put in an API to access a devices compass into HTML!!!) why the hell would you? I don’t want to have apps I can’t use without web access and while you’re at it, those I do I don’t want to load the code for an application off the web, i’d prefer an app which only needs to load data from the site, not code as well. It’s not hard to see that loading the text of every tweet plus whatever encapsulation they have is going to be a lot faster than loading that and all the layout code for the webpage as well. Plus with HTC Peep I can catch up on tweets at work where I have no signal.

Even if you could make a webapp with 3D rendering run native on a device it will end up running a lot better if it’s written specifically for that device manually since the web version built with a toolkit won’t be as optimized which is very important for something as resource hogging as 3D (or fancy 2D effects for that matter).

@all opponents of Native Applications

I’m on an airplane and I want to play a game to entertain myself
I’m on a hike in the wilderness and want to shoot some video of nesting birds
I’m on a boat in the ocean and want to work on a novel I’m writing.

Java, and Flash made claims to be able to have cross platform compatibility. HTML5 and Web Applications are just the next claim set to fail because Native Applications will always hold an amount of performance, security, and availability in some areas.

[...] continue to debate if mobile apps are here to stay and Google continues to improve their mobile services. Over the past couple of months, the Gmail [...]

[...] and Android and me befassen sich aktuell mit einem spannendem Thema: Haben Apps eine [...]