Here’s a shocking truth: your users don’t care about your tech stack. Not even a little. They’re not going to be awake at night wondering whether you choose React, Angular, Vue, or wrote it all in vanilla JavaScript or even jQuery like the so-called traditional approach. They don’t care if you used the “trending” framework or a tool you’ve been following since 2010. All they want is something that works, works well to solve their problem and doesn’t make them regret using the system you built.
Sure, as a developer, you might be one of the rare species who actually checks which technology a website is built on. Congratulations ! you’re probably in the 1% of users who even think about that. The other 99%? They don't care at all. When they book a flight online, do they pause midway and checkout to wonder if the airline’s site is developed with Java, Angular, Django, or written in assembly language ? Nope. When you use your banking app, do you care if it’s running in the cloud or on-premise ? Of course not. All you want is it to be fast, not lose your money, and not crash as you hit “Confirm.”
The problem is, just because developers are happy with their new tools doesn’t mean users are happy too. We get excited when our jobs become easier, and that’s okay. But our prime objective it to solve problems of end users not the problem of developers themselves. It doesn’t matter how modern or fancy the technology is, if the product is slow, full of bugs, or hard to use.
Am I trying to state that we should stop caring about our tools? Of course not. Good tools help us build better products faster. But we need to remember that frameworks are just our backstage crew. The user is watching the show, not peeking behind the curtains to admire the setup and preparations behind the stage.
So next time you feel like bragging about your tech stack, stop and ask yourself: does the end user really care about it ? Unfortunately for you, they don’t. They just want something that doesn’t break, lag, or make them want to throw their device out the window. If it works, they’ll love it. If it doesn’t, no amount of “Java this” or “Angular that” is going to save you from their frustration.