Start Here Farcaster Frames
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
How do you develop on top of the Farcaster protocol? Dive in. Focus is on giving you just as much documentation as needed as well as conceptual overviews and examples. We link out to detailed project documentation where used.
What are Frames?
Farcaster Frames brought custom interactive experiences to Web3 social where the full power of wallets, transactions and public information laying on blockchains can be used to the full imagination of dreamers, developers, artists and the anyone with internet access.
With Frames being as simple as one to four buttons, an optional input field and an image with each client rendering the layout as they see fit you can focus on the functionality to bring all you want to do in a simple format that can link out to webpages, do any kind of API call based on the logic of a button press and optional text input and sends back an new user interface to continue.
The layout with just buttons, an input field and showing a static image or GIF that is returrned based on the current context without the ability for video and sound means we are looking at a muted Gameboy or Nintendo DS style interface embedded into the social feeds of all of Farcaster.
Think everyone sharing the Gameboy game they play with all of their followers and online community every time they play and giving them the opportunity to also join in and play right away! Now imagine what you can do with it or how you can enable people to use your awesome tooling to enable even cooler experiences!
Where to Frames fit inside the Farcaster Architecture?
How to Frames work? learn more by clicking here.
For more on the Farcaster Architecture check the Architecture docs
How to build Farcaster Frames?
Quickstart building Frames is the best zero to hero guide on Farcaster Frames. It takes you from no idea about Frames to having your first frame in a mere couple of minutes. After your initial frame you are building a calculator getting familar with showing one frame after the other and connecting them with custom logic ran in the backend.