Ammo Navigation Weblog Company Support Store Rogue Amoeba
Rogue Amoeba
Fri, 06 Jul 2007

For a long time, there's been debate about just how much functionality the operating system should encompass. As I noted in The Rise Of The OS, the operating system has gradually been acquiring more and more functionality that was once the domain of third-party software. In many cases, this is a necessary step to advance general computing, but it can be unfortunate for those developers who pioneered new markets.

This issue has come up many times in the Mac community, when Apple has taken over a market. iTunes and Mail have put a hurt on the MP3 and mail markets, respectively. In some cases, such as Sherlock 3 or Dashboard Widgets, Apple's effectively recreated existing third-party software and included it in the OS, sparking debate on what constitutes a rip-off.1

Today, I'm not interested in debating what Apple has or has not ripped off from third party developers. The simple fact of the matter is that when Apple releases a major new application and bundles it free with the OS, it has the potential to be a game changer.

Indeed, when Apple2 absorbs a market into the OS, several major events occur. Most obvious, the functionality in question generally becomes much more widespread. By virtue of receiving Apple's blessing, this functionality is suddenly mainstream. Good for users, who gain new functionality. However, there are also two different parties who wind up losing out when a market closes down.

Group 1: Developers

Most obvious, the developers who first settled that market generally get forced out. Competing with a free and bundled application, as a third-party developer, is incredibly tough.

But while we certainly have a self-interest in developer relations, the developers who get locked out are a very small group, and tend to land on their feet. I don't have a broad solution for this problem, besides advising third parties to stay nimble and adapt fast.

Group 2: Users

The far larger group losing out when Apple absorbs a market is the end users of the OS . How can that be, when Apple has provided an Apple-branded solution for a given need? The problem arises from the fact that Apple is not married to any particular new market. As such, the provided solutions are seldom deep. They do the job for many, perhaps even most users, but as with all software, they're seldom complete.

In the comments for The Rise Of The OS, Rory Prior of ThinkMac notes:

"You end up in a situation where the bundled apps aren't necessarily that great but the environment has been starved of enough oxygen that a healthy ecosystem of 3rd party alternatives can't really survive. It would be nice to see Apple recognising this and working more with the wider developer community instead of trying to go it alone so much."

How About Frameworks?

It seems to me that there is a solution and it's one we've seen before, from Apple even - frameworks. Apple released the WebKit framework back in 2005, and it's now in use in dozens of applications, from browsers to RSS readers to other seemingly unrelated apps. WebKit has been a boon for OS X, making it a richer platform.

So perhaps a MailKit framework is in order, and maybe others as well. Just as they've done with rendering the web, Apple's already done the heavy lifting on email. Mail.app has the POP, IMAP, and SMTP backend that's required for every modern email client, but currently only Mail has access to the code. Rewriting this from scratch would take months, and when it was all done, you'd be effectively at square one. Only with this backend in place can you really begin to build new features on top of an email client.

If Apple decides to release such frameworks, developers will still be in a tough spot. A framework wouldn't change the reality of competing with a free and bundled first party solution. It would, however, lower the barrier to entry. With MailKit, and other similar frameworks, innovation could be restarted in previously stagnant areas. Adventurous developers could take a chance on both freeware and commercial applications, with less investment required. When that happens, everyone wins.

Footnotes:
1. To be sure, not all claims of appropriated IP have equal merit.

2. This applies to any OS vendor, of course, but current reality means that's just Apple and Microsoft. As a Mac company, we're focused on Apple.

Posted by Paul | Permalink | View/Post Comments (6)

Comments


Mark Munz
Fri Jul 6 19:33:07 2007

I definitely wish Apple would offer up more frameworks, it only helps to empower developers. The end result is cooler apps because developers spend less time on the fundamentals, and more time on the particulars for their audience.

I think a MailKit framework would allow developers to integrate email functionality right inside their applications, not just duplicate a mail package -- just like they do with browsing & the WebKit today.

It wouldn't even be a matter of competing with free. Yes, there are a handful of Safari replacements for WebKit, but the real growth of WebKit is in ALL THE OTHER applications that use it. It has become ubiquitous.

So while there may be some Mail replacements, it would probably be more about meeting niche market needs, something Mail will never do. Even with replacements, since ALL email apps generally suck right now, there's plenty of room to compete, even with free.

I think Apple is usually better off when it enables developers rather than just competes directly with them. It's really still about selling the hardware and enabling your developers to make kick ass products will sell more Macs (or iPhones or iPods or any other hardware you want to offer up).

Nerg
Sat Jul 7 02:34:11 2007

Surely this is a catch 22. If there was a framework available, then all third parties would still be starting from square one, albeit with say 75% of the work done for them. The situation would almost be identical to the current situation.

Even developing your own framework and trying to license that to other devs probably wouldn't help if Apple released there own version.

Apple do need to support third parties better than they do, but I don't think frameworks are the way forward. An alternative would be to bundle demo applications 'Windows Style' which I should think wouldn't go down to well.

It's a tough call, add ons to bundled apps would be great, but for that you need frameworks. Catch 22

Markus Magnuson
Sat Jul 7 06:02:05 2007

Why does it have to be Apple that develops these frameworks? I would rather see more joint open-source efforts.

A high quality MailKit framework could be produced by such a joint effort, it would just need a good project lead and of course an initial group of developers. There are no technical barriers, it's just a matter of priority and time.

Mark Munz
Sat Jul 7 11:22:38 2007

Actually, there is a 3rd party mail framework: Pantomime <http://www.collaboration-world.com/>.

I believe the IMAP support is new and v1.2pre3 was the last official release back in Feb '07.

Paul (Rogue Amoeba Staff)
Sat Jul 7 12:22:56 2007

Mark Munz: It's certainly true that WebKit isn't just about browsers. I'm not sure how many apps need email built in though. There are a lot of alternatives an application can use, from handing messages off to the system mail client, to submitting messages via a web server. It's an interesting thought though.

"I think Apple is usually better off when it enables developers rather than just competes directly with them."

That's right on the money. The question is, does Apple believe/know this? Sometimes it's tough to tell.

Nerg: The situation wouldn't be identical at all, no. For the mail client example: Right now, there's an enormous barrier to entry, as it requires an outlay of months (and MONTHS) just to get to the point of having the most basic client (sending and receiving over POP and IMAP). If that were available at a lower cost, more developers could work on  what comes next.

Markus Magnuson: It doesn't have to be Apple. However, Apple has the code already, and they have dedicated resources.  Open source is a great idea, but in practice, it rarely (if ever) provides the stability of a dedicated team of paid programmers.

The point here is that when Apple releases an application, it takes over a market. To combat that, when they release an application, they could also release a backend to it to enable other developers to provide custom solutions. There's no direct downside - Apple's apps are free and bundled. The biggest problem is determining if the economic upside of a richer platform makes up for the cost of releasing the framework.

DDA
Sat Jul 7 12:57:34 2007

"I'm not sure how many apps need email built in though."

Clearly every app needs this: http://en.wikipedia.org/wiki/Zawinski's_law_of_software_envelopment

:-)


This post is archived, and commenting has been closed.
Copyright © 2008 Rogue Amoeba Software, LLC. All rights reserved.