Matt
@mattlee
It is very clear that the only way mini apps are going to work is to have one standardized testing environment. If a mini app works in this testing environment and not your farcaster client, then that is a bug in your client not the mini app. It will be increasingly unfeasible for mini app devs to debug every farcaster client separately
5 replies
3 recasts
18 reactions
Samuel ツ
@samuellhuber.eth
yep, maybe I should setup a walletbeat / l2beat style compatiblity matrix that's hosted on a website and updated weekly as new features roll out across ? cc @sohey @linda I'd be down to maintain this list, though would appreciate if we could agree to ping me on breaking changes :D I don't have a git repo for the farcaster app client or TBA to automate any of the checks I am though notified on all new frame sdk features so at least I can add these for sure.
2 replies
0 recast
1 reaction
Matt
@mattlee
Wouldn’t that still put the responsibility on mini app devs to debug multiple clients? Seems backwards to me. The responsibility should be on clients to be able to host mini apps that meet standards
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
Nah. Means you can check what you can do in clients at least instead of guessing Also there’s a compatibilities feature in the sdk today you can use to block / announce what you need to clients But in the end you will never know it works across devices, screen sized and environments besides running it there Typical frontend development issue.
1 reply
0 recast
1 reaction
