Skip to content

docs: clarify when Farcaster manifest is required for Mini Apps#1257

Open
Kubudak90 wants to merge 1 commit intobase:masterfrom
Kubudak90:clarify-mini-app-flows
Open

docs: clarify when Farcaster manifest is required for Mini Apps#1257
Kubudak90 wants to merge 1 commit intobase:masterfrom
Kubudak90:clarify-mini-app-flows

Conversation

@Kubudak90
Copy link
Copy Markdown

Problem

The Mini Apps documentation doesn't clearly distinguish between two different scenarios:

  1. Mini Apps within Farcaster Frames - These require a Farcaster manifest
  2. Standalone Mini Apps - These don't need a Farcaster manifest

Solution

Added a clear note box explaining when Farcaster manifest is required vs not required.

Checklist

  • Content follows Base documentation style guide
  • Technical accuracy verified

Add 'Which flow should I use?' section to help developers understand:
- When Farcaster manifest is required vs optional
- Decision tree for choosing migration paths
- Clear distinction between Base App-only and Farcaster-integrated apps

Fixes base#1247
@cb-heimdall
Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants