Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Suggestion for @dwr.eth @v — consider refining the interaction on frame content rendering during its “state transitions”. Feels a lil like a modem internet slideshow right now — how can it be either dramatically faster or more fluid feeling. Maybe speed is the main thing to focus on…

CTO @ OpenSea. Fmr. Co-Founder of Dharma Labs. 

Opinions my own

Relatedly, what does the frames paradigm look like if it’s mediated over websockets v POSTs. Could open a much richer design space for frame experiences — particularly if the frame host can push updates to the rendered image / buttons @dwr.eth

100%. requiring the entire view to be pushed to the viewer fully rendered is a 15+ years loss of ux evolution. the need for dynamic loading is a must for today’s expected user experience

/bettik founder /outercorps stalwart | ex-binance, ex-celsiusX

there’s also the element of scalability for developers.

opening up a long lived socket connection for every load of a frame as users scroll the feed could be draining to our resources.

👨‍💻 /uno and /outside, @unofficial

the app could shut down the connection when the user scrolls the frame out of view?

it consumes a ton of resources both ways. a lot of bandwidth and CPU cycles burned for each handshake open/close.

but the user is only engaging one frame at a time