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

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

i would like to see more atproto apps that aren’t just “already popular app, but on 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

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

🧵 I've been wracking my brain around ATProto onboarding. Why do all ATProto apps make you create a new account before you can do anything interesting? Why don't we let people start with an email address or phone #? Then claim your identity if/when the need actually arises.

🧵 I've been wracking my brain around ATProto onboarding. Why do all ATProto apps make you create a new account before you can do anything interesting? Why don't we let people start with an email address or phone #? Then claim your identity if/when the need actually arises.

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

some thoughts on atproto as a post-app paradigm

I'm thinking about how non-developers will feel about atproto. For example, will it take people by surprise that data entered into one app can show up somewhere else? More thoughts in this post.

the point of atproto is to make locked-open apps. apps which are constrained such that they cannot be e.g. bought by billionaires and ruined. yes, doing non-atproto things "enables app developers to do more". yes, non-atproto is "more intuitive" and "it sucks" when you hit atproto's limits.

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.

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