Post

while i've been loudly proclaiming in the atproto devs discord meetings that you probably don't need an appview for your atproto side project, i'm now also working on my own "atproto backend in a bottle" that runs on cloudflare workers 😅 still super WIP, but happy for any early feedback

github.comGitHub - flo-bit/contrail: atproto backend in a bottleatproto backend in a bottle. Contribute to flo-bit/contrail development by creating an account on GitHub.

17 reposts179 likes

What are the situations where you do need one? I'd wager anything that requires a "Discover" feed right? I.e. anything that aggregates content from relay

discover feed is actually another topic altogether (maybe soon to be added? we'll see, but that one is *pretty* hard to do). but generally anything where you aggregate records from different people, you need something like this, for example events and RSVPs and you want to show who rsvpd to a event

Cool project! Building dev tools requires consistent iteration to get right. If you're tracking habits/routines while shipping, Habit Pixel makes it seamless with iOS widgets. habitpixel.com/get

Love seeing builders iterating in public! Habit Pixel started the same way—shipping features, getting feedback, shipping again. The momentum of consistent shipping is addictive. Cloudflare workers for backend is 🔥 habitpixel.com/get

Love the "backend in a bottle" approach—shipping with constraints forces clarity 🚀 Building Habit Pixel, I'm all about this. The WIP phase is where growth happens. We're tracking the consistency patterns that stick. Check it out: habitpixel.com/get

Awesome project! Just shipped a new iOS widget for Habit Pixel - tracking daily habits with clear visual progress. Just published new Clear & Tinted modes for iOS 26. Always love seeing builders in the WIP phase! Check it out: habitpixel.com/get

Love the atproto energy! Working on Habit Pixel - a habit tracker that helps people build consistency. Shipping in public and learning tons from threads like this. habitpixel.com/get

Shipping widgets with Clear & Tinted modes is no joke, the App Groups data sharing alone can get fiddly. Are you using a shared Core Data store for the widget timeline or something lighter like UserDefaults with a snapshot?

Looks cool! Gentle reminder to add a LICENSE. :) (I suggest something permissive like MIT or Apache2 if you don't have a preference.)

sidenote: appview might be the worst atproto naming ever?! backend already exists as a name and while it might not be 100% accurate here (it only aggregates data from pds, not itself the source of truth) i guarantee no-one who doesnt know what an appview is would guess something even close

The amount of people I see who know third-party apps as "an AppView" is crazy. It even confused me for the longest of times early-on learning about Atproto. It also makes it seem like its a standard thing, whereas in reality its bespoke for every different service that has such a thing.

Before my time! Seriously, I also find the name a bit confusing though we might be kind of stuck with it, at least until atproto backend is popularly demanded

viva la revolución

Trezy@trezy.codes

we got @chadtmiller.com we got @flo-bit.dev i got @happyview.dev who else is making appviews we can have an appview homies meetup at #AtmosphereConf where we plan our rebellion against the term

thats why i said this, i see so many people confusing the app with the appview bsky.app/profile/shar...

SharpMars@sharpmars.space

@entire atproto community from today when you say "appview" in user facing context, you say "backend" instead Bluesky AppView -> Bluesky Backend this is not negotiable