frames

All relatable pain points

But, frames started with the core idea of “apps in a feed”

> so as much as they inherit the properties of being an app

> they’re also inhering the properties of a feed item, i.e, they are non-static in your discovery, easily missable, etc

I don’t think so they should be evolved to fit the pain, instead I feel dev will double down on GTM aspects of frame

Frame feedback day 🫂

Frames would be so much more interesting in other clients if they weren't forced to communicate all the info in the form of an image 

Would love to move from current return structure to a more generalized json response that can contain both the generated image and the data used to construct that

This would make it a lot easier for devs to explore different form factors while still keeping it compatible with any warpcast-esque implementation

While letting anyone remix the frame experience

Mini apps will eat the internet | Latest drop: TRIVIA 💸| Building : /large /fctrivia /miniapps /flappycaster /jeeves /source @degentip @playsource /jump



我认为，框架的信息应该可以以其他形式传递，而不仅仅是图像。如果可以将返回结构更改为通用的JSON响应，这将使开发者更容易探索不同形式因素，同时保持与Warpcast等实现的兼容性，这将使框架的体验更加灵活。