The first thing I thought when I saw that the C64 emulator we posted about the other day still had the BASIC interpreter hidden in it was, "Well that won't last." And unfortunately for fans of software emulation on the iPhone, I was right: the software got pulled from the App Store but quick. You can't really blame Apple here -- they've made it pretty clear that they don't actually want people running unlicensed, emulated code on the iPhone, so it's not hard to see why, when it was discovered you could still activate the interpreter, they cleared it out of the store.

The good news is that the emulator has been updated to delete the interpreter completely, and the owners of the software have resubmitted it yet again to the App Store. But as much as I enjoy seeing emulators on the iPhone (I've made it very clear I'd love to see an official NES arcade app), I can't say I'd blame Apple for just passing on this one outright. They've had to go through this app at least twice now, and especially since app approval is already taking so long, that's pretty much a waste of time. Mistakes like leaving the BASIC in the app (Edit: My mistake -- they intentionally left it in and hidden, with the expectation that Apple would later allow it. Doesn't seem very likely.) are making it much easier at this point for Apple to just say "no emulators, period," and move on. Hopefully this app will get re-approved, and that'll be the end of it.

Well how about that. A Commodore 64 emulator for iPhone is nothing new -- we covered the fact that one had been developed a little while ago. Here's what is new (and a little surprising, to be honest): Apple approved it. In an environment where Apple seems intent on rejecting anything that might encroach on their platform, even just a little bit, they have apparently allowed an emulator right there on the App Store.

There are catches, of course -- the emulator comes bundled with five officially licensed titles: Dragons Den, Le Mans, Jupiter Lander, Arctic Shipwreck and Jack Attack, and more will be available to purchase soon, so it'll all be above board and legit (and the flip side is that if you want to play classic titles like Elite or Ultima, you'll have to hope that whoever owns the rights to those will let them see release). The biggest catch is that the emulator doesn't come with BASIC support enabled by default (although, via Daring Fireball and the iPhone Blog, it's possible to get to it via a backdoor), so it's more of a C64 arcade emulator rather than an actual software emulator.

But of course this is a step in the right direction -- someday we may finally see official SNES or NES emulators running in full glory on the iPhone and approved and available to purchase on the App Store. This emulator, simply called C64, is available right now on the App Store for $4.99.

Update: This app has been removed from the App Store because it was possible to enable the BASIC program. Look for it to return without that functionality.

I didn't really take last week's Twitocalypse that seriously, but as you probably know by now, it turned out a little worse than expected -- we'd been told that Twitterrific (and, we assumed, most other Twitter apps) would be fine, and of course, as Craig Hockenberry explains on his blog, things ended up not-so-fine. Desktop app developers, of course, could publish updates as quickly as they could code them; iPhone developers were in a different situation.

When the Iconfactory's app stopped working, most people (including me) got an API error all weekend. Craig found the bug, then he and his team were able to leverage their contacts at Apple Developer Relations to help expedite the release; in short order, an update was pushed out to the App Store. I downloaded it yesterday, and can tell you that things are fixed... at least until the numerical limit on Twitter's tweet identifier raises its head again (or the Newton flips out, but that's another story).

Hockenberry also has ideas about how to keep issues like this from happening again. Not the actual issue of a variable overflow (that will undoubtedly happen again at some point, on Twitter or any other API that scales way faster than anyone expects it to), but the issue of iPhone apps needing a quick fix. He says that Apple should give every developer a number of "incidents" -- situations rarely used, in which a high priority fix can get sent out to apps in major emergencies. He says, and it's true, that for most developers, it's not a question of if you'll need to send out a critical fix, it's a matter of when. And support by Apple, obviously limited to one or two instances per developer, would help developers, distributors, and consumers.

Of course, it's up to Apple, and it's not like they've smoothed out the approval process so well already that they can start adding wrinkles to it. But clearly, given that the Twitterrific update went through quickly, there's room for exceptions to be made.

[via DF]

Jonathan Zdziarski, who has appeared on this pages before for other iPhone-related hijinx, has written an open letter to Apple about the AMBER Alert iPhone app he's written. Apparently he's worked in conjunction with government agencies to set up an iPhone app that can easily and quickly send sighting reports of children gone missing in the United States. And he's unhappy with Apple, because they haven't yet approved it.

His letter, which you can read in full over here, complains that we've got tons of fart apps already approved on the store, but his app still sits in approval purgatory. He actually sounds kind of selfish in the letter to me -- he says he doesn't care about how the App Store works, and that he just wants someone to "pick up the phone" and push his app, which could save children's lives, through.

We've got nothing against the AMBER Alert system, of course, and if it's true that this app can get more reports in and possibly help kids who are in danger, then great. But do we really want Apple picking and choosing which apps get kicked to the front of the line?

Update: looks like the app has been approved. The question remains: what was the holdup?