Marc van Neerven

You should absolutely launch your MVP asap, but just don't forget that it should align with what you have defined as the sweet spot of what your early adopters see as their problem to be solved. This is what I call the Minimum Lovable Product. Following the Lean Canvas methodology, will make this first step much easier.

Before even going into frameworks, it's crucial that developers get acquainted with the web itself. Although this sounds like a no-brainer, it is actually quite shocking to see that the vast majority of web developers have very limited knowledge about HTML, CSS, Browser APIs, JavaScript and all the other web standards. The recent 'State of HTML 2023' survey shows that a vast majority of web developers knows less than half of what the web can do (even the so-called senior ones). This has to do with jumping into frameworks too soon in their journeys, and then being biased into 'staying within the framework' for every small piece of functionality, installing yet another framework add-on NPM package...

It's important to distinguish between UI components (the lego-style reusable blocks that make up a UI) and the application itself. While many developers just put their fate in the hands of a framework to handle everything, the best seniors think about the componentization layer and application and state layers separately. Knowing that you can create a set of completely independent UI elements, even without using any framework (by leveraging the Web Components standard), then use these components over and over again in your projects or products (or leverage an existing WC component lib like Material Web), speeds up development and makes it sustainable. Some people even realize they don't need a framework anymore for everything.

Less is more! Don't overdo it, as we're expressing functionality, trying to convey meaning, and giving gratification with microanimations. Subtleness expresses class and quality. Overdoing makes it cheap and is shooting yourself in the foot.

Focus on learning web fundamentals first! Recently, the "State of HTML 2023" survey has shown that basic understanding of web standards is at a record low. Many 'seniors' rely on a framework (or a framework-specific package) to get things done, and don't even bother to find out a direct/native way. But investing in frameworks adds risks: 1) you don't learn the underlying web standards 2) framework life cycles are always shorter than those of web standards, which are also downward compatible, where a framework upgrade might break your code 3) if you switch frameworks, you have to basically rewrite everything The modern web is extremely powerful, and most apps and websites will be less complex, and run faster without frameworks.

Remember that, as a web developer, you're probably in the top 5% when it comes to CPU power and internet bandwidth. Imagine what it is to visit the same site or use the same app, but with a low end device, on a bad connection. Read "The Performance Inequality Gap" by Alex Russel.