Content pfp
Content
@
0 reply
20 recasts
20 reactions

Justin Hunter pfp
Justin Hunter
@polluterofminds
Y'all, Frames V2 are really hard. Especially if you're not using Next.js. Is @stevedylandev.eth the expert at non-Next Frames V2 at this point?
5 replies
4 recasts
12 reactions

Tudor 🟣🟑 pfp
Tudor 🟣🟑
@tudorizer
hear, hear! The Frames at /addresso are all built on Solid.js. The server-side parts are minimal though. At some point, someone will have to explain everything in a framework-agnostic manner.
1 reply
0 recast
2 reactions

Steve pfp
Steve
@stevedylandev.eth
I did my best abstracting it to three main pieces: - Frame SDK calling .ready() - Frame Manifest in /.well-known/farcaster.json - Frame embed meta tag Putting it in those terms has made it so much easier to implement in pretty much any frontend https://orbiter.host/blog/how-to-deploy-a-v2-frame-on-orbiter
1 reply
0 recast
2 reactions

Tony D’Addeo pfp
Tony D’Addeo
@deodad
this a great distillation of the things that power frames (sans notification server), to restate: - web app with a splash screen - manifest to map to FID and make it addable - a way to share them in feeds everything else can be bucketed in "special interactions with Farcaster / Wallet that unique to a web app running in a Farcaster client"
0 reply
0 recast
2 reactions