Content
@
0 reply
0 recast
0 reaction
Hoot đ©
@owl
I think Iâm getting tired of frontend development? Youâre always building the same stuff, the same components, just with different style and slightly different functionality which makes it just not compatible with code you wrote previously. If you could reuse, the setup is too much work so you just build everything from scratch again. Maybe itâs time to protocollize all of this and just say hereâs web3s Bootstrap.js follow it for easy dapps and then gradually make it more extendable as it grows? Thereâs definitely a market for this, also with AI driven development becoming more common.
2 replies
0 recast
7 reactions
Stephan
@stephancill
i'm trying to build something along these lines and i don't think you need a protocol necessarily it's just a transaction editor for now but if you add the right building blocks it can be a frontend for any onchain app. frontends could probably be generated for arbitrary contracts using AI https://warpcast.com/stephancill/0xaa7a379a
3 replies
0 recast
1 reaction
Darryl Yeo đ ïž
@darrylyeo
Also been doing this with @blockhead to an extent â building a super-frontend within a single codebase to avoid the pitfalls that come with forking + modifying, while incubating my own custom components + opinionated design system in parallel.
1 reply
0 recast
1 reaction
Hoot đ©
@owl
Component systems have always been awkward, theyâre configurable to an extent but when you want to change them fundamentally you have to figure out their whole code base and rip out only the necessary parts, trying to stitch it together somehow. The shadcn model works quite well, you just copy & paste the component t and can use it as is or just change whatever you want. Works well with a common platform, tailwind in this case. Could translate to dapp component as well with viem & wagmi as the platform
0 reply
0 recast
1 reaction
