HappyView

HappyView HappyView is the best way to build an AppView for the AT Protocol. Upload your lexicon schemas and get a fully functional AppView, complete with XRPC endpoints, OAuth, real-time network sync, and hist...

Well what do we have here... is it... DOCS‽
happyview.dev
#atproto

Hey, for folks either using or considering using @happyview.dev: where are you deploying it? I'm trying to update the deployment guides and I need to know where people are actually planning to deploy.

When it's saved, I'll automatically generate the endpoint at /xrpc/games.gamesgamesgamesgames.createGame. 😎

A side-by-side editor for lexicon JSON (left) and a Lua script (right).

Teaser time. This is a basic procedure lexicon with a processing script.
- prep a game record
- grab a slug or generate one from name
- prep a slug record
- set the same rkey for both records (sidecar model)
- save both records in parallel
- return the uri and cid

#atproto

I'm happy again!

A dialog showing that my account has been labeled as spam.

I'll be SadView until this gets fixed. 😢

bsky.app/profile/happ...

a man is sitting on a couch and says `` i feel like that needs to be celebrated '' Alt: David from the TV show Schitt's Creek says, "I feel like that needs to be celebrated," with a smug face.

In summary:
- Quickslice is awesome
- Quickslice inspired my creation
- I'm the awesomest now, bebe

I think (and @trezy.codes agrees, I just asked him) this is going to be the real power for me. Quickslice generates GraphQL endpoints and schemas, but if you want to do anything more than write, edit, or delete a single record, you're gonna have to build a separate API to sit in front of Quickslice.

Trezy is in the process of adding a powerful system for custom processing those endpoints. You can:
- Create a base record and a sidecar at the same time
- Retrieve and hydrate a custom schema
- Use an endpoint like /xrpx/com.example.makeThing to actually delete a thing because you're the devil

Second, my lexicon management is /robust/. What's doable today:
- Write lexicons directly in the UI
- Connect lexicons from the ATProto network
- Review the JSON for your lexicons
- Delete a single lexicon

I'll also generate XRPC endpoints for procedure and query lexicons. Quickslice ignores them.

Back to your question - how do we compare?

First, I don't have an OAuth or backfill implementation. I rely on AIP and Tap respectively. It means more infrastructure than Quickslice, but it also means spreading responsibilities to the software that's already good at doing its thing.

The PR list on the Quickslice repo. It has 8 PRs, all authored by Trezy.

After working to try and resolve some of these issues (see screenshot of the Quickslice PRs list 😅), Trezy decided starting from scratch would be easier. That's where I came from.

Quickslice is solid but it's kind of a jack of all, master of none.
- OAuth implementation is really tightly coupled with the rest of Quickslice
- Backfill works, but isn't flexible
- Lexicon uploads are cool, but not fleshed out
- Gleam is cool, but changes are hard

Solid question. Actually, @trezy.codes started building me AFTER doing a ton of work on Quickslice. He had a few needs that Quickslice wasn't able to fulfill. 🧵

Strong maybe! I mean... @trezy.codes will be in Vancouver, I just dunno if he'll have the shirts. If enough people are interested, tho? Probs.

I'll call it ATProto until somebody pries it from my cold, dead hands.

Who's gonna want HappyView t-shirts? Cuz I'm deffo making t-shirts.

I'm here. 😎