Feeds

Dilemma meets opportunity: iPhone beta SDKs in review

Will you tread the Cupertino path?

Using blade systems to cut costs and sharpen efficiencies

As you'd expect, this sort of restriction is like a red rag to a bull as far as the open source community is concerned. Allegedly, the key needed to get the firmware to give the thumbs up has already been posted on the net, but as far as I can see, it's just a decryption key for IPSW firmware updates, which is quite different. One thing's for sure: Apple will change the key before the official release in a couple of months' time, so it doesn't much matter either way.

I believe that the upshot of all this will be fragmentation. On the one hand, we'll have the official developers selling their Apple-approved products through App Store. These programs won't be able to fully leverage the power of the platform because Apple won't let them. One of the bits of small print in the iPhone developer agreement is that you can't use undocumented APIs, which immediately gives Apple a big advantage over third-party developers.

Unofficial challenge

On the other hand, we're going to see the so-called "Open Source tool chain" - again, see my previous article - becoming increasingly popular in the shareware community.

Unlike the official route, this approach will give you access to all the available APIs (read that as more efficient and more capable applications) and a more traditional business model: marketing your software from your choice of web site rather than being forced to go through Apple's App Store.

Of course, this begs the question of whether or not the hacker community will be able to crack Apple's digital-signing mechanism, creating applications that are accepted by the 1.2/2.0 firmware. Based on previous track record, I really don't see this as a big deal. The necessary sleight of hand was online within a couple of days of the official firmware release.

And there are other advantages in going the unofficial route. Apple bans third-party developers from creating background applications - processes that lurk doing stuff while another application is in the foreground.

There are some solid justifications for this approach in terms of security, reliability and battery life. But for applications that really, really must operate in the background, and are intelligently written enough not to kill the device's battery life, then the unofficial approach is probably the only way forward.

Just to muddy the waters a little further, a number of enterprising individuals have figured out how to massage the official SDK tools so as to work with previous versions of the firmware. Point your browser here, and you'll find a series of steps describing how to get Xcode and the simulator to work seamlessly with firmware 1.1.4 - the latest, official firmware at time of writing. This gives you the convenience of the SDK, and the power of the full 1.1.4 firmware, undocumented goodies and all.

iWar fallout

The bottom line is that there is still a lot left to fall out of the iWars between Apple and third-party developers who don't wish to go the official route.

I can't help wonder how much simpler life might have been if Apple had planned to open up the iPhone from the beginning. This is either something that - in my opinion - Apple decided against from the start, a possibility given the company's track record on closed environments, or it realized the financial benefits of keeping the iPhone a closed and controlled platform later into the product's development cycle.

Either way, if Apple had welcomed third-party development from the start, then we might have a secure sandbox for non-Apple applications, a scaled down hacking war with the developer community, and maybe less neurosis at Apple. Hindsight is a wonderful thing.®

HP ProLiant Gen8: Integrated lifecycle automation

More from The Register

next story
Yorkshire cops fail to grasp principle behind BT Fon Wi-Fi network
'Prevent people that are passing by to hook up to your network', pleads plod
Major problems beset UK ISP filth filters: But it's OK, nobody uses them
It's almost as though pr0n was actually rather popular
Apple orders huge MOUNTAIN of 80 MILLION 'Air' iPhone 6s
Bigger, harder trouser bulges foretold for fanbois
Microsoft unsheathes cheap Android-killer: Behold, the Lumia 530
Say it with us: I'm King of the Landfill-ill-ill-ill
All those new '5G standards'? Here's the science they rely on
Radio professor tells us how wireless will get faster in the real world
US freemium mobile network eyes up Europe
FreedomPop touts 'free' calls, texts and data
'Two-speed internet' storm turns FCC.gov into zero-speed website
Deadline for comments on net neutrality shake-up extended to Friday
Oh girl, you jus' didn't: Level 3 slaps Verizon in Netflix throttle blowup
Just hook us up to more 10Gbps ports, backbone biz yells in tit-for-tat spat
prev story

Whitepapers

Designing a Defense for Mobile Applications
Learn about the various considerations for defending mobile applications - from the application architecture itself to the myriad testing technologies.
How modern custom applications can spur business growth
Learn how to create, deploy and manage custom applications without consuming or expanding the need for scarce, expensive IT resources.
Reducing security risks from open source software
Follow a few strategies and your organization can gain the full benefits of open source and the cloud without compromising the security of your applications.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.
Consolidation: the foundation for IT and business transformation
In this whitepaper learn how effective consolidation of IT and business resources can enable multiple, meaningful business benefits.