Content pfp
Content
@
0 reply
4 recasts
4 reactions

Varun Srinivasan pfp
Varun Srinivasan
@v
What's the most annoying thing about building frames today?
34 replies
3 recasts
38 reactions

Manan pfp
Manan
@manan
- Figuring out what url to POST to as a frame client is hard to get right. Lots of fallbacks! - The dance between JSON for tx call data and HTML for frames is not ideal.
1 reply
0 recast
3 reactions

Daniel - Bountycaster pfp
Daniel - Bountycaster
@pirosb3
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
0 reply
0 recast
2 reactions

jtgi pfp
jtgi
@jtgi
Most annoying? generating the images. Simple text is not so bad, but dynamic text, with emoji support, fonts, images is pretty clunky. Helps if you pay vercel but $$$. But images make it way more portable so it’s prob worth it.
0 reply
0 recast
1 reaction

Victor🎩🚴↑ pfp
Victor🎩🚴↑
@victoctero
Not finding the way to build a no-code raffle frame (maybe there is some workaround and I don’t know it)
0 reply
0 recast
0 reaction

Justin Hunter pfp
Justin Hunter
@polluterofminds
Images for interactivity is a super hacky experience. Sandboxed HTML would enable almost all the use cases people are hacking around today.
1 reply
3 recasts
31 reactions

Cameron Armstrong pfp
Cameron Armstrong
@cameron
- 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
0 reply
0 recast
12 reactions

Emmaniii pfp
Emmaniii
@emmaniii
We need transactions to work on test networks (i.e. sepolia) to make it easier to develop and test frames
1 reply
0 recast
12 reactions

Corbin Page pfp
Corbin Page
@corbin.eth
Frame caching can be tricky to deal with
0 reply
0 recast
10 reactions

Vladyslav Dalechyn pfp
Vladyslav Dalechyn
@dalechyn.eth
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!
1 reply
0 recast
7 reactions

Serg 🎩🔵⛓️✈️ pfp
Serg 🎩🔵⛓️✈️
@serg
Proper SVG support so we can do cool animations.
1 reply
0 recast
5 reactions

Matthew Fox 🌐 pfp
Matthew Fox 🌐
@matthewfox
not having a local testing playground if you don't use frog
4 replies
0 recast
5 reactions

veekay  pfp
veekay
@veekay
lack of debugging tools. lack of clear error messages leading to unable to find the bug let alone solve it
0 reply
0 recast
3 reactions

Manuel pfp
Manuel
@manuelmaccou.eth
Building the dynamic frames with node-canvas. Couldn’t get Satori to work for some reason
2 replies
0 recast
3 reactions

Coop pfp
Coop
@coopahtroopa.eth
Cc @ramie
0 reply
0 recast
2 reactions

Colin Johnson 💭 pfp
Colin Johnson 💭
@cojo.eth
- Wallet connection on mobile ( metamask sucks) - Text input issues (see below) https://warpcast.com/cojo.eth/0x4cc0e3af
1 reply
0 recast
2 reactions

Ramie رامي pfp
Ramie رامي
@ramie
Cacheing seems to be the one that gets me the most often. It can make it really difficult to figure out whether you've fixed a bug or not.
0 reply
0 recast
1 reaction

Ombre🎩💙 pfp
Ombre🎩💙
@0mbre
I wish buttons would show up even when user is not logged in FC. Beside that I kinda like constrained dev environment, so no big ask come to mind
0 reply
0 recast
1 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
For me, it's single POST target URL. State helps a lot there (I did not expect it!), but deciding what to do based on previous state (state + button) feels weird. It's as if I have a single URL and I decide what it does based on the referrer. (Maybe it's me)
3 replies
0 recast
1 reaction

grant 🌈 🎩 🐸 pfp
grant 🌈 🎩 🐸
@grunt.eth
transaction queuing for the end user
0 reply
0 recast
1 reaction