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
12 recasts
130 reactions
phil
@phil
Iām fine with the change. At some point, please consider having better support for the cast action to miniapp pipeline.
1 reply
0 recast
3 reactions
Varun Srinivasan
@v
Yes this does not affect cast or composer actions. We will improve support for those soon
1 reply
0 recast
4 reactions
phil
@phil
To clarify, it's only possible to launch a v1 Frame from Cast Actions today, not a v2 Frame (aka miniapp). Some people have a hack where they are chaining Cast Action -> v1 Frame with button -> Miniapp. This will break that flow.
1 reply
0 recast
3 reactions
scottrepreneur
@scottrepreneur.eth
Would love to see mini apps in the cast action flow here
1 reply
0 recast
2 reactions
Tayyab - d/acc
@tayyab
Yes, I would also like to see this. Icebreaker just launched its mini app this week. This was an action we wanted to build. Supportive of deprecating frames v1. We should commemorate what it meant to us though š
0 reply
0 recast
4 reactions