Varun Srinivasan
@v
We're considering ending support for v1 Frames in 3 months. Why? - It has little usage; most devs moved to miniapps - It simplifies the protocol for client builders + new devs. - It simplifies the UX for users. Only one type of "app" in the feed. Over 90% of devs we polled support this decision.
27 replies
14 recasts
135 reactions
Varun Srinivasan
@v
v2 Frames (now Miniapps) launched in November 2024. The eventual goal was to replace v1 Frames, but we supported both to make the transition easy for developers. Five months later, most developers have moved onto miniapps and are supportive of simplification. We plan to give developers another 3 months notice before ending v1 Frames support.
1 reply
0 recast
30 reactions
Varun Srinivasan
@v
Almost all v1 Frame features are supported in v2 Frames / Miniapps. We are aware of two that are missing: 1. One-shot mints and transactions. We plan to support some version of this in miniapps in the next year. It's not a high priority because it has not generated a lot of transactions historically. 2. Multi-button embeds in the feed. We don't plan to support these for miniapps. Lots of UI testing has shown that single buttons + full page miniapps is a better design pattern for users, developers and client builders.
2 replies
1 recast
13 reactions
Varun Srinivasan
@v
If you are building apps on Farcaster, your feedback on this is very helpful in informing our decision. If you are supportive, we appreciate a reply. If you are not supportive, we'd love to hear your reasons for why along with a link to your frame.
3 replies
0 recast
13 reactions
Mike | Abundance 🌟
@abundance
is it possible to launch a v2 from a cast action yet? that's one of the main reasons /impact has not moved to v2, since it's a major feature of the app. obv would not support terminating v1s without that workflow
0 reply
0 recast
0 reaction
