Got a tip for us? Share it...

iPhone SDK Reactions and Ongoing Questions

The release of the iPhone SDK provided a lot of answers, but has also raised a number of questions, many of which will not be answerable until the iTunes App Store launches in June 2008.

The general sentiment, however, has been quite positive with most expectations being exceeded. The addition of numerous enterprise features has removed many hurdles for corporate iPhone adoption, though it may still be an uphill battle against RIM which many businesses have already heavily invested in both servers and training.

The significance of a native iPhone version of Epocrates for health care professionals can not be overstated. In my experience, it alone has been significant driver in Palm sales amongst physicians, and its absence on the iPhone has been a significant hurdle for physician adoption of Apple's phone.

Developer reaction has also been generally positive. Despite lengthy MacRumors reader debates about the 70%/30% fee structure of the iTunes App Store, public developer response has been generally accepting. A notable comment by id Software's John Carmack suggests that the "iTunes distribution channel is really a more important aspect than a lot of people understand".

As expected, Apple is exerting editorial control on applications that appear on the iTunes App Store. Explicit restrictions are quite reasonable with limitations on illegal, abusive and offensive applications. Some are concerned, however, that Apple may have other restrictions that are not as clear-cut. Still, that hasn't prevented some from predicting that this marks the beginning of an enormous opportunity for Apple with the belief that "what Microsoft and Windows was to the desktop, Apple and Touch will be to mobile."

Top Rated Comments

(View all)

51 months ago
As I recall, Steve said SDK will be released late February and now he's making developers and iphone users wait until June. They are taking existing SDK Apple developers use and releasing to general developers so I'm not sure why he's making everyone wait for next Firmware update.
Rating: 0 Positives / 0 Negatives
51 months ago
Well put withthat final sentence
Rating: 0 Positives / 0 Negatives
51 months ago
June is a long time to wait, but let's hoe they get stuff right and make the ipod touch/iphone even more usable. Any idea on how much these fees are? Are all of them monthly?
Rating: 0 Positives / 0 Negatives
51 months ago

"what Microsoft and Windows was to the desktop, Apple and Touch will be to mobile."


I think so, but I wonder if AT&T will be the biggest road block.I can't wait for June. I think as time goes by we will cell the big cell companies fade with the focus being on the consumer buying data plans not hardware. Perhaps focus will shift more to the iPod touch as wifi becomes more available.
Rating: 0 Positives / 0 Negatives
51 months ago

As I recall, Steve said SDK will be released late February and now he's making developers and iphone users wait until June. They are taking existing SDK Apple developers use and releasing to general developers so I'm not sure why he's making everyone wait for next Firmware update.


No, the SDK is available now, for people to become familiar with it, and start writting and testing applications.

What comes in June is the ability to move the applications to the application store to sell them there and the ability of developers being able to test with their iPhone instead of the emulator.

Not sure why people has so little patience. People need time to get used to the SDK and learn what they can do with it. After that they can create even greater apps as the SDK and its API are powerful.
Rating: 0 Positives / 0 Negatives
51 months ago
This is my thought too. If they add a microphone the Touch will essentially become a 'pseudo-iPhone' with something like Sype installed
Rating: 0 Positives / 0 Negatives
51 months ago

As I recall, Steve said SDK will be released late February and now he's making developers and iphone users wait until June. They are taking existing SDK Apple developers use and releasing to general developers so I'm not sure why he's making everyone wait for next Firmware update.


I imagine that they needed more time to get the SDK / App Store to really work well. The 3 month intro time will get more developers on board, and make the promise of a "Full Store" available at launch.

Patience. It is hard, but it will be worth it.
Rating: 0 Positives / 0 Negatives
51 months ago

As I recall, Steve said SDK will be released late February and now he's making developers and iphone users wait until June.


He did say it. The SDK is available for download. Jobs never said or promised anything about application availability or anything related to distribution by any date before yesterday. All that was promised was an SDK. He delivered it.
Rating: 0 Positives / 0 Negatives
51 months ago
People are funny here... June is NOT a long time to wait... developers have something now.. this is good. And anyone that thinks the 70/30 split for world-wide distribution through iTunes is too much has no idea of distribution models for software.... this is very fair and reasonable.

The SDK and the program Apple has put together is great... it's going to change the value proposition for the iPhone and for the iPod Touch too... this is big.
Rating: 0 Positives / 0 Negatives
51 months ago

As I recall, Steve said SDK will be released late February and now he's making developers and iphone users wait until June. They are taking existing SDK Apple developers use and releasing to general developers so I'm not sure why he's making everyone wait for next Firmware update.


How is he making developers wait until June? Do you mean he's making them wait until June to sell their apps ?


If so. That's no big deal. It just gives developers some breathing room to make their app good.

I've been playing around with the SDK a bit now and I can tell you a couple of those sample apps use some CPU time. If this translates onto the ARM I can see why Apple doesn't want the Dev apps to use background processes as it would eventually make the iPhone crash.

Now the Silverthorne chipset would be able to handle this quit nicely.
Rating: 0 Positives / 0 Negatives

[ Read All Comments ]