Search code, repositories, users, issues, pull requests...

The last few weeks have seen a swell of developer interest in atproto. Welcome! The protocol is maturing, and now is a great time for early adopters to jump in and start building. This post lists some projects which we think would be good fits for the protocol, and could be built by independent teams today. They span the range from helper tools to full applications.

As a general disclaimer and reminder, public data in atproto is globally broadcast. The protocol does not yet have support for restricting visibility of content. This means that care needs to be taken both when designing projects and communicating them to end users.

It is possible to build entire new social apps on atproto, making use of existing infrastructure, tooling, and user communities. Some apps are a better fit right now than others. Here are a few patterns we think could be successful today. See the Statusphere Tutorial, and "What does an AppView Implementation Entail" for an overview of what goes into building a full application.

Reviews and Recommendations: a broad category of social apps which would fit quite well with the atproto model are social reviews and recommendation services, for almost any type of venue, content, or artifact: restaurants and venues, companies and services, film and other media, durable goods and tech products, etc. Moderation primitives (like labeling and Ozone) can be used to mitigate fake accounts and rating manipulation. Existing databases and identifiers (eg, IMDB, MusicBrainz, Wikidata, ISBNs, SKUs) can be used to disambiguate subjects. Existing social graphs (like the Bluesky follower graph) could be used to bootstrap social recommendations.

Leave a Comment