Mini Apps

Farcaster Devs

New proposal to allow Mini Apps to set a path and query params to be used when clients share the Mini App URL.

https://github.com/farcasterxyz/miniapps/discussions/227

mini app devs your feedback is appreciated on this proposal to give more fine grained controls to developers when a user wants to share while using an app

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

cto @ bwl.gg, 100M+ users (bdut.ch) 🙏 $eggs is life

crafting farcaster.in + terminal.co + @usetab

product /builders-garden /farville | 
 organizing /just-frame-it | hosting a web3 hub in rome /urbe-eth /ethrome 🇮🇹🐺

https://limone.lol

building /farcade | /farworld | /degentlemen

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

cc @vrypan.eth @chuckstock @moe @mjc716 @limone.eth @warpcastadmin.eth @jc4p @carlos

Michelada connoisseur. Chief Onchain Officer at /area51 since 2022 AD. Focused on digital art, tech & crypto. https://gramajo.carrd.co

friendly neighborhood shitcaster / building @pinetree

98% overlapping venn diagram already

URL bar is not in the Mini App circle

and Mini App SDK + Add is not in the In-App Browser circle

Was wondering this yesterday after dcs with @gramajo.eth — what’s the likelihood that the mini app view gradually becomes an in-app browser?

got it, seems sensible to use whatever og:image meta tag you had at the particular URL being shared (see https://github.com/farcasterxyz/miniapps/discussions/227) 

wdyt @gabrielayuso.eth

the question I have is one I've shared before. does the dev have control of what image card is loaded when the link (with params) is shared outside of farcaster? or does it always default to the image card in the manifest? Would love to have dynamic image cards that work outside of farcaster.