Content
@
0 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
1/ Today, the frame-related legos are confusingly named. Frames v2 will simplify this and make it easier to understand for users and developers. Status quo: 1. Frames can appear in a feed and DCs 2. The Explore tab is permissioned and mixes "frames", "mini-apps", "actions" together; cast actions are siloed in a separate experience; composer actions have 2 different discovery experiences. 3. Frames that are called from the composer or a cast are called "actions"
2 replies
9 recasts
81 reactions
Dan Romero
@dwr.eth
In Frames v2: 1. Everything is a frame 2. You can call a frame via a "context" -- the feed, DC, a dedicated my frames screen, or a menu in a cast or composer 3. Frames also move from ephemeral experiences to something that can be added by a user to their client for quick access. This should significantly improve retention. 4. Frames also move to being a web app—nearly anything you can build in a browser, you should be able to build in a frame. 5. And we're adding a new developer primitive: notifications. Rather forcing a developer to send a Direct Cast that might end up in the Requests inbox, we're allowing developers to send notifications to users main notification feed (and the user has full control to opt in / out). 6. Finally, Frames v2 will improve the UX and reliability of onchain transactions.
3 replies
4 recasts
18 reactions
rafa
@rafa
Based on what I understand, frames are part of the protocol correct? Not part of only Warpcast?
1 reply
0 recast
1 reaction
