the open ecosystem for atproto makes it super easy for one developer to build a compelling and feature rich application in their free time that cannot possibly be maintained by one developer in their free time

also, I kinda feel like calling the things that consume atproto data "apps" does a disservice to understanding what they are / how they work / what their potential is. But that is a partially-formed hot take I can't fully defend yet.

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.

one thing I really like about atproto is that it provides the infrastructure needed to make open source user apps that actually fucking sync data across devices sorry but the average random hobbyist is absolutely not going to run a user account server for their homebrew todo list app

It seems a fork lies ahead, is atproto a portable database for a bunch of apps or a new type of post-app, social filesystem?

some thoughts on atproto as a post-app paradigm

Hi, we're HappyProto. We help you build on atproto... without the hard parts. You create the app, we'll run the backend: auth, private data, scripting, and an API over 46 million accounts. Welcome to atproto on easy mode. Join the waitlist at happyproto.at?utm_source=bluesky&utm_medium…. #atproto

difficult to imagine atproto apps building to significant revenue in a world where you can just clone any given app in an afternoon & still access the backing data

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.