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

New atproto app idea I demoed yesterday where you record what you’re grateful for and tag someone. Each orb is a recording, and is used to power a generative synth for a dynamic ambient soundscape. Definitely zoned out to this last night 👽

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

Realizing that quietly, without a big push, all the apps doing events (or pushing events from their non-atproto system) have adopted the @lexicon.community events lexicon. "Wherever you get your events" == "wherever you get your podcasts" Thanks @flo-bit.dev for reminding us that this is working!

Every year, i build the app for @wickedwoods.ca I want to give the #atprotodev community a sneak peak of the UI surface, before @openmusicevent.app launches to the protocol It's a pure #swift app, that builds its single codebase to #iOS and #Android. More to come :)

some thoughts on atproto as a post-app paradigm

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