Application archetypes (according to a Microsoft study that Matt is talking about.)

• Doc editor apps
• Database apps
• Production/dev env apps
• E-commerce apps
• Info/ref. apps
• Entertainment
• Viewer
• Utility

Matt's six archetypes:

Easy-peasy desktop-native apps

• RoR + Mac + webKit + Tixe
• Custom GMail client, but not just rich client
• The new VB?

Aral: This falls squarely in the area that Apollo will be targetting.

2. Massive scalable affordable apps

• Storage: Amazon S3
• Computation: Amazon EC2 + MapReduce/Starfish
• Huge datasets: Alexa web index
• Intelligence: Computation + Mechanical Turk

Aral: I'm looking into EC2 and S3 quite a bit these days -- these two will revolutionize the way we build applications.

3. Situated apps that know where they are

• General purpose physical computing: Chumby, Nabaztag
• Input: Sensors, RFID
• Output: ARToolkit

4. Apps that are ambient; that do not interrupt

• Passively multiplayer online games
• Jaiku
• S&W+Nokia Continuous Partial Attention

5. Pipes transform (the Unix-style app)

• Scanr
• filtr
• Planet Venus Atom filters (reaching atomflow?)

6. RSS/Atom: Syndication for apps & interactivity

• RSS/Atom syndicates media
• Other updating lists: Bug trackers, moderation requests, etc.
• Syndicate limited application functionality

[Update] I apparently got Matt's last name wrong originally, it's Webb. Sorry, Matt! (And thanks, Ben, for correcting me.)

The BarCampLondon: Matt Webb on Application Archetypes article by Aral Balkan, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial 2.0 UK: England License.