"frames are slow"

after digging into this deeper I've come to appreciate this isn't about network latency or compute to generate images but the high level of  interactivity we've come to expect from apps and the inherent limitations of trying to embed this directly into a social feed

for ex: looking at a relatively simple and common flow like an ERC20 swap:
- input: 2 currency inputs, 2 token selectors, settings, submit
- dynamic: token selectors show tokens I own, changing 1 input will recompute implied values of other inputs, conversion rate is shown including total USD value, sell input goes red if exceed my balance
- 3 steps: input -> review which shows fees, gas estimate, rate, slippage -> tx monitoring

there is no way to build an equivalent experience in the existing frames model

this is why I'm excited about the new direction we're exploring that barbells a simple artifact that's easy to embed in feeds with the app frame where applications can deliver rich interactive Farcaster-native experiences

Building @warpcast and @farcaster, new dad, like making food

I like Telegram model of providing little interface space that is rendered natively on the client. This way there's no loading delay and app design is uniform. It doesn't necessarily have to be custom UI system but a stripped down HTML akin to Google's AMP

Building /frametown. Amusement, wonder, and uncertainty ✴︎ libred.org


It’s still possible to use full WebView. There are also UI Controls that allow to create inline views for

I didn't think TG used a stripped down markup language—thought it was plain ole web