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

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

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

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.

I hate to post from the other app but I have to agree with Zach. Add atproto and permissioned data and we’re onto something…

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.

ATProto is a post-app protocol trapped in a world of apps. I can feel it all around the edges of the network.

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

I'm building on atproto because I think that a single social network has essentially no shot of dethroning the current tech monopolies. But an open ecosystem of interoperating apps is so infinitely more interesting than legacy social that it seems almost inevitable it will win

some thoughts on atproto as a post-app paradigm

The future of atproto lies in bespoke AppViews: highly tailored features that seamlessly integrate with and elevate existing network-wide behaviors. Due to that, I am incredibly energized by the strategic innovations emerging from SkyBeMoreBlue and BlueSky Radio.

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?

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

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