not having a local testing playground if you don't use frog
frames
Being not able to invalidate cache of a frame. Upgrading a frame therefore becomes problematic. A button in the validator would be enough for such!
frames
Building the dynamic frames with node-canvas. Couldn’t get Satori to work for some reason
frames
lack of debugging tools. lack of clear error messages leading to unable to find the bug let alone solve it
frames
We need transactions to work on test networks (i.e. sepolia) to make it easier to develop and test frames
framesImages for interactivity is a super hacky experience. Sandboxed HTML would enable almost all the use cases people are hacking around today.
frames
Not finding the way to build a no-code raffle frame (maybe there is some workaround and I don’t know it)
frames
- no always up to date before releases canonical page for every frame spec change - constant moving target for spec changes (#1 would help w this) - no testnet for txn - no mobile playground for testing UX flows when 80%+ warpcast users are mobile - frame dev support is doing their best, but there's too much to deal w
frames
1. Not having support for a testnet for txn frames 2. A call back endpoint for a normal frame would be really cool.
frames
Not annoying anymore since we build a framework to abstract this, but I think this change could be high ROI: Having button actions as enums instead of indices reduce the requirement for state tracking + reduce problems related to backwards compatibility
frames
not building, but using https://warpcast.com/kugusha.eth/0xbe09be38
framesthis frame working in validator (https://warpcast.com/~/developers/frames?url=https%3A%2F%2Fonlyframes.xyz%2F65f061db0aebdd84b4aadd1e) but not in the casts https://onlyframes.xyz/65f061db0aebdd84b4aadd1e
frames
frames are extremely ephemeral with no great discovery mechanism today a good way to bookmark/ browse recently used frames/ discover new ones would go a long way
frames
Back button handling, not as tricky, just extra work to handle, plus sometimes you're simply out of 4 buttons
frames
* lack of end-to-end examples using modern tooling * we are so early - so all the tools are new and have many bugs * dependency on external services such as syndicate and neynar for common functionality such as verification and fid to address * lack of standard error handling * tx domain verification seems broken
frames
that there is a lot of competition and you don‘t earn much for the work
frames