Migrate additional information from previous section

Author: ericbrown99

docs/base-app/miniapps/debugging.mdx

@@ -327,7 +327,7 @@ await sdk.actions.ready({ disableNativeGestures: true });
 
 1. **Local Testing**: Use ngrok or similar to expose localhost  
 2. **Cast in DM**: Share your app URL in a DM to yourself  
-3. **Test Different Clients**: Test in Warpcast mobile and other Farcaster clients  
+3. **Test Different Clients**: Test in Farcaster mobile and other Farcaster clients  
 4. **Check Different Devices**: Test on both iOS and Android if possible
 
 <Info>

docs/base-app/miniapps/mini-apps.mdx

@@ -21,7 +21,7 @@ If you're already using MiniKit and experiencing issues, you can refer to our de
 ## Authentication
 
 <Warning>
-As a general rule of thumb, we recommend that you save authentication that requires an interaction for interactions that require it(eg. buying something, viewing personalized pages etc)
+Only authenticate when needed to talk to your backend. Do not block first load with auth prompts. Defer auth to the moment a protected action occurs (e.g., buy, personalize, post).
 </Warning>
 
 Below we will quickly cover the different methods of authentication offered for mini apps and how well each of them work in Base App:
@@ -40,9 +40,9 @@ This is the expected flow for end-users to Sign In with Farcaster in your mini a
 </Tab>
 
 <Tab title="Wallet Auth">
-Because users in Base App have an in-app smart wallet that doesn't require any app switching, we recommend wallet authentication as the primary method of authentication for developers looking to create a persisted session for the mini app user.
+Base App users already have a Base Account that is instantly available in-app. Prefer leveraging this auto-connected wallet; avoid showing an explicit "Connect Wallet" flow.
 
-As described below, we don't think it's the best practice to prompt the user to log in before that authentication will allow them to do something else in your mini app, but for cases where do you want a secure, persisted session, using a wallet connection is a great option.
+Only present a connect/switch wallet UI if you intentionally support a different wallet. Never make this a blocking step—let users explore, and gate only at the point-of-need.
 </Tab>
 
 <Tab title="Context Data">
@@ -57,6 +57,10 @@ Something important to note is that because of how the current mini app spec is
 
 </Tabs>
 
