What's the intended app/user etiquette for atproto apps with regards to publishing to the same lexicon? Like, say I build an atproto app, would it catch users by surprise if the wrote to the same records (e.g. posts, likes, etc?) that show up in the bsky.app? Or should my app be isolated?
Apr 3, 2026 at 3:54 PM
Lexicon Embeds Overview
ATProto’s inside out structure provides an opportunity for open, permissionless building on top of any component in the network, including its extensible data schema definition system, Lexicons. One of the opportunities this presents is users sharing their data and records with multiple apps. Those apps may be direct substitutions (different clients for microblogging say), or apps that use that data in a variety of ways, such as Popfeed an app which aggregates posts about a variety of media ty...
ATProto Standards Bodies | Sam Clemente | Offprint
How do we go about maintaining lexicons across apps?
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Guide for migrating your app to atproto
This is a quick response to this post @anniesexton.com on Bluesky Please do edit and point to other resources If you have an existing database powered app, here is a rough guide to thinking about migrating to atproto Figure out which data is private, this will stay in your database Figure out what the main data is. Look around for an existing lexicon or create your own. When creating new records, write them to the user PDS. You’ll need to start aggregating your lexicon types from the ne...
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
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.org@atpota.to and @dame.is, we were talking about making an ATProto-powered app directory on the community forum and someone found your atproto.garden and some records lying around. Are you interested in sharing your lexicons or talking about what a simple directory lexicon might look like?
A community app lexicon
discourse.atprotocol.communityI'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.ukAre there any atproto apps that use records from competitors? This ecosystem won't feel open to me until @bsky.app uses something from outside the `app.bsky` namespace as part of its core experience
How hard would it be to replicate a community Slack installation to an ATProto lexicon so messages can be archived or sent to other application for indexing? Is there any community lexicons for this already?! cc @bmann.ca
Are there any atproto apps that use records from competitors? This ecosystem won't feel open to me until @bsky.app uses something from outside the `app.bsky` namespace as part of its core experience
ATmospheric Apps
Things that use ATProto to create their own records (NOT Bluesky clients / Appviews)
import.py
Archivers AT
Brickster — Build anything, together.
BlueHarbor
Kimbia - A training journal that belongs to you.
Currents
