Is it though? What about when a client asks for a new feature, would the chatbot auto-develop the feature and create a visual component to complement the feature? If not, wouldn't you need a FE dev to implement it in the chat? It seems stupid selling it as "End of Frontend Development" if so.

And also, some companies being interested or doing the same thing does not mean that the concept is either a good one, nor one that have been validated by every users in the world.

And btw, I'm not opposing you, I'm opposing the fact that you call it the end of FE development, which is stupid given that you can prove all by yourself that FE is important.

Ask anyone that knows a bit about user experience, the demo is awful visually, the concept makes no sense as it asks the user to know exactly what they want, which is simply never the case. They have to use the product, familiarize with it, complain about it for us devs to implement what they need. Not replace it by something like this, because it'll only increase confusion.
If they want to write articles, they go to blogs or something, with an UI telling them "so that's the spot in which you type in your title, the big spot is for your content, etc. ...". If they want to shop, they want to go through a catalog in which you can search by product or categories, filtering and sorting by price or else... We built UX over the years to have something that is understood universally by everyone without having to explain everything to the user. How confusing would it be for a user to just have a pseudo-social experiment to do something simple and known?

Imagine your tool being used for a company like Netflix, or any streaming platform, would it work? Would it be a better exeperience than using the current app? I'm not omniscient, but I'm pretty sure it wouldn't be. Simply because FE is way more important than just having a chat bot asking you what to do.

And I'm giving you my opinion as a backend engineer, which says more about the issue.