+<CardGroup cols={2}>
+  <Card title="Feature: Authentication" icon="key" href="/mini-apps/features/authentication" />
+</CardGroup>
+
 ## Deeplinks and SDK Actions
 
 The official mini apps SDK offers a [set of actions](https://miniapps.farcaster.xyz/docs/specification#actions) (which MiniKit offers as well) so that users of your mini app can be led to do things back in clients like Base App (e.g. compose a cast, view a profile, etc).
@@ -80,7 +84,7 @@ As a mini app host, we expose an [EIP-1193 Ethereum Provider](https://eips.ether
 By using the [Wallet](https://docs.base.org/builderkits/onchainkit/wallet/wallet) component offered in OnchainKit/MiniKit
 
 <Note>
-If you run `npm create onchain --mini`, your mini app will have a "Connect Wallet" button already set up
+If you run `npm create onchain --mini`, the template includes a "Connect Wallet" button. In Base App, you typically don't need to show a connect button because the Base Account is already available. Show connect/switch only if you support alternate wallets—and do not gate first use behind it.
 </Note>
 </Tab>
 
@@ -321,7 +325,7 @@ The following Mini App SDK features are **not currently supported** in Base App:
 
 * Direct HTML links to third-party websites (`<a href=`, `<Link href=`)  
   * Note: You can instead use `sdk.actions.openUrl()` to safely open a third-party website in our in-app browser
-* Warpcast/Farcaster composer intent URLs (`warpcast.com/~/compose`, `farcaster.com/~/compose`)
+* Warpcast/Farcaster composer intent URLs (`farcaster.com/~/compose`, `farcaster.com/~/compose`)
   * Note: You can instead use `sdk.actions.composeCast()` to compose a cast directly in Base App
 
 #### Notifications are not yet supported
@@ -350,7 +354,7 @@ The following Mini App SDK features are **not currently supported** in Base App:
 ### Development Notes
 
 * Use `sdk.actions.openUrl()` for external navigation instead of direct HTML links  
-* Use `sdk.actions.composeCast()` instead of Warpcast composer URLs  
+* Use `sdk.actions.composeCast()` instead of Farcaster composer URLs  
 * Implement visual feedback alternatives for haptic feedback  
 * Avoid relying on location context for core functionality
 * To conditionally render functionality based on the user's client, check `context.client.clientFid` (Base App returns `309857`)

docs/docs.json

@@ -458,16 +458,15 @@
             "group": "Growth Playbook",
             "pages": [
               "mini-apps/growth/optimize-onboarding",
-              "mini-apps/growth/build-viral-mini-apps",
-              "mini-apps/growth/add-analytics"
+              "mini-apps/growth/build-viral-mini-apps"
             ]
           },
           {
-            "group": "Mini App Features",
+            "group": "Features",
             "pages": [
               "mini-apps/features/overview",
               "mini-apps/features/manifest",
-              "mini-apps/features/authentication",
+              "mini-apps/features/Authentication",
               "mini-apps/features/embeds-and-previews",
               "mini-apps/features/search-and-discovery",
               "mini-apps/features/sharing-and-social-graph",
@@ -488,20 +487,21 @@
               {
                 "group": "MiniKit",
                 "pages": [
+                  "mini-apps/technical-reference/minikit/overview",
                   "mini-apps/technical-reference/minikit/provider-and-initialization",
                   {
                     "group": "Hooks",
                     "pages": [
                       "mini-apps/technical-reference/minikit/hooks/useMiniKit",
-                      "mini-apps/technical-reference/minikit/hooks/useAddFrame",
-                      "mini-apps/technical-reference/minikit/hooks/useNotification",
                       "mini-apps/technical-reference/minikit/hooks/useOpenUrl",
                       "mini-apps/technical-reference/minikit/hooks/useClose",
                       "mini-apps/technical-reference/minikit/hooks/usePrimaryButton",
                       "mini-apps/technical-reference/minikit/hooks/useViewProfile",
                       "mini-apps/technical-reference/minikit/hooks/useComposeCast",
                       "mini-apps/technical-reference/minikit/hooks/useViewCast",
-                      "mini-apps/technical-reference/minikit/hooks/useAuthenticate"
+                      "mini-apps/technical-reference/minikit/hooks/useAuthenticate",
+                      "mini-apps/technical-reference/minikit/hooks/useAddFrame",
+                      "mini-apps/technical-reference/minikit/hooks/useNotification"
                     ]
                   }
                 ]

docs/images/minikit/metadata-guidelines.png

@@ -1,16 +1,34 @@
 ---
 title: Design Patterns
-description: Principles and patterns to build social, repeat-use experiences
+description: Design best practices for Mini Apps
 ---
 
-Importing core content from Thinking Social.
+### Mobile-first
+- Use legible font sizes, line heights, and adequate contrast for small screens.
+- Help people concentrate on primary tasks and content by limiting the number of onscreen controls while making secondary details and actions discoverable with minimal interaction.
+- Use tab navigation to simplify movement within the app.
+- Ensure layouts adjust smoothly to various screen sizes and orientations.
+- Design for vertical scrolling rather than horizontal, as it’s more natural on mobile.
 
-<Note>
-This page will summarize design principles and link to the detailed guide below.
-</Note>
+![Metadata Guidelines](/images/minikit/mobile-first.png)
 
-<Card title="Build Viral Mini Apps (detailed guide)" icon="users" href="/base-app/build-with-minikit/thinking-social" />
+### Onboarding and guest experiences
+- Your app metadata will be the first thing a new user will see, and is what they’ll base their first impression on. Aim for your metadata to provide helpful context, and properly set expectations with new users on what your app does.
+Consider the experience for new users opening your app for the first time. Include your value props, a light onboarding flow, or easy access to guides / FAQs from your homepage to help new users orient themselves
+- No technical jargon - language is user-friendly
+- Value is immediately apparent to new users
+- Defer auth until needed. Triggering the auth tray as the first thing a user sees on app open can create a jarring experience, and asks users to take an action they may not be confident in before demonstrating the value of your app.
+- Include a splash page for sign-in if needed.
+- Consider adding a “guest” mode, allowing users to explore your app before asking them to sign in.
 
-TODO: Add condensed patterns and examples tailored to Mini Apps (identity, co‑creation, rituals).
+![Metadata Guidelines](/images/minikit/metadata-guidelines.png)
 
 
+### Gasless transactions
+Enable users to transact on your apps without needing gas by using wallet solutions that support gas sponsorship like [Base Account and Paymaster](/base-account/improve-ux/sponsor-gas/paymasters).
+
+### Legible identity
+Never use wallet addresses. Instead, leverage identity solutions like ENS and [Basenames](/base-account/basenames/basenames-onchainkit-tutorial).
+
+### Localization
+Many of our users are located around the world. Apps that are localised for each region will perform significantly better. For next.js apps, you can use Next.js Internationalization to localize your app.

docs/images/minikit/mobile-first.png

@@ -1,8 +1,16 @@
 ---
-title: OnchainKit
-description: How to leverage OnchainKit components and MiniKit together
+title: 'OnchainKit'
+description: 'Ready-to-use components to accelerate the development of your mini apps.'
 ---
 
-TODO: Document recommended OnchainKit components for Mini Apps, integration tips, and examples.
+OnchainKit is a React-based design system for accelerating the development your apps. It provides pre-built, reusable full-stack components that follow Base's design guidelines, ensuring consistency and high-quality user experience.
 
+## Get Started
 
+Install the UI Kit with NPM:
+
+```bash Terminal
+npx create-onchain@latest --mini
+```
+
+Explore the full component library and usage examples in the [OnchainKit docs](/onchainkit/getting-started).

docs/mini-apps/design-ux/design-patterns.mdx

@@ -13,23 +13,55 @@ Supported approaches:
 
 <Tabs>
 <Tab title="Sign In with Farcaster / Quick Auth">
-Base App supports SIWF in‑app, enabling social identity without leaving the app. Quick Auth can issue a JWT to persist session state.
+Base App natively supports SIWF in-app, enabling social identity without leaving the app. Quick Auth can issue a JWT to persist session state.
+
+**User Experience in Base App:**
+- **Create Account Users** (new Farcaster accounts created during Base App onboarding): Users see a "Login request" tray with the SIWF message and can sign it directly with their passkey
+- **Connect Account Users** (existing Farcaster accounts connected during onboarding): Users are prompted to deeplink to Farcaster one-time only to register their wallet as an auth address, then enjoy seamless in-app sign-in thereafter
 </Tab>
 
 <Tab title="Wallet Auth">
-Base App provides an in‑app smart wallet. Use wallet auth for a persisted session when necessary, but avoid gating initial exploration behind connect.
+Base App provides an in‑app smart wallet that doesn't require app switching. Use wallet auth for a persisted session when necessary, but avoid gating initial exploration behind connect.
 </Tab>
 
 <Tab title="Context Data">
-All hosts return context data (including user). Use it for analytics or lightweight session hints, but do not treat as primary auth.
+All hosts return context data (including user). Use it for analytics or lightweight session hints, but **do not treat as primary auth** since context data can be spoofed by developers who create their own mini app hosts.
 </Tab>
 </Tabs>
 
-Best practices:
+## Implementation Example
+
+```tsx
+import { useMiniKit, useAuthenticate } from '@coinbase/onchainkit/minikit';
+
+function MyComponent() {
+  const { context } = useMiniKit();
+  const { user } = useAuthenticate();
+
+  // ✅ Safe: Use context for analytics only
+  const userFid = context.user.fid; // For analytics tracking
+  
+  // ✅ Safe: Use cryptographic verification for auth
+  const verifiedUser = user; // From SIWF or wallet auth
+  
+  // ❌ Unsafe: Don't rely on context for primary auth
+  // const isAuthenticated = !!context.user.fid; // Can be spoofed!
+  
+  return (
+    <div>
+      {/* Use verified user data for secure operations */}
+    </div>
+  );
+}
+```
+
+## Best practices
 
 - Gate wallet only at the point of onchain action
 - Prefer SIWF/Quick Auth for low‑friction identity
 - Use context for analytics; avoid using it as primary auth
+- Handle Base App's different authentication flows gracefully
+- Always use cryptographic verification for security-critical operations
 
 Further reading:
 

docs/mini-apps/design-ux/onchainkit.mdx

@@ -83,7 +83,7 @@ If your Mini App does not show in search, follow the debugging guide [here](/min
 ```
 
 <Note>
-For a visual mapping of how fields render, see the [Mini App specification reference](/mini-apps/features/search-and-discovery#how-metadata-works).
+For a visual mapping of how fields render, see the [Mini App specification reference](/mini-apps/features/search-and-discovery#visual-specifications).
 </Note>
 
 

docs/mini-apps/features/Authentication.mdx

@@ -3,6 +3,12 @@ title: Notifications (coming soon)
 description: Send relevant, rate‑limited notifications to users who saved your Mini App
 ---
 
-TODO: Add guidance for `useAddFrame` + `useNotification`, proxy route, and rate limiting.
+<Info>
+Notifications are not yet available in Base App but are planned for a future release.
+</Info>
+
+Push notifications will allow you to re-engage users who have saved your Mini App, driving retention and bringing users back at key moments like new content releases, achievements, or time-sensitive events.
+
+When available, notifications will be rate-limited and only sent to users who have explicitly saved your Mini App to their collection.