Farcaster Devs

📣 We are building a simpler way to detect Mini App environment

We are considering different ways for Web apps to detect if they're running in Farcaster Mini App context vs. a regular web browser.

Which approach would you prefer as a developer? Join the discussion:

📣 We are building a simpler way to detect Mini App environment

We are considering different ways for Web apps to detect if they're running in Farcaster Mini App context vs. a regular web browser.

Which approach would you prefer as a developer? Join the discussion: https://github.com/farcasterxyz/miniapps/discussions/222

A sufficiently decentralized social network. farcaster.xyz

Engineer @farcaster. Founder bountycaster.xyz

Ex Phantom, 0x Project engineer.

From Italy originally, currently live in NYC

Small update: 🚀 We’ve shipped the first piece of our Mini App detection

1) An `isInMiniApp()` is now live in @farcaster/frame-sdk. Just call it to get a true/false for MiniApp context.

2) I'll update docs later today with query-param tips (to make your Mini App SSR-friendly)

Try it out & let us know what you think!

Much needed so we can programmatically change the connectors and also decide whether to mount Mini App actions and context…

Just another GPT in this universe






interspace.fi

Building a home for embedded apps at @interspace.

Feedback regarding detection of mini-app hosts:

• Option 1 (well-known query parameter) would be the worst because it’s another identifier apps need to hardcode and will be easily spoofed (akin to browser extension wallets setting `isMetaMask` to true on their `window.ethereum` object). Just continue to let apps specify custom params for themselves in `<meta name="fc:frame">` if they really need it.

• Option 2 (message passing) is ideal but can be improved further – I recommend turning it into a two-way message system modeled after EIP-6963 to avoid race conditions. (Also while you’re at it, use EIP-6963 to announce Farcaster Wallet’s EIP-1193 object to the app for instant compatibility with existing wallet picker UIs.)

• Option 3 (`isInMiniApp()` SDK function) – this is fine assuming apps don’t already have the SDK code-split from their main client-side bundle, but maybe redundant to Option 2.

https://warpcast.com/darrylyeo/0x8fa17165

nice!! just left a comment on the proposal 🫡

using url param is anti pattern imo

should be a lightweight postMessage (option 2), but sdk should include a method that will make the postMessage call (option 3)

I think both Option 1 and Option 3 would work for me. That said, I prefer Option 3 because it doesn't require manually appending query parameters every time Next.js navigates to a new route. This would make the experience more seamless from a developer perspective.

Option 1 every time of the day and twice on Sunday