Developers miffed about Apple’s third-party iPhone apps solution

“Perhaps it’s playing well in the mainstream press, but here at WWDC, Apple’s ‘you can write great apps for the iPhone: they’re called ‘web sites’’ – message went over like a lead balloon,” John Gruber writes for Daring Fireball.

Gruber writes, “It’s insulting, because it’s not a way to write iPhone apps, and you can’t bullshit developers. It’s a matter of spin. What Apple should have announced is something like this: “We know that you want to write your own apps for iPhone, and we’d like to see that too. We love the apps you write for the Mac, and we’d love to see what you might be able to come up with for iPhone. We’re thinking about it, and working on ways that we might make that happen, but we don’t have anything to announce today. The good news, though, is that because iPhone has a real Safari web browser, you can write web-based apps that work great on iPhone.”

Gruber writes, “That wasn’t what the developers here at WWDC wanted to hear, but at least it wouldn’t have been insulting.”

Another reason why Apple developed and released Safari for Windows, according to Gruber, “is simply money. Safari is a free download, but it’s already one of Apple’s most profitable software products.”

It’s not widely publicized, but those integrated search bars in web browser toolbars are revenue generators. When you do a Google search from Safari’s toolbar, Google pays Apple a portion of the ad revenue from the resulting page,” Gruber explains. “My somewhat-informed understanding is that Apple is currently generating about $2 million per month from Safari’s Google integration. That’s $25 million per year. If Safari for Windows is even moderately successful, it’s easy to see how that might grow to $100 million per year or more.”

Full article, with more about Leopard, Jobs’ scant list of “top secrets,” that the new Dock that only works visually at the bottom of the screen, and more, here.

98 Comments

  1. OK I’m not a programmer and I do take the point that they want full access to the OS on the iPhone.

    But that’s no reason to throw the baby out the pram.

    If Google are writing all their apps on Web 2, it can’t be all bad, and arguably it’s the future.

    I for one don’t blame Apple for restraining the use of apps on iPhone. We’ll end up with duplicate Mail progs, browsers, antivirus and a lot of other bollocks we don’t need.

    Let’s learn to live with it and see how it goes. It is a revolution after all.

    I say the kiddies should grow up frankly.

  2. And, no, they are not being Microsoft, they are being sensible. Microsoft would have the whole think cocked up in no time with a free for all in an endeavour to take the whole market.

    Oh, but then Microsoft never invented ANYTHING like this before.

  3. I think as soon as the developers see how many iPhones are sold they will start developing the apps using the Apple tools whether they like it or not.

    Lets face facts, the iPhone is going to be MASSIVE.

    And when is does you can bet that the clients of developers are going to DEMAND their apps be written for iPhone.

    And if the developers dont do it… then they will lose their client to a developer that will do it!

  4. Developers miffed about Apple’s third-party iPhone apps solution

    Well you know what developers?

    95% of exploits are on applications, yea YOUR FSCKING SHODDY CODE!!

    Why is it shoddy? Because your G-Dammed marketing departments want your insecure crap out the door first and fix it later approach, if it gets fixed at all.

    So because of this, your FSCKING SANDBOXED!!! Good for us consumers!!

    And to those third party developers who demand a admin password (aka sudo/root) to install your programs/hacks when it’s really not needed (system level/cloning software excluded naturally).

    A big FSCK YOU from those of us needing security.

    You install your hacks in Mac OS X and it leaves a pathway to root through your shoddy coding practices.

    Sure nobody is frigging perfect, but you plan for that and keep your frigging code out of root and in user space where it belongs so a compromised app doesn’t have access to Mac OS X.

    BUT NOOOO!!! Your marketing departments want root so they can install marketing ware, knowing exactly what time and day we are launching what programs, how often we use the competitors software and evil privacy crap like that.

    And we all know full well you plan to use EFI to bypass any OS installed outgoing firewall software to catch you, to verify apps and other DRM crap invading our privacy and security.

    We buy your apps to solve a need/want, not to be exploited and probed and labeled thieves automatically.

    Get out of root space, stay out of EFI because I’m on a campaign to educate everyone to avoid software that installs in these areas.

    Apple is guilty too for trusting developers to care about security. They realize shoddy security by third party coders is going to ruin their hardware sales.

    So sit in your friggning sandbox where you belong, you earned it!

  5. There’s one huge group of developers that I guarantee you are very happy with Apple’s iPhone development solution: web developers. Last time I checked, they outnumber Mac OS X developers by a hefty margin.

    Relax people, more options will come in time. I for one will be happy to see apps with similar quality to Dashboard Widgets running on iPhone. They’ll still beat every other phone platforms apps any day.

  6. If you’ve seen the iPhone commercials, I’d have to sum it up as WOW, those “kinda sorta look like” applications!

    Hey Jobs, if you want to bend over your developers, please don’t do it in public and expect them to applaud you while you do it!

  7. the web will be the future of software development the day HTML is replaced by something a lot better.

    it’s just too limited, there are completely categories of software that just can’t be made in HTML.

    i was planning to write a game that uses the iPhone’s accelerometer to move a ball through a labyrinth, that is not be possible with the Web API.

  8. Apple went with the web 2.0 option because it does not want to compromise the quality of the iphone user experience.

    This is totally understandable.

    Imagine the iphone in 2 years time if Apple didnt, the user experience would be as crap as all the other phones out there.

    This is the right way for Apple and developers to proceed imho for a co-hesive, sustainable and stable user experience.

  9. re: he web will be the future of software development the day HTML is replaced by something a lot better.

    it’s just too limited, there are completely categories of software that just can’t be made in HTML.

    i was planning to write a game that uses the iPhone’s accelerometer to move a ball through a labyrinth, that is not be possible with the Web API.

    —-

    Solution… write the game in flash! ” width=”19″ height=”19″ alt=”wink” style=”border:0;” />)

  10. To anybody defending this announcement:

    Please tell what it is was really good about the announcement for you! They already announced that a full version of safari was running on the phone, so you already knew you could write web-applications back at their original announcement. They already showed full websites before. People are not bad about that, they are mad that apple tried to pawn web-applications off as real applications.

    Stop defending this announcement! It was pure spin intended for the press, and it shouldn’t be tolerated by technology literate people of any form, web-developer or app-developer.

  11. If Google are writing all their apps on Web 2, it can’t be all bad, and arguably it’s the future.

    That’s Google’s bread and butter. Some of us live on a different diet. And web apps aren’t the future. And the internet won’t end the paper industry.

    You install your hacks in Mac OS X and it leaves a pathway to root through your shoddy coding practices.

    You shouldn’t argue with your imagination. It’s too easy. Pick a real opponent and argue with them.

  12. Anyone who sais that AJAX and web 2.0 technologies don’t allow full app development has no idea what he is talking about.
    Developers are now only scratching at the surface, most are too lazy to try something really new.
    Have a look at picnik.com or the Google apps!

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.