Content
@
0 reply
0 recast
0 reaction
jacopo
@jacopo
what's the point of the 5s timeout in frames? @v @horsefacts.eth
1 reply
2 recasts
13 reactions
limone.eth 🍋
@limone.eth
in my opinion is a constraint that forces devs simplifying their product and ux, in the end producing more effective frames
1 reply
0 recast
0 reaction
jacopo
@jacopo
5s is a very short timeout. in most cases - it forces devs to add complexity to their product, not reduce it - ux often is degraded (more clicks, total load time) rather than improved in any case this should be the app's concern and not the client's
2 replies
0 recast
0 reaction
alec
@alecpap
i like the timeout. it adds some upfront complexity of building out a queue system (eg waiting for a txn to get included in a block). you can build that once though, and reuse it in all your frame apps. staring at a frame and waiting, with nothing to do, stinks. adding a step into your frame where the user has a button they can tap to see if its done is a better option in my opinion. you can have fun and show different loading animations, render gifs on demand, etc reminds me of the buttons on traffic signal posts at intersectio s that dont actually do anything, but theyre there so people can push a button while waiting for the walk sign to light up
1 reply
0 recast
0 reaction
limone.eth 🍋
@limone.eth
yeah right, it’s something that warpcast does but then other clients can behave differently
0 reply
0 recast
0 reaction
