All Articles Tagged sdk

Literally every source on the interwebs is reporting that Apple has just released Beta 2 of their universe-denting SDK (Software Developers Kit). This new version now sports a working Interface Builder and an update to Xcode 3.1.

Warm up your downloads then get yourself a tasty beverage, because at 1.4GB and with $100 million on the line, even Apple’s servers may take a little while getting it to you!

Hot on the heals of the Microsoft MacBU (makers of Office 2008 for Mac) talking iPhone SDK, comes word (via Fortune) that Microsoft’s recently acquired TellMe division, which specializes in voice recognition, is also eyeing Apple’s little market grabber:

“If the SDK supports [voice recording and location-based information],” [general manager Mike] McCue told Fortune in February, “we’re absolutely going to get a version out there as soon as we can, get TellMe out there on the iPhone.”

Of course, limits placed on the iPhone SDK may well make this impossible without the mythical “special dispensation” from Apple. We do know Bill Gates loves him some “natural interfaces”, though, and who knows how long it will be until VistaMob 7 or Surface ship, so is this like back in the early days when Microsoft got all GUI on Mac Excel? Or is Microsoft really all just about the software profits, man? What do you think?

Chalk another developer up for the iPhone App Watch: Microsoft. Microsoft has a small team called the MacBU that develops the very successful Office Suite for the Mac — an office suite that until the recent version was widely thought to be more advanced than even its Windows counterpart and in some ways a “test bed” for features that would eventually make it into the Windows version of Office.

It may surprise some to hear that Microsoft is looking at the iPhone for development, but it ought not. I mean, they just all got buddy buddy with full ActiveSync Exchange support, so a little thing like utilizing the SDK for a Mini-Office app ain’t no thang.

“It’s really important for us to understand what we can bring to the iPhone,” Tom Gibbons, corporate vice president of Microsoft’s Specialized Devices and Applications Group, told Fortune on Monday. “To the extent that Mac Office customers have functionality that they need in that environment, we’re actually in the process of trying to understand that now.” – FORTUNE [via MacRumors]

Macnn/iPodnn (via The Inquirer) reports that unlike CoreLocation, which gives access to the Google Maps-like location-based services, Apple’s new iPhone SDK will be providing absolutely no access to iPod functionality or the onboard iTunes:

Any functionality related to music playback is inaccessible by the iPhone SDK, a new report claims. While the SDK allows access to many other functions of iPhone and the iPod touch, such as dialing, the camera and Internet access, The Inquirer writes that any components connected to iTunes are off-limits, preventing developers from accessing one of the most popular features of the phone

While this could be an anti-competitive move meant to keep VLC off the iPhone — or to protect consumers from the horror that would be RealPlayer Touch… — it may also cripple any Guitar Hero, Rockband, or iPod-style Phase gaming. (Unless Harmonix and other big game developers like EA are granted that oft-mentioned “special dispensation”…?)

Did it used to about the music, and Apple’s now telling us to just “sl@g off!”? Or are you happy they’re keeping developers’ tone-deaf mitts off your shiny (i)tunes? What do you think?

iLounge tells us that Apple has sent out a second note to would be $99-level iPhone SDK developers:

“We have many more requests than we can serve during this initial beta period, so we must limit the Program at this time. We plan to expand it during the beta period, and we will contact you regarding your enrollment status at the appropriate time. We appreciate your patience.”

This follows up on last week’s far more confusing note, and the rampant speculation it caused.

Now TUAW brings word that some developers have, indeed, been granted access to SDK paradise:

The accepted developers were apparently among the first to apply. The accepted developers previously received the rejection letter. The acceptances appear to be random. The program is firewalled. Five iPhone limit. Test devices are iBricks [or maybe not: see update at TUAW]

So does that really clarify anything? Will anxious developers get in before June? Or is Apple dropping the ball?

