Core loops and skinsuits

I once went to a local meetup where some app developers were presenting talks on user interfaces. I like these kind of presentations online, so I figured I’d enjoy this. I did not. They were much more open and honest about their motivations during their offline presentations. The crowd was full of superficial human-like husks. They were front end user-interfaces without a backend. Empty skinsuits.

It was probably just that crowd, but I ended up developing a stereotype of the typical app developer as someone who is looking for an infinite life hack. If their hack destroys lives or society at large, that logic has not been implemented, sorry.

I keep coming back to app development as a social system. Can one design an app that splices into social systems in a constructive way, rather than destructive? Right now I’m calling my framework the Core Loop Foundation, based around cores, features, messages, and loops.

Main Definitions:

• A core distinction that defines the boundary of the app
• Diverse features that adapt the app around the core distinction
• Messages being sent between the app, users, and the world
• Socially integrated loops of messages that keep the app alive

The Initial Process:

1. Analyze and map existing social systems and existing message loops out in the world.
2. Brainstorm different core distinctions and social loops for potential apps to integrate with existing loops.
3. Plot out these configurations:
   • What features would the prospective core need?
   • What messages would make up the proposed loop?
4. Experiment and test those configurations to see if they work in the real world.

That would be a very different core loop than the skinsuit-style core loop that is hyperfocused on keeping the user on platform.

Just an infographic today. I literally used this post to generate it. :-D