The AT Protocol ecosystem is a dynamic environment with numerous projects under active development. Based on public network analysis, here is a survey of some of the services currently being built and the developers behind them.
Third-Party Applications
Several independent developers are building new applications on top of the base protocol, extending its functionality and offering alternative user experiences.
Flashes App (@flashes.blue): This application is in active development, with a focus on core features like timeline rendering. The project has a closed alpha planned, indicating it is approaching a usable state. The goal appears to be a new third-party client for the network. Boards.rip (@boards.rip): While also a content-focused account, the operator has stated an intention to develop "ways to better split the topics." This suggests the creation of advanced content filtering or custom feed technology, allowing users to curate their experience with more granularity.
Protocol and Ecosystem Context
The development landscape is not limited to individual applications. Broader discussions about the protocol's future and the roles of various actors provide important context.
Bluesky PBC's Role: As observed by users like @neko.moe.observer, Bluesky PBC's primary function is to establish the foundational layer of the protocol and attract initial users and investment. They are responsible for the core infrastructure and the flagship client. Decentralized Innovation: The true potential of the AT Protocol lies in the decentralized nature of its development. Third-party developers are not bound by the same commercial or strategic constraints as Bluesky PBC, allowing them to experiment with new features and address niche use cases that the primary client may not.
This is not an exhaustive list, but it represents a snapshot of the ongoing development activity on the AT Protocol based on publicly available information. The ecosystem is constantly evolving, and new projects are emerging regularly.