Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

Thursday, 08 April 2010 11:52

iPhone OS API controversy reignited by iPad developer

By

A fresh round of controversy has exploded concerning the way Apple forbids third-party developers from using private APIs in iPhone OS.


Apple's software development kit (SDK) for the iPhone, iPad and iPod touch describes a wide variety of APIs (application programming interfaces) that expose functions and features to developers.

But if developers try to use undocumented (aka private) APIs, the resulting applications will most likely be rejected by the App Store approval process. About the best outcome developers can hope for is "OK, but make sure you remove that in the next version."

The latest round of controversy was sparked by an observation by Marco Arment, lead developer of Tumblr and Instapaper, that the iBooks app uses private APIs, including one that provides a true brightness control.

Arment's concern is that "I won't be able to offer some features that iBooks has (such as a true brightness control), but my customers will expect them, making my app inferior to Apple's in key areas."

Consequently, Apple's apps would be advantaged over third-party products in the same segment. But as Arment noted, the Pages, Keynote and Numbers apps reportedly do not use private APIs, so it doesn't seem as if the company is seeking an unfair advantage.

So why do private APIs exist in iPhone OS? And why doesn't Apple want third-party developers to use them? Please read on.




Private APIs are by definition those that the platform owner doesn't want outside developers to use. The main reason is that some features are only half-baked, and therefore subject to change.

APIs are essentially contracts between their provider and developers. The deal is that developers can write to APIs, confident that the functions will continue to work even if the provider makes under-the-hood changes, and that the API won't vanish without an extended period of notice.

So a provider such as Apple doesn't want to make an API public until it is confident that the interface is stable and can accommodate likely changes in underlying functionality.

If Apple's about anything other than making money, it's about the user experience. And you don't deliver a good user experience if applications have to be updated just to keep working with every new OS release.

History suggests that Apple does progressively make more functionality available via public APIs. For example, iPhone SDK 3.0 made it possible for apps to access the iPod library. And when 3.1 arrived, it provided a way to superimpose graphics on a live video stream from the camera.

Arment's suggestion that "Ideally, Apple should only publish first-party App Store apps that would be approved if they were submitted by a third party, and they should therefore use no undocumented or prohibited APIs" is clearly - and understandably - looking at the issue from the perspective of a developer, not an end user.

What might Arment's idea mean to those end users? Please read on.




If we look at the specific case of iBooks being able to control the screen brightness, would you (as an iPad owner) prefer that this feature had been omitted from the app until Apple was satisfied of the API's stability and was ready to open it to all comers? Probably not.

And even if Apple did adopt Arment's suggested policy, it would still have an easy workaround available - simply deliver iBooks as a 'built in' iPad application rather than leaving it to owners to download the software from the App Store.

Those in Arment's camp might argue that the long term benefits that will accrue from more level playing field (in the context of Apple vs all other developers) will outweigh any short-term loss of utility. Others might adopt the attitude that 'in the long run we're all dead.'

And trying to draw parallels with anti-trust actions against Microsoft (and this is something that Arment brought up) are misplaced. Central to the case against Microsoft was its overwhelming market share.

Popular as the iPhone is, BlackBerry is still the leading smartphone in the US. And not even BlackBerry accounts for the majority of smartphones in use in that country.

While it's reasonably obvious that the fewer private APIs the better, expecting platform vendors not to use them doesn't make much sense.

If a tree falls in a forest and no one is around to hear it, it does not make a sound - sound (as opposed to vibration) requires a listener. And an interface that no application is allowed to use can hardly be called an API.

 


Subscribe to ITWIRE UPDATE Newsletter here

PROMOTE YOUR WEBINAR ON ITWIRE

It's all about Webinars.

Marketing budgets are now focused on Webinars combined with Lead Generation.

If you wish to promote a Webinar we recommend at least a 3 to 4 week campaign prior to your event.

The iTWire campaign will include extensive adverts on our News Site itwire.com and prominent Newsletter promotion https://itwire.com/itwire-update.html and Promotional News & Editorial. Plus a video interview of the key speaker on iTWire TV https://www.youtube.com/c/iTWireTV/videos which will be used in Promotional Posts on the iTWire Home Page.

Now we are coming out of Lockdown iTWire will be focussed to assisting with your webinatrs and campaigns and assassistance via part payments and extended terms, a Webinar Business Booster Pack and other supportive programs. We can also create your adverts and written content plus coordinate your video interview.

We look forward to discussing your campaign goals with you. Please click the button below.

MORE INFO HERE!

INTRODUCING ITWIRE TV

iTWire TV offers a unique value to the Tech Sector by providing a range of video interviews, news, views and reviews, and also provides the opportunity for vendors to promote your company and your marketing messages.

We work with you to develop the message and conduct the interview or product review in a safe and collaborative way. Unlike other Tech YouTube channels, we create a story around your message and post that on the homepage of ITWire, linking to your message.

In addition, your interview post message can be displayed in up to 7 different post displays on our the iTWire.com site to drive traffic and readers to your video content and downloads. This can be a significant Lead Generation opportunity for your business.

We also provide 3 videos in one recording/sitting if you require so that you have a series of videos to promote to your customers. Your sales team can add your emails to sales collateral and to the footer of their sales and marketing emails.

See the latest in Tech News, Views, Interviews, Reviews, Product Promos and Events. Plus funny videos from our readers and customers.

SEE WHAT'S ON ITWIRE TV NOW!

BACK TO HOME PAGE
Stephen Withers

Stephen Withers is one of Australia¹s most experienced IT journalists, having begun his career in the days of 8-bit 'microcomputers'. He covers the gamut from gadgets to enterprise systems. In previous lives he has been an academic, a systems programmer, an IT support manager, and an online services manager. Stephen holds an honours degree in Management Sciences and a PhD in Industrial and Business Studies.

Share News tips for the iTWire Journalists? Your tip will be anonymous

WEBINARS ONLINE & ON-DEMAND

GUEST ARTICLES

VENDOR NEWS

Guest Opinion

Guest Reviews

Guest Research

Guest Research & Case Studies

Channel News

Comments