All Articles Tagged sdk

Monday we asked you “What’s the iPhone 3G Chip and When Will it Ship?“. Tuesday it was “What is the iPhone 3G Going to Look Like?“. Wednesday brought “What Surprises Will There Be in the iPhone 2.0 Software & Services?” Today we want to know what 3rd party iPhone SDK Apps might be ready to download come launch day?

EA, Salesforce, AOL, Sega, and a noble few were right there at the beginning, and since then dozens if not hundreds of others have been rumored if not confirmed, including titans like Microsoft, Sun, and Adobe. But who will be ready come game (and business!) day? Bioshock? Documents2Go? SlingBox? Flash?! What do YOU think?

To give you some help, here’s a HUGE roundup of all the iPhone SDK 3rd party apps rumors. Epic-style. Because let’s face it, roughly 0.01 seconds after Steve Jobs pulled the first iPhone from his pocket back at Macworld 2007, and someone, somewhere, put aside their childlike sense of wonder long enough think: “Nice! What’s the next gen going to be like?”

Complementary, contradictory, obvious, confusing, all but confirmed or from left field via outer space, the rumors have flooded the internet ever since. It’s become almost impossible to keep track of them all.

Four days from today Steve Jobs takes Moscone Center stage for the sold-out WWDC keynote, and according to everyone and their newsfeed, announces the iPhone 3G. In eager anticipation, every day this week, TiPb wil be asking you to tell us what you think the next generation iPhone will be, from 3G to GPS, release dates to price points, colors to casings, 2.0 software to .Mac .Me services, and this weekend we’ll wrap it all up with a look into the WWDC/iPhone 3G Crystal Ball, and a roundup of the very best of YOUR predictions.

So come on, let’s get in on!

Read the rest of this entry »

Apple has just dropped the sixth (6th!) update to their iPhone SDK and 2.0 beta firmware. Pre-req is Apple’s almost simultaneously dropped OS X Leopard update, 10.5.3, so developers are forewarned to get that first before beginning the SDK install.

No word yet on what new treasures may be hiding in this version, but if past betas are any indication, there’ll no doubt be something hidden in them there strings

According to TUAW, however, Apple is now carding. Yup, they’re checking Application IDs at the door, so make sure you’re registered before you try to install apps on a test iPhone.

Head on over to Apple’s iPhone DevCenter to get yours now!

A New Version of the iPhone SDK is Now Available Sixth beta version just posted.

Via

Want to develop apps for the iPhone? Sad that WWDC is sold out? You’re just in luck, the iPhone Dev Camp 2 is scheduled for August 1-3, 2008 in the Adobe Systems offices in San Francisco, California. A follow up to the original iPhone Dev Camp with one obvious new twist, the SDK.

A not-for-profit effort focused on the development of apps on the iPhone, it also hopes to migrate Mac OS X apps to the iPhone. Though they are well aware of the NDA that Apple has in place on the iPhone, they are hopeful that Apple will lift the NDA after the public launch of the App Store.

Over that August weekend, Cocoa Touch developers, web developers, UI designers, and testers will be working together in app development. If you are interested in attending the project, feel free to click the Read Link!

Read

Ask and ye shall receive, dig deep into the code and ye shall find fresh-baked Apple-y goodness.

No sooner did Apple drop iPhone 2.0 SDK Beta 5, than the developers began scouring it for any hint of what’s to come, and as usually TUAW serves up what they found:

A certain, unnamed individual sent us some pictures of the latest build of the iPhone firmware showing .Mac push e-mail. The picture shows the main Settings page with a new button: “Fetch new data.” When you click the button, you are taken to a list of your mail accounts, where you can choose between either “fetch” or “push.” According to Mr. Anonymous, while .Mac is offering push e-mail, you are currently not able to do contact or calendar syncing.

Check out TUAW’s gallery for the pics.

Boy, Apple is pushing the features fast and furiously. We already knew about “push” via the Microsoft licensed ActiveSync, which offers full Exchange support, but complementing that with .Mac for non-Exchange users? Very nice!

(Of course, much as I love Back-to-My-Mac, iSync, iDisk, and other .Mac features, it really needs a more competitive feature-set upgrade — Imagine Google-like offerings and capacities with Apple’s ease of use and integration! — especially for the rather steep $100 a year.)

June really can’t come fast enough!

TUAW and iPhone dev extraordinaire Erica Sadun reports that Apple has dropped the svelte-ish 1GB iPhone 2.0 SDK Beta 5 and accompanying firmware:

The fifth beta version of the iPhone SDK is now available. Log in to the iPhone Dev Center and take advantage of all the development resources available to you—a new version of the iPhone SDK, updated documentation, the latest release notes, and more.

No word yet on what secrets deep delving this latest code may reveal, but if past discoveries are any indication, literally anything is possible (except for cut and paste, of course).

Any guesses?