As part of his piece on the continuing confusion surrounding the $99 iPhone SDK program acceptance/pending/rejection letters, Daring Fireball’s John Gruber also dropped this very interesting nugget about the equally continuing and confusing situation surrounding the apparent Apple ban on multitasking and background apps:

[A] source confirmed to me that the iPhone AIM client AOL demoed during the iPhone Roadmap event does not cheat by continuing to run in the background — it quits when you switch to another app, but doesn’t log you out of AIM automatically. Such a client can’t notify you of IM messages from the background (a la the way the iPhone notifies of you SMS messages), but when you switch back to the AIM app, messages you missed should appear. Be wary of claims that “An app that does X is impossible without background processing.”

If accurate then that, as they say, is that in terms of any hope for multitasking apps before June. If Apple didn’t grant AOL “special dispensation”, they certainly won’t give any to Johnny “Next Big Social Perpetual Ping App”.

But is a non-background running AIM of any use to you? A welcome break from the constant connection demands of IM? A way to keep AIM second class to an eventual Mobile-iChat Touch app? Smart thinking on Apple’s part or just a train wreck in the making?

GearLive reported Flash for the iPhone was immanent. Adobe retorted that it was all up to Steve Jobs. His Steveness resorted to telling investors that Flash desktop was too big, Flash Lite was too small, and they were missing a product that was juuuusssst right.

Well, Adobe CEO Shantanu Narayen hopes Apple’s newly released SDK will help Adobe deliver that middle ground, with or without Jobs’ blessing. Speaking to investors, Narayen said (via Apple Insider):

“We believe Flash is synonymous with the Internet experience, and we are committed to bringing Flash to the iPhone. We have evaluated (the software developer tools) and we think we can develop an iPhone Flash player ourselves.”

Hopefully without those peskyprivacy and security problems, b’okay?

Given the restrictions imposed on 3rd party apps, unless Apple gives Adobe “special dispensation” it seems unlikely that even Adobe could get Flash working in an unplugged-in, sandbox environment, but we’ll see.

Eerily similar to Sun’s Java announcement immediately following the iPhone SDK launch, all that remains now (in terms of rival interactive development platforms) is Microsoft’s Silverlight. Balmer, get your dance shoes!

Following up on the cryptic “I Hate You – Don’t Leave Me” letters Apple sent out last week to many (all?) would-be iPhone developers who had coughed up the $99 for a certificate all signed and legal, Daring Fireball reports on whether or not anybody has made it in already:

I believe there are a small handful of developers who are sort of “in” already, but they were hand-selected by Apple. Perhaps, as with the ones who came on stage during the event to demo their “two weeks worth of work” apps, they were involved before the SDK was even officially announced.

But everything I’ve heard suggests that last week’s email from Apple was sent to everyone who applied for the program. I.e., there are developers who’ve been let in through the back door, but no one has gotten in through the front door yet.

John Gruber goes on to quote two sources who’ve told him that Apple has received over 10,000 applications alone for the $99 package and couldn’t meet demand for certificates this fast if it wanted to (and no one seems sure whether they do or not, nor how badly).

Massive over-reaction by the Twitterati? Yet another example of Apple’s dwindling communications skills? And will we have to wait until the June (30th at 11:59pm?) release to know for sure?!

The iPhone SDK will not allow 3rd party apps to multitask or run background services. We’ve previously covered both initial developer Twitter-rage at this, and pundit counter-points. We’ve also covered Craig Hockenberry before — the man who (perhaps poetically) develops Twitterrific for the Mac and jailbroken iPhones, and is now bringing it to the SDK.

Hockenberry, via his furbo.org blog, shares his experience on iPhone development and his views on the multitasking (non-?) issue.

To be blunt, I’ve never seen so many experts without a fricken’ clue. If you haven’t written code using the jailbreak tool chain, your opinions on the iPhone SDK, based entirely on what you see in a simulator, just aren’t relevant. You might as well be explaining the nuances of brain surgery.

