No, it's very much a technology issue. The overhead just for shipping an entire webbrowser with your app is insane. Building a decent UI in HTML/CSS which were never designed for that purpose, is an absolute disaster. HTML and CSS are for formatting text documents, not for designing user interfaces. There is a reason that there is a framework-of-the-week for webapps.
So now you have this massive webbrowser footprint, with the framework-of-the-week on top and then you have to write your app on top of this abomination in one of the most terrible languages ever invented.
The whole 'webapp' thing exists solely on the false promise of cost savings. Every kid who made a webpage for their aunt's Etsy business calls themselves a 'web designer', which has resulted in a race to the bottom. Web designer are a dime a dozen (sure, a good one may cost a pretty penny, but that's not what management sees). Now you can hire that cheap 'web designer' and they can build apps too, since that's just web tech, right? And since it all works cross-platform, you only need to build it once. What a cost savings!
They will even get an initial version out the door quickly. Look, everything worked out as expected. The problem is that it's quicksand. Your app grows and it gets harder and harder to fix issues and add features, as it's all build on shaky foundations. The more you move, the more difficult it becomes. Soon, you find yourself writing platform-specific code as the cross-platform promise doesn't hold for anything but the simplest functionality. Before you know it, you have this bloated, unmaintainable mess.
At the end of the day, it's easier and cheaper to just develop 2 native apps for iOS/Android than it is to build a 'webapp'. You can use nice, modern programming languages with very few footguns (Swift/Kotlin), good tooling, a UI toolkit designed to actually build UIs with, a set of well designed platform APIs. The whole cross-platform web-app thing sounds nice in theory, but it never delivers on its promises.