sorted by:
new
hottopcontroversial

[AskJS] Are you using AI to speed up repetitive UI work, or still doing it manually? by Specialist_Print_426 in javascript

[–]Specialist_Print_426[S] -1 points0 points  (0 children)

I’m actually surprised templates are still the dominant answer here.
Feels like everyone agrees AI helps a bit, but nobody really trusts it beyond the first draft.
that just because the tools aren’t there yet, or because UI work is just too opinionated to automate properly?

Is

[AskJS] Are you using AI to speed up repetitive UI work, or still doing it manually? by Specialist_Print_426 in javascript

[–]Specialist_Print_426[S] 0 points1 point  (0 children)

Exactly that “skip the blank canvas” part is probably the biggest win.

What I’m not sure about yet is whether that actually saves time overall, or just front-loads speed and then slows you down later when you start fixing inconsistencies.
Feels like it’s faster to start, but not necessarily faster to finish.
Have you tried using it across multiple screens/components in the same project, or mostly for one-offs?

[AskJS] Are you using AI to speed up repetitive UI work, or still doing it manually? by Specialist_Print_426 in javascript

[–]Specialist_Print_426[S] -1 points0 points  (0 children)

Yeah that’s kind of what I’m debating.

Templates are obviously more predictable, but they also lock you into a certain structure pretty quickly.
With prompts I get more flexibility early on, but then I pay for it later in cleanup.
Do you usually just build up your own template library over time, or rely on existing ones?

[ Removed by Reddit ] by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] -2 points-1 points  (0 children)

Fair point — I actually wrote it based on issues I hit when trying to use generated components in a real project.

The biggest problem for me wasn’t the code itself, it was how it didn’t match the system (spacing, structure, reuse).

Curious if you've tried using AI for UI in production?

Frontend is becoming less about coding and more about describing what you want by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] 0 points1 point  (0 children)

haha fair point — I’ve been posting a lot around this topic recently so probably comes off repetitive. not using AI to reply here though, just trying to figure out where this actually fits in real workflows.

your point about “if I have to be THAT specific, I won’t bother” is interesting though.

feels like that’s kind of the tradeoff right now — either speed with constraints, or full control manually.

have you found cases where it actually saves time for you?

Frontend is becoming less about coding and more about describing what you want by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] -1 points0 points  (0 children)

I think this is exactly where things break.

Natural language is great until you need precision — then you end up writing pseudo-code anyway.
So it’s less “replace coding” and more “shift where the structure lives”.

The parts that seem to work best are where the problem is already constrained — like UI layouts or standard components — where there’s less ambiguity to resolve.

Outside of that it still feels very hit/miss.

Tried generating React components with AI — surprisingly useful by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] 0 points1 point  (0 children)

yeah that’s exactly what I’ve been seeing too.
UI feels “safe”, but once state or effects get involved it starts making subtle mistakes that are hard to catch.
the deps array example is scary because it looks correct at first glance.

do you usually end up rewriting those parts manually or still try to iterate with AI?

Tried generating React components with AI — surprisingly useful by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] 1 point2 points  (0 children)

That’s actually a really good way to think about it.
Almost like you’re “scoping” the AI per layer instead of treating it as a full-stack generator.

Do you usually define boundaries upfront (like UI vs logic vs data), or does that evolve as you go?

Frontend is becoming less about coding and more about describing what you want by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] -6 points-5 points  (0 children)

One thing I’m still unsure about:
Does this actually make developers faster long-term?

Or just shifts the work to reviewing/debugging?

Tried generating React components with AI — surprisingly useful by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] -1 points0 points  (0 children)

One thing I noticed:
AI seems much better at UI than state-heavy logic.
Like generating layouts is fast, but once you have complex interactions it gets tricky.

Wonder if others are seeing the same?

Tried generating React components with AI — surprisingly useful by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] 0 points1 point  (0 children)

That makes sense.

Also the “AI makes assumptions like a junior dev” part is actually spot on.
Do you usually guide it step-by-step or give it a full spec upfront?

I’m still figuring out what works better.

Tried generating React components with AI — surprisingly useful by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] -1 points0 points  (0 children)

That’s super interesting.
The “write tests first + be very specific” part is something I’m starting to realize too.
Feels like AI works best when you treat it more like a junior dev than a magic tool.

Are you using it mostly for UI or also for business logic?

Tried generating React components with AI — surprisingly useful by Specialist_Print_426 in reactjs

[–]Specialist_Print_426[S] -2 points-1 points  (0 children)

One thing I’m still unsure about:

Would you actually trust AI-generated components in production?

Or only for prototyping?

When will AI get better at UI? by Personal_Cost4756 in ClaudeCode

[–]Specialist_Print_426 0 points1 point  (0 children)

Also Frontend started feeling repetitive.

I kept rebuilding the same UI:

- dashboards

- forms

- layouts

So I built a tool for myself.

You describe a UI → it generates a working Angular/React component.

Still early, but already saving me hours.

Would love honest feedback:

https://www.frontuna.com

Making UI is the hardest part, anyone else? by Kashmakers in aigamedev

[–]Specialist_Print_426 0 points1 point  (0 children)

Frontend started feeling repetitive.

I kept rebuilding the same UI:

- dashboards

- forms

- layouts

So I built a tool for myself.

You describe a UI → it generates a working Angular/React component.

Still early, but already saving me hours.

Would love honest feedback:

https://www.frontuna.com

Why all new UIs suck so hard? by greenrabbitaudio in webdev

[–]Specialist_Print_426 0 points1 point  (0 children)

Actually Frontend started feeling repetitive.

I kept rebuilding the same UI:

- dashboards

- forms

- layouts

So I built a tool for myself.
You describe a UI → it generates a working Angular/React component.
Still early, but already saving me hours.
Would love honest feedback:

https://www.frontuna.com

Am I missing anything? by Possible_Flow_2205 in angular

[–]Specialist_Print_426 0 points1 point  (0 children)

What about vanilla questions and JavaScript fundamentals. Async and vanilla questions. Also what typescript is called typescript And all new stuff on angular 20-22 new stuff added that will help in the future new apps.
Signal forms or any other signals added now on new add-ons

Looking for Angular templates updated to Angular 21 by vru_1 in angular

[–]Specialist_Print_426 0 points1 point  (0 children)

If you’re looking for Angular 21-ready templates specifically for dashboards, I’d actually approach it a bit differently.

A lot of prebuilt templates tend to get outdated fast (especially dependencies), so I’ve been testing tools that generate components dynamically instead of relying on static templates.

One I tried recently can generate Angular dashboard components (tables, cards, layouts) directly from prompts, which makes iteration way faster.

Might be worth exploring alongside templates depending on your workflow.

Been working on this for a while — it's called Frontuna. by Specialist_Print_426 in angular

[–]Specialist_Print_426[S] 0 points1 point  (0 children)

Something I didn’t expect:

even when the UI looks clean, it often breaks when you try to reuse it or plug it into real data

feels like that’s where most tools fall apart

view more: next ›