Sign of a post-app economy forming around atproto
Erlend Sogge Heggen
As @awarm.space pointed out in the replies, ‘traffic’ was never the real goal for authors. What we want is for our stuff to be read, and expand-on-click article embeds enables that, with AT-net metrics. The prospect of mutual syndication is the entire premise of our shared presence here on atproto.
Dec 29, 2025 at 5:30 PM
This is a spec for ATProto accounts to request and advertise (compute) resources.
This is a spec for ATProto accounts to request and advertise (compute) resources.
ATProto Isn't What You Think
This post takes a look at ATProto from a different angle, and explores the value of some possibly less-noticed pieces of it.
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.comsome thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgImagining atproto as a post-app protocol starts with materializing the social filesystem – decomposing apps and their data into materials and instruments. For the time being, this guestbook is a good example where the display element is a material and the sign element is an instrument.
dan
in any case, the end game is composing these little guys, whatever goes on behind the scenes. social components
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.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
the 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.
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.org
