Umair Haque is at his usual stimulating and frustrating best in a recent post comparing Apple and Facebook’s third party application strategies. Stimulating because he is looking at an important topic and pointing out interesting differences. Frustrating because Umair’s free wheeling style and usage of otherwise well defined terms leads to conclusions that seem unwarranted (at least to me).

There are two important differences between the Apple application model and the Facebook model

1. Apple allows for paid apps, whereas all Facebook apps are free (and hence ad supported)
   

2. Apple screens apps prior to their release, whereas Facebook has no such mechanism [CORRECTION: As a commenter points out I am wrong here – Facebook does have an approval process for the directory. It is, however, possible to build and release an application without approval.]
   

Somehow in Umair’s view this makes Apple’s app strategy a “market” and genius and Facebook a failure. This strikes me as a gross exaggeration. It is worth examining both of these differences more closely.

On the first point, it turns out that many of the popular apps in the Apple app store are in fact free. So it does not seem that Facebook made a huge mistake by not supporting a paid app model from the get go. It is well known though that Facebook is working on a payment platform and I would not at all be surprised if once it launches Facebook too will support paid apps. Price would be used as a form of hygene, i.e. to keep app spam out, only if no *free* apps were permitted. Clearly that’s not the case in Apple’s app store. The compalints about Facebook app spam also seem grossly exaggerated. People do in fact learn how to uninstall apps and Facebook has toned down the potential for apps to be spammy. So this does not seem to be a dramatic difference today and is likely to disappear entirely as a difference.

On the second point, Apple had to have a screening mechanism to make sure that apps don’t brick the phone. This is a result of Apple’s decision to let apps execute native code rather than putting apps in a strict sandbox. While that is a valid reason, it clearly provides Apple with power and control that it can and

Umair Haque is at his usual stimulating and frustrating best in a recent post comparing Apple and Facebook’s third party application strategies. Stimulating because he is looking at an important topic and pointing out interesting differences. Frustrating because Umair’s free wheeling style and usage of otherwise well defined terms leads to conclusions that seem unwarranted (at least to me).

There are two important differences between the Apple application model and the Facebook model

1. Apple allows for paid apps, whereas all Facebook apps are free (and hence ad supported)
   

2. Apple screens apps prior to their release, whereas Facebook has no such mechanism [CORRECTION: As a commenter points out I am wrong here – Facebook does have an approval process for the directory. It is, however, possible to build and release an application without approval.]
   

Somehow in Umair’s view this makes Apple’s app strategy a “market” and genius and Facebook a failure. This strikes me as a gross exaggeration. It is worth examining both of these differences more closely.

On the first point, it turns out that many of the popular apps in the Apple app store are in fact free. So it does not seem that Facebook made a huge mistake by not supporting a paid app model from the get go. It is well known though that Facebook is working on a payment platform and I would not at all be surprised if once it launches Facebook too will support paid apps. Price would be used as a form of hygene, i.e. to keep app spam out, only if no *free* apps were permitted. Clearly that’s not the case in Apple’s app store. The compalints about Facebook app spam also seem grossly exaggerated. People do in fact learn how to uninstall apps and Facebook has toned down the potential for apps to be spammy. So this does not seem to be a dramatic difference today and is likely to disappear entirely as a difference.

On the second point, Apple had to have a screening mechanism to make sure that apps don’t brick the phone. This is a result of Apple’s decision to let apps execute native code rather than putting apps in a strict sandbox. While that is a valid reason, it clearly provides Apple with power and control that it can and