So if you are able to properly evaluate the outcome, it is probably fine.
It will also depend on the type of frontend and its target complexity. From what I understand from your question, you would handle the backend and infrastructure so these do need higher rigour.
If you apply the principle of separation of concerns, the frontend shall be decoupled from the rest and may evolve on its own end. That means that you have some degree of freedom to test and fail the frontend without harming the rest of your project.
Your end users may not like it much, but from a dev perspective, there is no "flaw".
Also consider that LLM training dataset and available data is huge about frontends, so it is way better at doing these.
We're at the dawn of a new era at the moment and it's only going to get crazier. Existing professional developers with deep understanding of code will do really well if they embrace it. People with understanding of cloud infrastructure will be similar. And subject matter experts with an idea can create something really awesome - although these people the most will need help to ensure potential products are production ready. SME's who rush products without proper understanding of security are the most dangerous in my opinion.
ventana•29m ago
Inside, there will be dragons: you will probably learn that all your CSS and JS are inline in your HTML, and that each page has its own implementation of the header and the footer, and other things like that, but if you don't plan to support it as a real product, you probably won't care.
simon84•24m ago
But I totally agree on the fact that it will probably look like just any other frontend.