As a developer I went onto this page expecting to see some UI that it's created... That's usually my first port of call with any of this stuff, does it pump out something that's actually useful.
I might not be your target demo, but feedback's feedback!
There was 3 seconds where I was thinking "ah thats an interesting problem, wonder how theyre trying to solve it". Shouldve guessed it would be a gpt frontend.
Everything now is shadcn anyway; just build nice ux with shadcn and give that to the designer to make some meaningful changes. It is faster and anything else will end up there anyway because the stakeholders are used to that style and will say 'little more this, little more that' for months until you arrive there anyway. Might as well start there and save yourself the lost months of life.
I like that the theme is added to the context up front!
How does the tool handle modifying existing components once requirements eventually change? I find the pain of implementing UIs isn’t the initial implementation, it’s that product/design loves tweaking requirements in a very complex way.
The benefit of component libraries is the extensibility, IMO. I’m not sure why I would use this over an existing library without a demo
All of these sites look just the same. From the time the good designers have been pushed out of the industry by flat designers, we have had just horribly ugly UIs and even worse UX in the industry.
I love the idea of this sort of thing, but FWIW I personally don't think the lean "make a landing page to gauge interest in a product before we make it" is that effective these days, sorry.
Flagged because this is just a signup page. It cannot be tried. A requirement for Show HN: https://news.ycombinator.com/showhn.html
As a developer I went onto this page expecting to see some UI that it's created... That's usually my first port of call with any of this stuff, does it pump out something that's actually useful.
I might not be your target demo, but feedback's feedback!
Isn't the site itself that UI that it's created??
Dunno. It's not totally obvious to me, so I suspect others will struggle too.
There was 3 seconds where I was thinking "ah thats an interesting problem, wonder how theyre trying to solve it". Shouldve guessed it would be a gpt frontend.
Everything now is shadcn anyway; just build nice ux with shadcn and give that to the designer to make some meaningful changes. It is faster and anything else will end up there anyway because the stakeholders are used to that style and will say 'little more this, little more that' for months until you arrive there anyway. Might as well start there and save yourself the lost months of life.
I like that the theme is added to the context up front!
How does the tool handle modifying existing components once requirements eventually change? I find the pain of implementing UIs isn’t the initial implementation, it’s that product/design loves tweaking requirements in a very complex way.
The benefit of component libraries is the extensibility, IMO. I’m not sure why I would use this over an existing library without a demo
Copying from the link:
>webapps
>context-aware components
>copy production-ready code or deploy it from here.
so folks who don't want to use Electron or HTML should look elsewhere.
Will this tool be open source?
All of these sites look just the same. From the time the good designers have been pushed out of the industry by flat designers, we have had just horribly ugly UIs and even worse UX in the industry.
I love the idea of this sort of thing, but FWIW I personally don't think the lean "make a landing page to gauge interest in a product before we make it" is that effective these days, sorry.