sammybauch.eth
@sammy
new miniapp from me, megapool - join or create pools to win the /megapot jackpot together - contribute ETH or USDC - ETH swapped for USDC via @aerodrome - winning pool uses @splits to distribute propotionally - no fees (i get 10% of ticket cost as referrer) https://megapool-frontend.vercel.app
23 replies
37 recasts
177 reactions
sammybauch.eth
@sammy
pool here for tomorrow's drawing! ( we aren't gonna win dont go crazy) https://megapool-frontend.vercel.app/pools/0xcbd6B2C57bb9eF142a3582114B23c507614B8B7C
2 replies
0 recast
9 reactions
sammybauch.eth
@sammy
tbh the minapp / minikit docs and devx are not great! linking to pages other than index, handling actions for miniapp context vs otherwise (is a miniapp on desktop in the miniapp context?), caching of the manifest
2 replies
1 recast
6 reactions
sammybauch.eth
@sammy
image sizes, like come on. i took the example images from minikit and replicated the exact dimensions and this looks like crap
0 reply
0 recast
7 reactions
Soheybuildson.base
@sohey
Hey @sammy, thanks for the feedback! Just to make sure I address your concerns: * linking to pages beyond index (just an FYI Minikit uses Next.js-style routing https://nextjs.org/docs/app), * handling actions inside vs. outside the miniapp context (you can use useIsMiniApp() from Farcaster SDK to determine where the app is being loaded https://miniapps.farcaster.xyz/docs/sdk/is-in-mini-app), * Image resolution for Minikit we ship with the correct image sizes as required. But we do have some documentation here about what is required in the Manifest https://docs.base.org/wallet-app/mini-apps#metadata Are there any other pain points that are specific to Minikit documentation that we could do better?
1 reply
0 recast
2 reactions
