All Articles Tagged developers

Tim Cook (in)famously said other platforms and devices are still struggling to catch up with the original 2007 iPhone 2G, and while TiPb wouldn’t go that far (the App Store didn’t show up until the iPhone 3G in 2008), strictly in terms of user experience and functionality, he may have had a point.

First up, Jamie Zawinski (jwz) has abandoned the Palm Pre and gone all in on iPhone, despite Apple being worse than Palm when it comes to developer relations and closed ecosystems. Why? “Because it just [redacted] works.” He highlights Mac sync, but especially performance as key. Long delays in being able to use the Pre calendar, phone, and camera apps are especially irksome.

I don’t expect the performance of this phone to be even remotely suitable for every day use for at least a year. I figure it’s going to either take a substantial amount of work on the lower levels of the OS, or they’re going to have to throw Moore’s law and new hardware at it…

Next up, Steven Frank, who abandoned the iPhone after the Google Voice incident, and returned to it when he couldn’t find happiness with another device, nails why that’s still the case some 2 years later:

It’s not just that the iPhone has fancy woo-woo transitions and purty graphics; it runs all the way down the software stack. For example, when I tap on something, I don’t have to hover for five seconds wondering “now did it get that tap, or do I have to do it again?” This is something other platforms are still struggling with. When we say you have a bad experience, this is the sort of thing we mean. It has little to do with features, and everything to do with core functionality.

Lastly, Daniel Pasco offers a theory as to why — Apple spent years and a fortune figuring out the iPhone:

Because of that effort, since the iPhone was released, everyone else has been struggling to play catch up, and no one has really come close. Apple raised the bar higher than anyone else had before, and by the time the competition realized how much of an effort would be required to seriously compete, the public had already turned to them to see how they would meet Apple’s threat.

Spending 2.5 years in secret, and who knowns how many of those billions, and then unleashing the iPhone 2G multi-touch user interface changed the game in 2007, and more — it forced competitors to play catchup in public. Sure, many have the iPhone now to copy, but Apple has the momentum to keep innovating.

The question is, can incredibly rich companies like Microsoft, and amazingly innovative ones like Palm — or Google which is both — bridge that gap at the core functionality and user experience level?

[via Daring Fireball]

Dan Moren of Macworld has an interesting post up about this year’s C4 Independent Developers Conference, and how the indie devs seem to have cooled towards iPhone development and turned their attention back to the Mac. Why? Not the technology, of course. They’re up on the handset and almost everyone had at least one. No, it was dissatisfaction with the state of how Apple runs the iTunes App Store, of course.

Lack of control over elements like release times was cited as one issue. Profitability, another:

The problem is that the prices in the App Store, which tend towards the lower end, make it harder to recoup the investment put into developing the program in the first place. Sure, there have been over two billion downloads from the App Store, but remember there’s more than 85,000 apps available. Even if your 99 cent application gets downloaded 10,000 times, after Apple’s 30 percent cut that’s just $7,000 in revenue—not profit, mind you, just revenue—and if you spent the last six months of your life working on that application, you better hope you’re still working a day job if you want to cover living expenses.

Rather than abandoning the platform, however, some devs had suggestions for how Apple could help make things better, including upgrade pricing (to avoid Tweetiegate situations), creating a mechanism for demos, and something we’ve heard before from Craig Hockenberry — having a higher-priced developer account option that comes with a better service level from Apple ($999 platinum account, for example, in addition to the current $99 version).

With the current volume market, Apple may not care since they’ll make their 30% off Apps and CrApps alike. But here’s hoping their pride wins out, and Apple decides they don’t merely want the most successful App Store, but the very best one as well — for users and developers.

Apple has begun emailing registered developers with the following:

As a developer actively working with iPhone OS 3.0 beta, we would like your help in testing the Apple Push Notification service. We have selected a pre-release version of the Associated Press app for iPhone OS 3.0 to create a high-volume test environment for our servers.

Great move on Apple’s part, provided they recruit enough developers to really test the scaling of their iPhone 3.0 Push Notification system. After last year’s disastrous MobileMe launch, Apple needs to make sure their infrastructure is as bullet-proof as possible before they pull the push lever… even if they are planning some limited multitasking as well…

