Varun Srinivasan
@v
We're going to say goodbye to Frames v1 on July 31st. When we announced miniapps (v2 frames) back in November, we promised to support the old standard for 6 months, to make the transition as smooth as possible. Now that time has come. Most people are building and using miniapps which we are excited about, and the old frames are slowly disappearing from the timeline. What happens next? On July 31st, we'll slowly stop rendering frames and cast actions in feed. Both these features are seeing little to no usage. In the coming weeks, we may also make changes to make cast actions less prominent in the UI to make space for some new features we're working on. Why is removing frames important? It's a lot of work to support older standards and slows down the team from shipping things that people want. No new teams are building frames anymore, and existing teams have largely moved over to miniapps.
30 replies
34 recasts
287 reactions
Mikado
@mikadoe.eth
I might be wrong but something I notice still missing with mini apps is sharing personalized data. V1 frames could pull personalized data and show them in the embed (example the duolingo frame by nikolaii) but as I understand for mini apps to do so there should be a dedicated subdirectory in the website to be shared as the embed.
1 reply
0 recast
7 reactions
Tony D’Addeo
@deodad
you can share any sub paths and serve them each with their own image + button + page to open to https://miniapps.farcaster.xyz/docs/guides/sharing
1 reply
1 recast
3 reactions
