The vector for new signups of atproto accounts is apps. Adoption is unlikely to come through just one app. A “drive” app would actually make sense and I have some ideas there but I think it will be varied. A lot of different apps can get big - from recipes to events to whatever.

Odoo has this toggle of showing their apps / what apps you can build or replace. They list 40K+ "community apps" And yes, also open source github.com/odoo/odoo With private data, likely good opportunities for atproto, too.

Some initial atproto-related learnings from #Rebuild Helsinki 🇫🇮 * most people building apps here have no idea what atproto is, which is a shame since especially when building social apps, atproto is a great starting point for many reasons

adding social features to our websites will accelerate atproto adoption faster than building pure atproto apps

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

I saw requests for a new way to find atproto alternatives, so I made alternativeproto.net - an atproto spin on AlternativeTo. It itself is on atproto, so you can log in and make submissions, votes, and reviews that are stored on your PDS. Give it a try and go easy, it's my first public atproto app.

what is our “moat” on atproto even? what keeps people using a specific atproto app vs a fully compatible other app?

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.

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