Full text after the break:

Read the rest of this entry »

Ars Technica reports, with some very nice commentary and screen caps from Equivalence (iTunes link) for iPhone, that:

One of the most requested features from developers, automated crash reports, can now be submitted by users via iTunes 8.2. Developers can access the reports via iTunes Connect.

No code is ever perfect, but anything that helps developers make their apps more solid for more users is certainly appreciated.

Apple has gone out of their way to point out the cons of multi-tasking background applications — a claimed 80% reduction in battery life while on standby with a single 3rd party IM client enabled. Push Notification, likewise, has been promoted by Apple as providing a single point of coordination for 3rd party alerts routed through servers on Apple’s end.

But unlike the code-once, release-done model of background processing for a single app, Push Notification requires developers to create a server system on their end as well, one that’s constantly and reliably available to send alerts to Apple, and scales to an iPhone and iPod touch user base already exceeding 30 million units.

Ars Technica’s Erica Sadun goes into detail on the process and problems:

Consider an application with just 10,000 users. It might service a million uses per day, assuming update checks every 15 minutes. More time-critical uses might demand checks every few minutes or even several times a minute. As the computational burden builds, so do the hosting costs. While cloud computing provides an excellent match to these kinds of needs, that kind of solution comes with a real price in development, maintenance, and day-to-day operations.

For more on additional issues, like security, and whether or not small developers will even be able to afford to implement Push Notification, check out the rest of the article.

Any developers out there avoiding Push Notification for just those reasons? What could Apple do to help you out? Offer a hosting system for small developers on Apple’s end?

Apple has just let developers know that they can start testing the upcoming Push Notification Service starting today!

Start testing your applications using the Apple Push Notification service today. Log in to the iPhone Dev Center and review the Apple Push Notification Programming Guide and Getting Started video. Team Agents can log in to the iPhone Developer Program Portal and proceed to the App ID section to create the components necessary to enable and test applications using the Apple Push Notification service.

So, what Apps do we want to see getting pushy? Twitter clients? Instant messengers? Fart Apps? Let us — and your favorite developers! — know.

Following hot on the heels of last Tuesday’s monster iPhone OS 3.0 announcement, Apple wants developers to know that there’s never been a better time to develop for the iPhone:

With a rich set of over 1,000 new APIs, iPhone SDK for iPhone OS 3.0 beta provides you with an amazing range of technologies to enhance the functionality of your iPhone and iPod touch applications. New APIs also provide support for applications to communicate with hardware accessories attached to iPhone or iPod touch.

Any devs previously sitting on the fence finally decide 3.0 is finally enough to push you over?

The Situation: Developers who signed up for Apple’s iPhone SDK Beta and iTunes Connect program last year are coming up on their 1 year renewal deadline.

The Problem: Apple has no mechanism in place to handle such renewals.

The solution: Er… there is none — yet. But in the meantime, Ars Technica’s Erica Sadun reports:

Apple has now e-mailed iPhone developers to extend their memberships until July 11, 2009. A short-term solution to the problem is good, but it shows that Apple is still working out the longer-term details.

Here’s hoping them details get worked out soon rather than later.

Almost a year ago, Apple held their iPhone SDK Roadmap Event and unleashed the App Store concept on the world. Developers signed up for iTunes Connect contracts, and now their first year is almost up and they need to renew.

One problem: Apple doesn’t yet have a renewal process in place.

Wha-wha-wha-what? Erica Sadun over at Ars Technica (following an article in Apple Insider) looked into it and found the right side of the Apple didn’t seem to know from the left:

When we explained that we were looking both to renew ADC memberships and to update iTunes Connect contracts, the representative instructed us to send a query to devcontracts@apple.com. [...] We did in fact contact the iTunes Connect e-mail address, who wrote back to us saying, “Please refer to the Contact Us links at the bottom of iTunes Connect. devprograms should be able to assist you.” Apparently 1 Infinite Loop does not just refer to a corporate street address.

Yikes! Hopefully — for the sake of developers and those of us who want to continue seeing apps in the App Store — Apple will sort this right quick.

Any developers manage to get a better answer from Apple?

More pics from yesterday, enjoy!