John Gruber and the Macalope have made an artful science out of reasonably, logically, and methodically skewering the most pathetic punditry and junky journalism surrounding Apple and the iPhone.

Case in point is Gruber’s recent and rather succinct dismantling of Simon Brocklehurst’s complaint that Apple chose Objective C as the language behind the SDK. And while he certainly doesn’t need my help, there are a few points I’d like to add.

First, anyone (but especially Simon) who thinks Apple just now (or even recently) decided to create an SDK for the iPhone knows little about SDKs and less about the polish and maturity easily observed in even the beta SDK Apple released at their special Roadmap event. The briefest look at actual developer blogs and tweets — including developers with substantial experience in jailbroken iPhone apps — would see the flood of remarks on the maturity of the beta SDK. Bottom line, if Apple hadn’t been planning the SDK for a long time (perhaps since the launch itself) they have a hidden supply of killer engineers capable of truly mind-boggling delivery.

Second, I’m going to go out on a limb and guess that, while I don’t know anything about Brocklehurst’s background, quoting Jonathan Schwartz indicates some level of Java-centricity. By serendipitous contrast, I just this week had a conversation with a developer at work who was being brought onto a new project. Since he’d recently done a lot of C++ and PHP, he was looking for a new language with which to stretch his skills. He wanted to try Ruby or Python, wanted to see what Rails could do. Gruber’s right, good programmers can (and want to) program and can (and want to) stretch themselves to do it (even when it’s not so far a stretch). Good programers who want to make good iPhone apps won’t think twice about adding Objective C to their skill set.

Third, the iPhone/iPod halo is clearly helping Apple gain traction in their Mac market, and there’s no reason to think the iPhone SDK won’t help Apple gain traction for Objective C and Cocoa via Cocoa Touch. Apple has shown time and time again — to the point of frustration on some occasions — that it is a future thinking company. Getting a bunch of convenience-oriented programmers now by putting out a Java or C++ iPhone SDK pales to insignificance when compared to the mindshare Apple could gain by delivering a powerful, delightful Object C/Cocoa Touch development environment (and experience) to the uber-keen developers of the next generation, whose newfound skills — and more importantly, tastes — will flow right back into the Mac and future Apple products.

While Apple certainly fumbles the ball on occasion, this time they look to be smashing their way clear to a touchdown.

Sorry Simon.

Daring Fireball, via Digital Arts, brings word that Sun hasn’t stopped trying to bring a Java Virtual Machine (JVM) to the iPhone even though:

Apple has not been publicly receptive to having Java on its popular new device. There have been questions about whether Apple’s iPhone SDK agreement would permit this. The JVM potentially could sidestep Apple’s App Store program for dispensing iPhone applications.

And while Sun’s efforts continue, they’re also hedging their bets with Innaworks, who produces alcheMo, which may let Java programs compile as native iPhone apps, ready for App Store:

[I]nitially targeted at games publishers. Now in a beta release, alcheMo for iPhone can be used to port Java ME mobile games to iPhone and iPod touch without the need for further manual adjustments. The product features an optimizing translator to convert Java ME application source code to equivalent source code for iPhone, according to the Innaworks press statement on the product.

While Apple’s Cocao Touch development sounds like a more chocolaty, and much sweeter beverage than Java, Sun sure does seem determined. Of course, determination has a tendency to crash and explode in Matrix-like bullet time when it strikes up against the Zen-like immovability of one Steven P. Jobs.

I don’t think we’ll be seeing the steaming coffee mug on the iPhone any time soon. You?

No reports of Pink Screens of Death this time, but Apple has released the fourth version of their SDK (5A258f), which weighs in at a beefy 1.15GB (200+MB for firmware) and according to TAUW (via Apple Developer Connection) sports:

Xcode IDE, iPhone simulator with Open GL ES support, Interface Builder, Instruments, frameworks and samples, compilers, and Shark analysis tool.

In addition, code-signing is now enforced, Audio Toolbox was big-upped, NSXML parser was introduced, fonts were given some pro love, and — teasingly — the UIApplication delegate class is now rumored to have Springboard Icon badging and some way to get and release “active status”. TAUW speculates this may allow some form of background functionality for Apps! (Wishful thinking?)

Go get ‘em developers. Especially you deep-code-digging developers who find all sorts of goodies hidden in the strings.

After waking up on Tuesday to face the dreaded Blue– er… Pink-Screen-of-Death (?!) that signaled the expiry of the 2nd beta release for the iPhone SDK, would-be-developers managed not to go to bed angry as Apple kissed and made-up in the form of SDK Beta 3.

Erica Sadun over on TUAW reports that the latest/greatest weighs in at 1.4GB, or just three-quarters the size of the original beta, with the matching firmware at under 200MB according to a commenter.

What new goodies does this release hold? We’ll have to wait a bit to find out. But with the continual slow, grinding, excruciating march towards an anticipated June release (WWDC? June 30 at 11:59 pm? Little help?) waiting is something iPhone lovers are used to.

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?