base.base.eth

**Mar 12**

## We’re Updating How Apps Work in the Base App.
Over the next few weeks, we’re rolling out new [Base.dev](http://base.dev/) primitives for metadata, notifications, and distribution - designed to simplify how apps are built, managed, and surfaced. As part of this shift, the Base App will move off the Farcaster mini-app spec and Neynar-powered infrastructure on April 9.

The goal is straightforward: to make building more seamless by removing custom specs and enabling standard web apps with wallet connectivity, powered by industry standard tooling and Base-native infrastructure.

Below is what’s changing, when it’s happening, and how to migrate.

## What’s Changing:

1. **Self-Managed Metadata (Mid-March)**  
   You’ll be able to manage your app’s metadata directly in [Base.dev](http://base.dev/), including icons, taglines, descriptions, and screenshots. Today, this data comes from your Farcaster mini-app manifest. But soon, you’ll have a dedicated dashboard in [Base.dev](http://base.dev/) to update it directly.

Your existing metadata has already been backfilled, so none of it disappears.

2. **[Base.dev](http://base.dev/) Notifications API (April 9)**  
   We’re introducing a first-party Notifications API. So instead of managing Farcaster tokens, FIDs, or third-party webhooks, you’ll send notifications directly to wallet addresses via [Base.dev](http://base.dev/). Our builder platform will then handle user permissions, opt-in state and delivery. Basically, notifications join metadata and distribution in a single [Base.dev](http://base.dev/) surface.

3. **Unified Browser + Standard Web Infrastructure (April 9)**  
   On April 9, support for the Farcaster mini-app spec and Neynar-powered metadata/notifications inside the Base App will end.

From that point forward:
   - Your app operates as a standard web app
   - Wallet connectivity works out of the box
   - No custom mini-app SDK is required

If you distribute through Farcaster clients like Warpcast, those integrations can remain in place. This change applies specifically to the Base App.

## Tooling Guidance:
If you're currently using mini-app-specific wrappers (like MiniKit or OnchainKit) or relying heavily on Farcaster-specific tooling, we recommend migrating to standard web3 tooling like SIWE for authentication, and wagmi/viem for wallet connection and onchain transactions.

The team has created an agent skills repo so your preferred agent can help you build with ease, including a mini app migration skill: [Migration Skill](https://github.com/base/skills/blob/master/skills/convert-farcaster-miniapp-to-app/SKILL.md)

And more info can be found in our docs here: [Migration Docs](https://docs.base.org/mini-apps/mini-apps/quickstart/migrate-to-standard-web-app)

## Migration Guide by App Type:
For most builders, migration takes around half a day. Here’s a guide on what you need to do depending on your current setup:

1. **You Have a Regular Web App (No Farcaster SDK):**  
   - Ensure your app is registered on [Base.dev](http://base.dev/)
   - Update your metadata in the new dashboard (mid-March)
   - Optionally integrate the [Base.dev](http://base.dev/) Notifications API

2. **You Have Separate Web and Farcaster Apps:**  
   - Register your web app with [Base.dev](http://base.dev/)
   - Fill out metadata
   - Ensure that your web app's URL is set as the primary URL
   - Now your mini app will still work on Farcaster and TBA will serve the web app

3. **You Have a Hybrid App (Works on Web + Farcaster):**  
   - Detect environment where necessary using the Farcaster SDK’s isInMiniApp utility
   - Ensure Farcaster-specific content and actions are not shown to regular web users
   - Migrate notifications to the [Base.dev](http://base.dev/) API
   - After April 9, your app will behave like a web app inside the Base App, while still functioning in Farcaster clients if you choose.

4. **Your App Has No Standalone Web Experience:**  
   - Create a standard web version of your app (or add a web-compatible layer)
   - Use Sign-In with Ethereum (SIWE) instead of Sign In with Farcaster
   - Replace Farcaster SDK methods with standard web APIs
   - Use wagmi or viem for wallet and onchain interactions
   - Register your app on [Base.dev](http://base.dev/)
   - Update your metadata in the dashboard
   - Optionally integrate the [Base.dev](http://base.dev/) Notifications API

We’re intentionally sequencing this across multiple weeks to avoid disruption and ensure the user experience remains consistent while builders migrate.

## FAQ:
1. **What happens if I don’t migrate by April 9?**  
   After April 9, apps still relying on the Farcaster spec or manifest will not function properly inside the Base App, so migration is required to maintain compatibility.

2. **Is the platform moving away from the "Mini App" framework?**  
   Yes. We are transitioning away from the integrated mini-app model. Partners and developers should prioritize their web-based versions for user access moving forward.

3. **Will my analytics or user attribution change?**  
   Core engagement metrics and delivery reporting will continue to work. The underlying delivery mechanism changes, but your ability to measure sends and engagement remains intact.

4. **What happens to existing notification opt-ins? Will there be rate limits or pricing for the new Notifications API?**  
   Existing user opt-ins will carry over. Users do not need to re-subscribe when the new Notifications API goes live. There are no new fees being introduced with this launch. Any usage guidelines or limits will be clearly communicated in advance.

5. **Are rankings or discovery changing as part of this update? How will the user experience change for accessing third-party apps and wallets?**  
   No apps are losing visibility as part of this migration.

6. **Why not support both systems long-term?**  
   We heard consistent feedback from builders that maintaining multiple specs added unnecessary complexity. Standardizing on a single, web-native stack reduces overhead and lets us ship improvements faster.

7. **What is the status of the Farcaster social feed within the app?**  
   The Farcaster social feed is being deprecated in favor of a trading feed.