1st image, building an app
2nd image, app is published to PDS
3rd image viewer renders it in an iframe and injects the SDK

The hypercard part would be some nice builder UI but the user could also just manually push to their PDS and compatible appviews would discover the app.

By editing the injected SDK the user chooses where their data is saved. One viewer could be pure PDS, one could be some centralized store, one could be local only.

If you trust it there's no reason you can't fetch the "backend" source from the stack definition and run it in an isolated sandbox

Yes!! at-proto needs hypercard. As soon as I get some time I'm planning to build it out.

But each stack/card a record. UI definition is either straight compiled HTML ala ChatGpt Apps, or some schema that defines what the view should render.

AppView injects a standard async SDK into the UI.

Stop treating it's subjective opinions on WHY it did something as important. It's noise. It does not know. Focus on the important shit, is this maintainable? How is this decomposed? How is this going to evolve once I build on it?

Stop treating the AI like a human. It is not. It cannot learn and it is frankly stupid to expect it to. It pattern matches to what you give it. So give it good patterns to match. This isn't hard.

And if you literally cannot find a single way to speed up your work flow with a fucking magic box that spits out 80% correct code, the problem is YOU not the magic box. Learn to use your tools better. Be more creative.

Enabled by projects like opencode.

This is the post that made me try opencode. After a day of user holy shit. Seriously good piece of software. I'm excited to build with what the server enables.

I lied. I kind of love it after doing more digging. Way more extendable. It doesn't follow my instructions as well which I'm sure has to do with the system prompt but I can see a lot of cool integrations possible with this.