This really depends on the scope of the project or the philosophy of the project.
Personally I have pretty much sworn off webapps because of the amount of separate concerns:
* the web stack (html+css+ts)
* framework quirks
* dom vs vdom
* nodejs quirks
* hosting platform quirks (if you use serverless)
While some of these can be overcome, personally it was too damn much work.
Compared to say flutter it's dart + flutter quirks, I was surprised how fast I got a working prototype ready without having to dread the all extra crap.
And it seems it's mostly the bullshit Apple and Google does since both solutions have technical issues, all the web apps that only support Chrome for instance.
Personally I have pretty much sworn off webapps because of the amount of separate concerns:
* the web stack (html+css+ts)
* framework quirks
* dom vs vdom
* nodejs quirks
* hosting platform quirks (if you use serverless)
While some of these can be overcome, personally it was too damn much work.
Compared to say flutter it's dart + flutter quirks, I was surprised how fast I got a working prototype ready without having to dread the all extra crap.
And it seems it's mostly the bullshit Apple and Google does since both solutions have technical issues, all the web apps that only support Chrome for instance.