I’ve wondered the same many times. Most apps are smaller than a typical MP3 — and yet it takes probably 10 times as long to install an app than it does to copy over a song. Why? Visit site »
Apparently is prototyping elements day on jeffcroft.com. Here’s an awesome-looking PSD full of iPhone widgets. Via Wilson. Visit site »
Steven has a great piece on how the iTunes App Store is simultaneously the best mobile application distribution platform ever and downright scary for developers who want to make their stuff available from it. Visit site »
John Allsop wonders aloud whether or not most iPhone native apps should be web apps, instead. Although I don’t really share John’s lack of enthusiasm for native iPhone apps in general, I definitely think he has a point. Many of the best apps on the iPhone are simply interfaces to web content. Many of them don’t offer any real advantages over a similar web app. Developers would be wise to still consider the web app direction as a possibility, unless they specifically need to access native functionality such as the camera or location data — web apps are more compatible, more distributable, and arguably easier to develop. Visit site »
Kevin from howiworkdaily.com had my good friend and design hero Nathan Borror on the line for a 30 minute podcast. They two discuss Django, Basic Apps, playgroundblues.com, the iPhone, and more. It’s a really good listen.
I’ve said it before, but I’ll take the opportunity to say it again: Nathan Borror is absolutely the most underrated web professional on the Internet. He’s quite possibly the most talented person I’ve ever worked with. His attention to detail and breadth of knowledge across all aspects of web work is surpassed only by his sympathy for the user. I know just about every amazing designer in this industry, and Nathan would still be the first person I’d call if I were hiring.
And, he’s a great fucking guy, too.
(Nathan, you owe me dinner, or something.) Visit site »
Apple has publicly apologized for the disaster that was the MobileMe launch, as well as the misleading use of the word “push,” and given subscribers a free 30-day extension to their service. A nice gesture for what was, indeed, an ugly string of screw-ups. I especially like the letter’s copywriting: no-bullshit, sincere, to the point, and personal. We all know a lot of companies would have taken a “our Terms of Service clearly indicate that we can not guarantee our services,” sort of approach. Well-done, Apple.
Now that things are running smoothly, I’m really liking MobileMe a lot. Not having to put my iPhone in its dock all the damn time to ensure I’ve got my latest contacts and calendar events on all my device is really a sweet thing. There’s no doubt this is a better service than .Mac for iPhone owners. I’m not sure it’s an improvement for those who just want to keep multiple Macs in sync — but, whatever. Visit site »
A nice looking blog about iPhone/iPod touch gaming. Visit site »
Turns out, MobileMe doesn’t “push” changes to calendars and contacts made on your Mac to the Me.com web apps and your handheld devices. From an Apple Knowledgebase article:
Changes made on your computer will be synced to the MobileMe “cloud” once every 15 minutes (or every hour in Mac OS X 10.4.11).
Changes to calendars and contacts made on Me.com or on your iPhone will be pushed to your Mac immediately, but the reverse is not true. Strange. From Apple’s MobileMe features page:
MobileMe stores all your email, contacts, and calendars in the cloud and pushes them down to your iPhone, iPod touch, Mac, and PC. When you make a change on one device, the cloud updates the others. Push happens automatically, instantly, and continuously. You don’t have to wait for it or remember to do anything — such as docking your iPhone and syncing manually — to stay up to date
Emphasis mine. For many people, including me, a 15 minute sync time is probably just fine in real-world usage. But, it definitely seems contrary to how the service was promoted and demoed at the WWDC keynote, and I can definitely understand why so many people are complaining about it on the MacRumors forums and across the Internet. This sort of reeks of deception.
A couple things worth pointing out about this, for those wondering why it’s a big deal:
In which I note that Apple’s new MobileMe service doesn’t work with subscribed calendars like its predecessor, .Mac, did.
According to a growing number of people on Twitter, Apple is having problems with its in-store activation process. Couple this with the botched MobileMe rollout, and this launch isn’t looking good for Apple right now. Here’s hoping they get it all resolved in short order.
It’s now been 24 hours since the start of the six-hour downtown window Apple gave for the .Mac to MobileMe migration. I’m frustrated. A lot of people are frustrated. But a lot of other people, in forums around the Internet, are saying, “Oh, get over it. You’ve waited this long for MobileMe, you can wait another day or two.” Those people are missing the point. I pay for .Mac, and I rely upon its services (notably Sync, Back to My Mac, and iDisk). I’m not upset that MobileMe isn’t ready yet; I’m upset that Apple has taken away my .Mac services. MobileMe can take six months for all I care, but I need my syncing and iDisk.
Apple has another problem at play, too: a lot of the hype surrounding the new iPhone 3G is directly related to its integration with MobileMe. The iPhone went on sale hours ago on the other side of the world, and will go on sale in less than 10 hours here in America. If the push e-mail, contact, and calendar functionality Apple has been hyping for the past couple months isn’t available when these people get their iPhones home, the media is going to have a fucking field day — and RIM’s stock is going to look pretty darn good.
Update: Media frenzy has begun. AP article on .Mac/MobileMe transition woes. And a new article on ComputerWord. Visit site »
The Brightkite team says their native iPhone app will be out by the end of the month. Great news, because so far, I’m not very impressed with Loopt or Whrrl. Brightkite’s iPhone web version defeats both by a long, long longshot. Visit site »
Ever since I tweeted that I have installed iPhone 2.0 and downloaded apps from the app store, I’ve gotten countless IM’s, DM’s, and e-mails asking me how. It’s been all over the Internet all morning, so it’s no secret, but Wired has now published a comprehensive, step-by-step guide that is probably the simplest to follow that I’ve seen. So, get on it. Visit site »
Short story: the Samsung Instinct on Sprint is the best “iPhone killer” made to date, and it also happens to b the cheapest (at just $129, after this week’s price reduction to compete with the iPhone 3G). Being from the Kansas City area (where Sprint is headquartered), I know a lot of people locked into Sprint contracts. While it’s still not an iPhone, the Instinct does seem like a solid buy for someone stuck on Sprint — especially at just $129.
All that having been said, I sort of suspect phones like the Nokia N95, Samsung Soul, and Garmin Nuviphone are more likely to take business away from the iPhone — even if they’re not as directly positioned to compete with it. Visit site »
Gruber walks through the “should I upgrade to the new iPhone,” dilemma, one I’m currently having, myself. He correctly points out that the only real noteworthy advantages are faster networking and GPS. He doesn’t mention the flush headphone jack, which isn’t a big deal to me personally (I’ve already gone and bought V-Moda iPhone earbuds), but may be to some audiophiles who’ve been avoiding the iPhone because they can’t use their favorite headphones with them.
For me, I think it’s going to boil down to this: Will the location-based SDK apps work with the triangulation functionality of the original iPhone, or will they require GPS? And if they do work: how well? I’m excited about the location based services more than the 3G networking, myself. If these work reasonably well on the original iPhone, then I may not have much incentive to upgrade this time around. Visit site »