







An design provocation: A big reason people love atproto is because of the feelings of empowerment it offers. These feelings don't translate to end users. We're not building things that give non-technical people atproto creative experiences. How do we design to give feelings of atproto empowerment?
Aug 14, 2026 at 9:09 PM
An introduction to radical participatory design: decolonising participatory design processes
Outside of community-led design projects, most participatory design processes initiated by a company or organisation maintain or even strengthen power imbalances between the design organisation and the community on whose purported behalf they are designing, further increasing the absencing experience. Radical participatory design (RPD) is a radically relational answer to the coloniality inherent in participatory design where the community members’ disappointment is greater due to the greater expectations and presencing potential of a ‘participatory design’ process. We introduce the term RPD to show how research and design processes can be truly participatory to the root or core. Instead of treating participatory design as a method, a way of conducting a method, or a methodology, we introduce RPD as a meta-methodology, a way of doing any methodology. We explicitly describe what participation means and compare and contrast design processes based on the amount of participation, creating a typology of participation. We introduce ‘designer as community member’, ‘community member as designer,’ and ‘community member as facilitator’ models and provide characteristics for the meta-methodology of RPD.

An introduction to radical participatory design: decolonising participatory design processes
Outside of community-led design projects, most participatory design processes initiated by a company or organisation maintain or even strengthen power imbalances between the design organisation and the community on whose purported behalf they are designing, further increasing the absencing experience. Radical participatory design (RPD) is a radically relational answer to the coloniality inherent in participatory design where the community members’ disappointment is greater due to the greater expectations and presencing potential of a ‘participatory design’ process. We introduce the term RPD to show how research and design processes can be truly participatory to the root or core. Instead of treating participatory design as a method, a way of conducting a method, or a methodology, we introduce RPD as a meta-methodology, a way of doing any methodology. We explicitly describe what participation means and compare and contrast design processes based on the amount of participation, creating a typology of participation. We introduce ‘designer as community member’, ‘community member as designer,’ and ‘community member as facilitator’ models and provide characteristics for the meta-methodology of RPD.

Introducing ATProtoFans: A New Way to Support Creators You Love - ATProtoFans Blog
Atproto Ethos - AT Protocol
A deep dive into the philosophical and aesthetic principles underlying the design of AT Protocol.

Making the Case for Actionable Prosocial Design Research
Regulating harmful design is only half the equation — attention must also go toward how platforms can build prosocial design, and toward the research that shows them how.

By Humans, For Humans – Mindful Design
Now, more than ever, we need to consider the real, human impact of the work we do. This is a fundamental principle of Mindful Design.

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”
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”
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
Some more ideas about how I think to build an atproto app for artists from the needs I see in my community, and how I envision to grow this into a longer term project. I am curious about your feedback and who is interested to participate.
Artist app diary (2): how to stay sustainable with community building and financial funding
hilkeu.leaflet.pubSome 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.pubImagining 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
I finally put some ideas into words about the artist focused app that I would like to build on atproto. I am looking for collaborators, especially artists and UI designers.
Artist app diary (1): the general idea
hilkeu.leaflet.pub