Farcaster Devs

Farcaster Devs: Your Feedback is Requested

we published a draft spec for App Frames 
https://warpcast.notion.site/app-frame-spec

App Frames will replace Mini Apps and provide better performance, an expanded API, and won't require allowlisting

questions and comments are appreciated

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

As far as I understand, the first screen (or the screen that lives in the cast) will just be a basic "open" button with a static image. Are there any plans to make it more interactive and customizable?
I see that one of the most popular frames has fairly primitive iterations, like "check me" and "share" buttons. Creating an app frame that would open a new modal for this type of frame would be overhead, I imagine.

"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

separately from App Frames we are consider how to improve the UX of embedded frames

what we've noticed is that frames with branching paths lead to a bad UX, most commonly expressed as "frames are slow" (see quoted cast)

so the thinking is how to do we streamline embedded frames to make them always be a great UX

stripping them down to a single button and removing text input (robust inputs require JS and should happen in an App Frame) will make them look better in feeds and give the user a clearer CTA

to answer your specific question: we've considered both completely static or like today where you can take an action that replaces the current frame with a new one 

I like the later since it supports the use cases you mentioned like "check me" followed by a "share"

Moxie Frame https://warpcast.com/nastya/0x928b8aed | CastAlerts bot t.me/CastAlertsBot | TX decoder https://github.com/3loop/loop-decoder

separately from App Frames we are consider how to improve the UX of embedded frames

what we've noticed is that frames with branching paths lead to a bad UX, most commonly expressed as "frames are slow" (see quoted cast)

so the thinking is how to do we streamline embedded frames to make them always be a great UX

stripping them down to a single button and removing text input (robust inputs require JS and should happen in an App Frame) will make them look better in feeds and give the user a clearer CTA

to answer your specific question: we've considered both completely static or like today where you can take an action that replaces the current frame with a new one 

I like the later since it supports the use cases you mentioned like "check me" followed by a "share"

https://warpcast.com/deodad/0x9835cdad