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

Think it's looking a lot nicer :) Got comments going too, I used @leaflet.pub's lexicon seems to work well for general use case of threaded comments on the atmosphere, thanks friends! We might actually launch this thing yet! Now the hard part: AppViews!

Lexicon suggestions for reader apps on AT Proto (such as @leaflet.pub Reader and @skyreader.app): - storing the reading status of a given URL - “liking” or “recommending” an URL - public (and when permissioned data will be out, private, or access controlled) folders to organize subscriptions

does a @semble.so <-> @lexidraw.app integration interest anyone 👀

Hey @danabra.mov, I’m working on a new labeler for arbitrary atproto records. I’d like lexicon owners to be able to suggest how to render their lexicons in the app. I’m thinking maybe @inlay.at components as sidecars?

I've been thinking a lot lately about how lexicon authors could help app developers understand intent. #atproto trezy.codes/blog/what-if-lexicons-knew-ho…

this is really great, and i'm glad that you're thinking about it!! I just started building @atmobb.app and wanted to build a way for it to pull in topics from similar forums and landed on subscribing to a "topic" for those forums. very excited to see what happens!!

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.

related: for a number of use cases on atproto, the challenge has shifted from 'how do i get people to use my app' to 'how do i get people to use my lexicon' this also shifts what prototype apps even are

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.