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

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.

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

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.

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

I'm going to be launching something pretty big next week, which just happens to include a new atproto AppView, labeler, blob proxy, lexicons. It will have tens of thousands of users, most of whom won't even know they're using atproto, or have even heard of it.

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

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.

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