bsky.app — Semble

Log in to connect Log in to add

bsky.app

Ricardo J. Méndez

@ricardo.bsky.social

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.com

May 11, 2026 at 11:31 AM

Log in to connect Log in to add

social

bsky.app

Ricardo J. Méndez

@ricardo.bsky.social

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.com

May 11, 2026 at 11:31 AM

social

blog.muni.town

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.

nearhorizon.app

Horizon — an ATProto client

Horizon is an ATProto client in development.

Wesley Finck

some thoughts on atproto as a post-app paradigm

Bridging the interop gap and addressing the long-tail of user needs

Ecosystem Plugins

notes.wesleyfinck.org

kademlia (crass version)

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.

midwest emo fan

what is our “moat” on atproto even? what keeps people using a specific atproto app vs a fully compatible other app?

taurean

also, I kinda feel like calling the things that consume atproto data "apps" does a disservice to understanding what they are / how they work / what their potential is. But that is a partially-formed hot take I can't fully defend yet.

𝕮

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

Frances Meh

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

Boris

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

blog.muni.town

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.

Chimney Sweepers Local 420

Hot 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.

Wesley Finck

some thoughts on atproto as a post-app paradigm

Ecosystem Plugins

notes.wesleyfinck.org

dietrich

while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

dame

i would like to see more atproto apps that aren’t just “already popular app, but on atproto”

Building atproto apps

useful tools and resources for building apps in the Atmosphere.

𝕮

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

John

Some thoughts on why ATProto is so exciting from the perspective of what it could unlock software dev wise.

Accelerating the Security Development Lifecycle

ATProto: Engine of Software 2.0

john.leaflet.pub

dietrich

while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

dame

i would like to see more atproto apps that aren’t just “already popular app, but on atproto”

nearhorizon.app

Horizon — an ATProto client

Horizon is an ATProto client in development.

Frances Meh

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

John

Some thoughts on why ATProto is so exciting from the perspective of what it could unlock software dev wise.

ATProto: Engine of Software 2.0

john.leaflet.pub

Chimney Sweepers Local 420

Hot 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.

kademlia (crass version)

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.

Wesley Finck

some thoughts on atproto as a post-app paradigm

Ecosystem Plugins

notes.wesleyfinck.org

Boris

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

taurean

also, I kinda feel like calling the things that consume atproto data "apps" does a disservice to understanding what they are / how they work / what their potential is. But that is a partially-formed hot take I can't fully defend yet.

Wesley Finck

some thoughts on atproto as a post-app paradigm

Ecosystem Plugins

notes.wesleyfinck.org

𝕮

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

midwest emo fan

what is our “moat” on atproto even? what keeps people using a specific atproto app vs a fully compatible other app?

dietrich

while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

dame

i would like to see more atproto apps that aren’t just “already popular app, but on atproto”

𝕮

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

dietrich

while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

dame

i would like to see more atproto apps that aren’t just “already popular app, but on atproto”

Building atproto apps

useful tools and resources for building apps in the Atmosphere.