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

This is gonna be big

I see it as an equivalent to how Instagram (and other web2 social apps) render links in feed

The design space is *even bigger* than the current Frame spec - you can literally embed your whole website

Very bullish :)

Like:
- Permissionless nature of domains (no more allowlisting)
- UI parity with web2 social apps (see attached cast)
- Primary Button for persistent CTA
- Variety of API endpoints (especially openFarcasterURI, which didn't seem possible with prior ComposerAction spec)

Wish that there was no requirement for splash screen (feels unnecessary; I think Warpcast should have a simple default loader for all App Frames)

Also - does the ChannelProfileLaunchContext endpoint pull from the external link field in Channel Profiles? What's an example of that launch context?

Overall, great work on this!

Like:
- Permissionless nature of domains (no more allowlisting)
- UI parity with web2 social apps (see attached cast)
- Primary Button for persistent CTA
- Variety of API endpoints (especially openFarcasterURI, which didn't seem possible with prior ComposerAction spec)

Wish that there was no requirement for splash screen (feels unnecessary; I think Warpcast should have a simple default loader for all App Frames)

Also - does the ChannelProfileLaunchContext endpoint pull from the external link field in Channel Profiles? What's an example of that launch context?

Overall, great work on this!
https://warpcast.com/zd/0x54250147

building /fc-marketplace // prev. rabbithole, village global

> the idea is this makes the loading experience feel more native to users vs
feeling like an in-app browser opening any ole webpage

I know you mentioned "feeling more native to users" in our last back+forth, but I'm not sure I know what that means? Native to what?

If goal is to make it FC native → I'd vote for Warpcast default loader

If goal is to make it feel {project} native → then doesn't the use case become "an in-app browser opening any ole webpage"?

I wouldn't be upset if the latter is the case btw, but want to clarify

> does the ChannelProfileLaunchContext endpoint pull from the external link field in Channel Profiles? What's an example of that launch context
yes

> splash screen
the idea is this makes the loading experience feel more native to users vs
feeling like an in-app browser opening any ole webpage