Every lexicon, every "app" on ATProto is a "yes and" waiting for your contribution to the vision. We're all first party developers.

new proof of concept: ATProtoCall! video calling over atproto with just static files and no dedicated signaling or streaming infrastructure.

new proof of concept: ATProtoCall! video calling over atproto with just static files and no dedicated signaling or streaming infrastructure.

ATProto is a post-app protocol trapped in a world of apps. I can feel it all around the edges of the network.

some thoughts on atproto as a post-app paradigm

some thoughts on atproto as a post-app paradigm

the open ecosystem for atproto makes it super easy for one developer to build a compelling and feature rich application in their free time that cannot possibly be maintained by one developer in their free time

The future of atproto lies in bespoke AppViews: highly tailored features that seamlessly integrate with and elevate existing network-wide behaviors. Due to that, I am incredibly energized by the strategic innovations emerging from SkyBeMoreBlue and BlueSky Radio.

This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.