Wha-wha-wha-what? Please, allow Mr. Hockenberry to continue:

Twitterrific on the iPhone could definitely make use of a background process to gather new tweets. In fact, a prototype version of the software did just that. And it was a huge design failure: after doing XML queries every 5 minutes, the phone’s battery was almost dead after 4 hours. In fact, the first thing I said after giving Gruber this test version was “don’t use auto-refresh.”

Hockenberry goes on to discuss the power demand problem of the radios, both EDGE and Wi-Fi, and the danger of even well-intentioned developers getting individually reasonable but collectively overwhelming access to background services. He does, however, expect that in a future release Apple may include some method of notifying network apps that the radios are being used (for example, by MobileMail Touch), and allowing brief TCP/IP connections during that period. Bottom-line, at the OS’s discretion, not the individual apps’.

Sound reasonable? Sound crazy? Should Apple give unfettered access to everyone immediately an trust users to sort through it themselves? Or should Apple be as strict as possible from the get-go? What do you think?

Developers want them their multitasking. They want them popping up, one after the other, like Agent Smith replicants in the Matrix sequels. What? Viruses incarnate from poorly conceived follow-up movies is a bad analogy?

Not according to some leading Apple pundits.

Witness Daniel Eran Dilger’s iPhone 2.0 SDK: The No Multitasking Myth from Roughly Drafted Magazine:

By limiting the amount of background processes running, the iPhone’s OS X can offer more of that available RAM to the foreground application, along with a less distracted processor. The iPhone is not a general purpose computer; it is primarily a phone, browser, and iPod. Due to the restrictions imposed by the SDK, it will also be a credible gaming platform and pack the power to run significant productivity applications, all without giving up the ability to be a responsive phone, browser, and iPod. Other devices can’t make that claim.

Sure, Dilger is sometimes considered on the extreme-end of Mac’tivism. Let’s see what Daring Fireball’s John Gruber has to say when he takes on One App at a Time:

Why has Apple imposed this limitation? Easy: the iPhone is severely resource constrained. Battery, RAM, and CPU cycles are all severely limited. If third-party apps could run in the background, all three could suffer. RAM would suffer for sure; all running apps consume memory. The iPhone has just 128 MB of RAM, and no swap space. CPU performance and battery life would suffer when background apps do something — and if they’re not doing anything, what’s the point of keeping them running? I noticed a significant increase in battery life after I switched the Mail app’s auto-checking interval from 15 minutes to 60 minutes. That’s just one app.

Okay, but they’re not developers. They don’t understand the needs, the passion. But then developers aren’t pure consumers either and developers don’t always understand consumer needs. Sometimes developers are so busy with the abstract coolness of what they can do, they don’t always stop and consider the colder reality of whether they should.

For every OS-changing Switcher app, there are dozens of buggy, crash-inducing WinMob and Palm fetishware. (As I can personally attest to, when even major apps from major developers rendered my Treo unusable).

No developer goes out there with ill-intent (malware aside), but their concern is app-level, not device or OS level. That’s where Apple comes in. The overall user experience isn’t the developers concern, nor should it be. It’s Apple’s concern, and right now Apple is imposing that concern via no-multitasking guidelines.

Note: John Gruber, quoting Hank Williams, also gives us The Flip Side of the Multitasking Argument. (Hit up the Roughly Drafted link above for some excellent back-and-forth between Williams and Dilger in the comment section as well.)

UPDATE: Gruber follows up in Foot, Meet Bullet, a point-counterpoint with Ian Betteridge.

What do you think? Is the ban on multitasking good or bad for the general user-base (i.e., our moms!)? For power users? Will Apple make exceptions for certain big developers (like AOL for AIM)? Will they relax the policy after the initial development rush is over, the space shakes out, and only cooler, more seasoned and reasoned heads remain in the game? Will some crafty devs will figure ways around the rules? (creativity thrives under constraint!). Or will things just stay the way they are?