







ATProto ideas
If AT Protocol becomes “a meaningful layer of the web” — even if it’s only tens of millions of users — then the winning ideas probably won’t only be futuristic...
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgthe point of atproto is to make locked-open apps. apps which are constrained such that they cannot be e.g. bought by billionaires and ruined. yes, doing non-atproto things "enables app developers to do more". yes, non-atproto is "more intuitive" and "it sucks" when you hit atproto's limits.
ATProto, by design, refuses to be the place where things happen. Decisions live in apps. Value derives from execution, and execution will demand focus. This is application primacy — and it's why I don't expect an ATmospheric "everything app": numergent.com/2026-05/ATProto-Application-P…
ATProto's Application Primacy
numergent.comI'm thinking about how non-developers will feel about atproto. For example, will it take people by surprise that data entered into one app can show up somewhere else? More thoughts in this post.
How do we talk about atproto to non-developers? | Rachel Andrew
rachelandrew.co.ukSome initial atproto-related learnings from #Rebuild Helsinki 🇫🇮 * most people building apps here have no idea what atproto is, which is a shame since especially when building social apps, atproto is a great starting point for many reasons
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgHot take but I think it’s problematic for atproto that lots of developers i see talking about making stuff focus mostly on things absolutely no end user gives a shit about to fuel their protocols and architecture fetish, and it’s a failure there isn’t another app with like 100k+ users active even.