Farcaster Devs

Farcaster Devs: Your Feedback is Requested

we published a draft spec for App Frames 
https://warpcast.notion.site/app-frame-spec

App Frames will replace Mini Apps and provide better performance, an expanded API, and won't require allowlisting

questions and comments are appreciated

Building @warpcast and @farcaster, new dad, like making food

I hope I got it wrong, but it seems app frames take more of farcaster specific direction rather than previous generic mini-app approach.

I'm sure many would love to support their app outside of farcaster as well, e.g. telegram, world app, standalone web app.

But I will also appreciate if the actual spec implementation will be more of plug-in rather than the framework for app frame development.

Happy to see there will be an SDK to simplify authentication as well as leveraging farcaster specific functionality.

Not many specific cases for now, it's too early to be certain, but still wanted to share so you guys keep that in mind :)

1) Is primary button optional? I understand it's good to align the UX, looks nice, but might be an over-kill, especially if you already have button components with logic backed-in, and handling additional button logic doesn't make it appealing to me. 

2) ethereumProvider - I assume should work fine with Privy, right, or should be handled separately? does this make mini-apps transaction spec obsolete?

is there something specific that makes you think it'll be hard to support apps outside Farcaster?

I think it should be fairly straightforward to take an application and make it work as a Farcaster App Frame or standalone or for another platform

Mini apps will eat the internet | Latest drop: TRIVIA 💸| Building : /large /fctrivia /miniapps /flappycaster /jeeves /source @degentip @playsource /jump

yah, seems alright :)

I think primary button feature gave me this initial impression 😅

This is actually closer to Telegram than it was before

Atm both TG & World provide similar SDKs, with platform specific nuances or unique features you would have to contextually handle 

So think this is actually a +1 towards omnichannel apps