Why don't you take off your geek hat for a second and put on a quality of service hat. Everything on the iphone runs as root... therefore everything has the ability to A) crash the system B) hog resources and cause other programs to perform poorly C) cause users to have to worry about buffer overflows and other security issues that Apple has no control over.
Why don't you take off your ultra-fanboy HAT for a second and put on a customer hat. APPLE MADE THE OS AS SUCH TO RUN THEIR APPLICATIONS AS ROOT. Obviously, this could easily be changed and limit system access to 3rd party apps, not to mention they would probably build a separate sandbox anyways.
Doing what Apple did for the SDK is pure solid genius. I think the only area where they were cruel and unusual was not allowing local storage, and not having hooks into the existing Apps... phonebook, maps, etc. There are extremely valuabe tie ins there.
pure solid genius, eh? Is that why there is such an incredible backlash against the company?
yes there are no killer web 2.0 apps for the iphone... but *gasp* the iPhone *is* the killer app.
COME ON NOW.. thats so just reaching for the stars....
What do you *need* that the iPhone doesnt have, that a 3rd party could give you? The only thing I can think of is instant messaging, but that will never happen with the current agreement terms with AT&T.
I knew THAT ARGUMENT was going to come out.. "what do you need that Apple won't give you". That's just pathetic.
Unless you TRULY can't COMPREHEND what could come out of 25,000 developers having access to a revolutionary-in-capability high-speed graphics-accelerated Multitouch device?
You can't think of ANYTHING you might want? just off the top of my head..
- Voice Recorder (college lectures)
- Ebook reader
- Instant messenger
- picture / file transfer
- dictionary / thesaurus
- enhanced email program
- sketch / drawing
- Wi-Fi stumbler
- money manager/quicken pocket
- medical diagnostics for physicians
- DNA sequence / BLAST database
- Corporate applications
[/B]
The thing that mystifies me is, how can Apple expect us to take the idea of using the web for applications when they themselves don't? How stupid do they think we are?
I mean - look at what they do, not what they say. Stocks and Weather are applications that consist of nothing but putting a simple (if pretty) frame around pure internet-supplied, simple data. Hell, the Calculator is so simple that it would be nearly trivial to do it in Javascript... but since you might want to use that when you have no network, let's just keep it to Stocks and Weather, which are useless without net.
Stocks and Weather are applications that are pure naturals for web pages if any ever were - and Apple ships them as native applications, taking 2 out of only 16(*) buttons - a full 12.5% - on the very highest level of the device.
[ (*) OK, 17 buttons if you've updated. I haven't even though I haven't hacked mine in any way.]
It simply doesn't ring true. If Apple isn't content using Safari for such trivial front ends, why in the hell should anybody else be? It's clearly an inadequate approach for applications, and Apple isn't even eating their own dog food on this.
GREAT POINT...
I fail to see your point...
are you serious? is that sarcasm?
I'm the only one in the world who likes that there is no native support.
It forces devlopers to make web apps and web apps don't take up any of my iPhone's precious space. Granted, I have a bit of room on mine fora few apps, but there are soooooooo many web apps out there that we take for granted. I use facebook and an IM client many many times a day. It's nice to have those not take up any room on my phone.
Besides all the shortcomings of webapps... the point here is CHOICE. I don't give a rip what you like or the fact you think little iPhone apps are going fill your 8GB HDD? Just the same, you are not me and want you want, not what I want.
The beauty of choice......
In addition, I think Web 2.0 apps could come extremely close to matching full apps -if there are several improvements to the WebKit engine in the iPhone to improve performance and add more full-app like features.
I am not going to rewrite everything, but look back at my posts on page 5 -7, and you'll see why web apps will never "COME EXTREMELY CLOSE" to matching native apps.
painfully slow javascript execution, no access to the awesome hardware accelerated graphics to make a sweet GUI interface, no access to the camera, no access to the microphone, no access to the speaker, no access to the bluetooth, most importantly NO ACCESS TO MULITOUCH! you take away all these things and whats left? html/javascript interace with a "onclick" event.
What fascinates me is that those who state that Apple is wrong in its manner of addressing third party applications, etc. seem to generally have taken the time in thinking the issue through and writing logical and convincing arguments, while those who disagree seem to take personal slams and use rhetoric that lacks any thought. Very interesting...
Haha.. great post
If you do some more research into Intels upcoming hardware, you'll realize the iphone will run ARM and NOT x86 for at least 3-4 years. And only then the only way that will work is if they had some type of hybrid solution because even an Intel 45nm silverthorne sucks battery like CRAZY compared to an ARM architecture chip. A Silverthorne in an iPhone with a similar size battery as it has now would NOT last more than 7-9 hours standby and 2-3 hours talktime on a charge, if that. They would have to have some type of ARM running the phone radio and then the x86 (well actually it would be x64) running OSX. Go speak to any expert in embedded development and they will tell you the same thing.
Besides, even if it was a thought for the future, that is no excuse to completely stifling *REAL* software development on the iPhone. "Web 2.0 Apps" are a complete joke on such a powerful phone. CASE IN POINT, why did Apple not use WebKit for any of THEIR applications, especially weather, stocks, and google maps?
Oh, right because Javascript/HTML "apps" are SLOW, Have crap interfaces, Can't use accelerated graphics, Can't utilize multi-touch etc etc.
To the guy who says he's going to make Ajax apps that are close to native apps, I say SHOW ME. If you are talking about a form-based To-Do list or a Flickr viewer... fine. Anything more complex is NOT going to happen. Have you tried to write/debug/maintain a large javascript/html application?