I'm mainly a backend developer, but my role now includes frontend work too. What should I focus on to improve both the code and the look and functionality of the UI?
How can I get better at frontend work as a backend developer?
Answers
Separate design from implementation when you're deciding what to learn. Design covers things like visual hierarchy and whether a flow makes sense. Frontend development turns that into a working interface, including all the interactive states.
For implementation, get comfortable with the CSS box model, JavaScript and the event loop, then learn the UI framework your team uses. A basic usability course is worth doing alongside that. You don't need to become a designer overnight, but you do need to spot when a screen is confusing.
Reply to this answer
Pick a component library that fits your stack and use it consistently for a while. You can spend a surprising amount of time hand rolling buttons and forms that still don't quite match each other.
For the visual side, study a few product screens you like. Look at their spacing, font sizes, color roles and empty states, then apply those patterns rather than copying their code. Set a small spacing scale and type scale in CSS variables so every new screen isn't starting from scratch.
Reply to this answer
Start with one complete flow, not a big redesign. Make sure it has sensible loading, empty and error states, not just the happy path. Those missing states can make an otherwise nice screen feel unfinished fast.
Check that the flow works with a keyboard and that controls are usable and understandable for people with disabilities. Accessibility isn't just polish. There can be legal requirements depending on where the product is used.
Nexlora-7h:
Improving a small flow end to end also makes the work easier to review than changing the whole UI at once.
Reply to this answer
If you're using AI to generate UI, give it a direction before asking for a whole page. A short brief can specify the audience, a visual reference, colors, type, spacing and component patterns. Otherwise each screen may end up making its own design decisions.
Build and tune one representative page first, then use those choices as the basis for the rest. Review the generated code and behavior rather than assuming a good-looking screen is finished.
Reply to this answer
Add your answer
Answers are reviewed before publication.
n.573+foldladle:
A rough visual reference or wireframe can help too. It gives you something concrete to compare the finished screen against.