Farcaster Devs

frames are becoming mini apps! so i made a new mini app starter project on val town

https://moe--3238fa84059c11f0ac33569c3dd06744.web.val.run

✷ hono + react + tailwind
✷ mini app manifest, embed tags, webhook, sdk actions, wallet actions, and a welcome notification
✷ edit code in browser and instant deploy on save

✷ soon: store notification tokens and send notifications on schedule / on demand
✷ soon: some standard ui components
✷ soon: what else?

code is here: https://www.val.town/x/moe/MiniAppStarter

you can fork and deploy your own version in less than 30s

https://miniapp-starter.val.run/

big updates to my mini app starter/template with many improvements:

✷ saves user notification tokens and allows sending notifications to users (recurring + on demand), including handling multiple fc clients
✷ built in db (blob storage)
✷ dynamic frame embed images and icon
✷ react-router navigation

so now it comes with everything you need for full-stack apps 🚀

full open source code on val town:
https://www.val.town/x/moe/MiniAppStarter

Most mini app webhookUrl endpoints will probably override KV data between clients (Warpcast, Coinbase Wallet) since that's how it's done in the mini app v2 demo's setUserNotificationDetails. But no prob if people stick to a single client

cc @horsefacts.eth @deodad 
https://github.com/farcasterxyz/frames-v2-demo/blob/main/src/app/api/webhook/route.ts#L50

Assuming a lot of mini app devs also have the notifications.url hardcoded since it used to be the same always, so probably most notifications won't work with Coinbase Wallet from the start (although it's correct in the mini app v2 demo)

I don't think saveUserNotificationsDetails is able to handle multiple clients at the same time, if fid uses multiple clients

I don't think saveUserNotificationsDetails is able to handle multiple clients at the same time, if fid uses multiple clients

https://warpcast.com/mvr/0x240d216e

hamst.art $hamster /hamster 
martinvr.eth 
deploy.degen.eth

yeah, could be a problem when the coinbase wallet integration goes public

but won't be if everyone sticks to a single client

yes you're correct, it doesn't handle multiple clients for the same user. i meant it handles multiple clients for multiple users by saving the notifications url for each user and the token. 
most other projects/templates just store the token and hardcode warpcast urls.