Hey guys, I’ve been a programmer for quite some time (not web-related) and I was wondering, could anyone share what are the hardest technical parts of being a web designer?
like what are the most frustrating parts in the web design’s flow?
(not related to clients/people/money),
thank you!
Given the virtually infinite combinations of screen sizes, devices, browser types and versions, and operating systems, it’s impossible to cover every combination.
It can be frustrating to invest time in making your design look fantastic on your workstation, only to discover it doesn’t translate that well to a different screen size.
Moreover, when you check on your phone, you might find it looks completely different, no matter how carefully you were.
And then, keep in mind that even between iPhone and Android devices, users might experience different visual results.
1 Like
To me the frustrating to manage all moving parts that should work together. Especially if you are full stack. Just HTML, CSS and Javascript is a challenge of its own.
1 Like
And at last you have the security aspects: SAST, DAST, CORS, XSS etc etc
1 Like
this is an interesting point! thank you
The hardest parts are making designs fully responsive, ensuring cross-browser consistency, and keeping performance optimized without sacrificing visual quality. It’s a constant balancing act.
1 Like
these are great points, thank you
I’m just glad I could help.
Hi everyone,
I’m curious to hear from web designers and developers about the biggest technical challenges you encounter when designing and building websites. Whether it’s front-end issues, back-end complexities, or optimizing for performance and accessibility—what hurdles do you regularly face?
Some challenges I’ve come across include:
- Ensuring cross-browser compatibility
- Responsive design across a wide range of devices
- Optimizing site speed without compromising functionality
- Managing complex JavaScript frameworks and dependencies
- Implementing SEO-friendly structures and markup
- Balancing security with user experience
What about you? Are there any particular tools, workflows, or solutions you rely on to overcome these obstacles? Let’s share insights and tips to help each other improve.
1 Like
The above post from a new topic was merged with this topic as they appear similar in theme.
I did choose an odd path. Using pure Go as foundation, I almost always get score 100. By not using a framework, I also save some extra code detours. And gets cheaper and hence greener hosting (small footprint saves environment and money).
Frameworks gives a shortcut to the market. I admit. But using a framework for decades, I realized that it also created in my case a maintenance hell when a new version arrived.
I found that the shortcut to the market has a price tag in my case was more expensive in the long term. As it creates a maintenance and dependency hell that comes some years after. Find and create workarounds for all “new features” in a new version of the framework.
So my challenge was to find a way to reduce maintenance time and cost created by magic that I do not understand. And I was willing to pay for the extra time to market…
1 Like