Paying for the compute time and licensing of the code are not going to be the problems that stop this it will be programming the AI and then debugging the output. Generating the correct prompt for an AI is going to be much, much harder than people think. Sure, it is easy to generate a picture in your head of what you want an app to do but, at least in my experience, often the most consuming part of programming is deciding _exactly_ what you want your code to do i.e. converting the vague floppy idea in your head into a concrete set of instructions where all ambiguity is removed and everything is decided.
Having an AI involved might mean that a developer may not need to know the programming details (although I suspect it will be needed since AI code is far from bugfree) but they will still need to describe the program with complete precision e.g. what input parameters are needed, what the controls for each should look like, where they should be placed etc. because if you do not then not only will the AI make a complete mess of an interface but, everytime you tweak the prompt to fix an issue, the interface will likely completely change unless clearly specified.
Now multiply that by all the small decisions that developers make when coding an app and, while AI may help reduce the burden I doubt it is going to massively reduce it plus you have to contend with the issue that unlike a traditional programming language, one slight change to the prompt can radically shift how the AI codes things meaning that a minor change in one area could radically change another area unless the prompt has everything tied down precisely. So I think that developers are absolutely going to be needed but, if this works well, it may make them more productive as well as change their skillset somewhat.