Replies: 2 comments
-
|
endorse! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Endorsing this proposal as it'll be a nice QoL improvement for everyone, and also signaling that the Coinbase Wallet beta can support this out of the box! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The Embed Action Schema includes the following three fields that are also defined in the Manifest:
namesplashImageUrlsplashBackgroundColorThe primary intention behind these fields was to better support simple Mini Apps that didn't want to setup a Manifest file. In practice, the number of Mini Apps that aren't providing a Manifest is essentially zero outside of development.
We can simplify the Embed Action Schema by removing these properties and instead always resolving the these from the Manifest. This is slightly more work for Farcaster Clients hosting Mini Apps with the benefit of simplifying things for Developers who will no longer need to redundantly define these properties on each page and reason about what is the source of truth between the embed definitions vs manifest definitions.
Developers
After this proposal is accepted, developers should stop setting these attributes. This change is backwards compatible, if the attributes are there they can simply be ignored.
Farcaster Client
When launching a Mini App from an Embed, a Farcaster Client should look up the name and splash screen details from the Manifest. If there is no Manifest the app should show a generic loading screen and display the
domainin the header so that users are able to identify the site they are interacting with.Adopting
Since this proposal is backwards compatible for developers, this proposal can be adopted as soon as Farcaster Clients accept and update their implementations.
Beta Was this translation helpful? Give feedback.
All reactions