Content pfp
Content
@
https://warpcast.com/~/channel/frames-devs
0 reply
0 recast
0 reaction

Varun Srinivasan pfp
Varun Srinivasan
@v
If you've built a frame that returns images, do you: a) dynamically generate them b) return static images If you pick (a), would be useful to know if you're doing this out of necessity or convenience. This feedback would be very helpful for some perf optimizations we're working on.
27 replies
2 recasts
38 reactions

Daniel - Bountycaster pfp
Daniel - Bountycaster
@pirosb3
I do a) out of to necessity. This approach allows me to incorporate additional text directly onto the images for users navigating the interface. If there was an alternative to display text labels on every frame, I would be less reliant on dynamic image
0 reply
0 recast
2 reactions

Will Papper pfp
Will Papper
@will
I’ve done both. A only when needed (e.g. because I’m fetching realtime data) Having control over cache busting let me change the update frequency as needed. Took a bit longer to set up but was quite nice once it was running
0 reply
0 recast
1 reaction

aaalex.eth 🎩 pfp
aaalex.eth 🎩
@aaalex.eth
Hey Varun. For ensframe we return dynamic images because it's a much better experience. For example showing listings, the point of the frame is to provide as much info + cta. If we had static image as the frame, it kinda defeats the purpose.
1 reply
0 recast
1 reaction

Stephan pfp
Stephan
@stephancill
If you consider frames to be mini apps that behave differently depending on the user there is no other way than dynamic images with that being said, the first frame should probably be static but i usually define that in jsx because it's more convenient
0 reply
0 recast
3 reactions

Corbin Page pfp
Corbin Page
@corbin.eth
Both and only do (a) when necessary. Like returning an image with information based on the context of the user…wallet balance, pfp, etc
0 reply
0 recast
1 reaction

Devin Conley pfp
Devin Conley
@dcon.eth
a) dynamically generate images lazily when requested. This is out of necessity, there's a lot of variety and state change, so not possible to precompute content (for reference this is for a multiplayer game /tournament )
0 reply
0 recast
0 reaction

Cameron Armstrong pfp
Cameron Armstrong
@cameron
Both but do a) in the context of specific user info on cards. We try to generate stuff ahead of time if we can (usually at build time) You can tap through this to see an example - note that these preview cards change as creators publish new content on like substack/YT Https://seemore.tv/cameron
0 reply
0 recast
0 reaction

Sinaver pfp
Sinaver
@sinaver.eth
a) both necessity and convenience: adding user specific info, as well easier with making changes/upgrades to relatively constant images.
0 reply
0 recast
0 reaction

Shashank  pfp
Shashank
@0xshash
held off on few ideas because of complexity with a) for fetching realtime data
0 reply
0 recast
0 reaction

Joshua pfp
Joshua
@hashwarlock
Dynamically generate them
0 reply
0 recast
0 reaction

Stephen Caudill pfp
Stephen Caudill
@mrmemes.eth
(a) - out of necessity
0 reply
0 recast
0 reaction

Peter Kim pfp
Peter Kim
@peter
both, I have an image generation api route for each "page" of our frame app it's a mess, but haven't had time to sit down to think of an easier way save us
0 reply
0 recast
0 reaction

Andrew Jiang pfp
Andrew Jiang
@ok
A) out of necessity
0 reply
0 recast
0 reaction

Nico.cast♣️ pfp
Nico.cast♣️
@n
Necessary when dealing with user specific data
0 reply
0 recast
0 reaction

Hoot 🎩 pfp
Hoot 🎩
@owl
Mix of both, we're rendering dynamic data like the numbers players have picked or the countdown to the next draw in the Powerbald frame. Some other screens are static
0 reply
0 recast
0 reaction

Darryl Yeo 🛠️ pfp
Darryl Yeo 🛠️
@darrylyeo
(a) – out of necessity
0 reply
0 recast
0 reaction

doug pfp
doug
@pfeffunit
Depends! If it’s some static image I’ve generated then ahead of time. Using ImageMagick the old fashioned way. Just put them up on s3 and you’re done.
0 reply
0 recast
0 reaction

Sid Gandhi pfp
Sid Gandhi
@sidg
a huge part of the appeal is dynamic — way cooler experiences possible but if we’re just rendering html into an image (easiest way) then you might as well allow iframes to be returned, but disable all events/interactions
0 reply
0 recast
1 reaction

Hang Yin pfp
Hang Yin
@h4x3rotab
Dynamic image is a must. Best to allow SVG rendering on mobiles. It’s fast and expressive. But if it cannot, at least to allow the frontend to render the frame and load the image async.
0 reply
0 recast
1 reaction