Farcaster Mini Apps

# Farcaster Mini Apps ## Docs - [Blog](/blog) - [Why Farcaster Doesn't Need OAuth 2.0](/blog/oauth): OAuth exists to let three separate parties (user → platform → third-party app) establish mutual trust. Farcaster is built on a decentralized architecture that collapses this triangle: - [Getting Started](/docs/getting-started): Mini apps are web apps built with HTML, CSS, and Javascript that can be discovered and used within Farcaster clients. You can use an SDK to access native Farcaster features, like authentication, sending notifications, and interacting with the user's wallet. - [Specification](/docs/specification): A Mini App is a web application that renders inside a Farcaster client. - [Authenticating users](/docs/guides/auth):  - [App Discovery & Search](/docs/guides/discovery): Making your Mini App discoverable is crucial for reaching users in the Farcaster ecosystem. This guide covers how to ensure your app is correctly indexed and visible in our mini apps catalogue. - [Migrating to a new domain](/docs/guides/domain-migration): While Mini Apps are designed to be associated with a stable domain, there are times when you may need to migrate your app to a new domain. This could be due to rebranding, domain expiration, or other business reasons. - [FAQ: Frequently Asked Questions](/docs/guides/faq): **Quick Answer**: A **manifest** is your app's identity document (one per domain), while an **embed** is social sharing metadata (one per page you want shareable). - [Loading your app](/docs/guides/loading): When users open Mini Apps in Farcaster they are shown a branded splash screen instead of a blank loading page like they would in a browser. Once your interface is ready to show the splash screen can be hidden. - [Farcaster Mini Apps: Manifests vs Embeds Developer Guide](/docs/guides/manifest-vs-embed): **Manifest** = Your app's identity and configuration (one per domain)\ **Embed** = Social sharing for individual p