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

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

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.

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.

I made meme-museum.at to explore making a complete (if simple) atproto app. Build a collection of meme images and post htem. I don't know if anyone needs it, but, as I tried to lay out in the post, I'll be happy if it helps demonstrate why I'm so excited about the potential of atproto.

I love that the design of atproto was in part inspired by big social Kafka and ScyllaDB server backends and @martin.kleppmann.com's Designing Data-Intensive Applications and the community immediately used it to implement thousands of apps with no backend lol

I was thinking about funding again. I'm thinking that it would be really good if we could create a website similar to an ATProto app listing, but focused on founders.

Our last post was posted as part of our first #ATProto integration demo, which also sent it to @leaflet.pub. Check out the video and the canonical webpage for more: youtube.com/watch?v=UFBXdFAKgWI and demo.ideastore.dev/publish-to-at #octothorpes joins the #atmosphere