But for quick info displaying apps, I find it very useful.
I am currently using Kivy (a Python UI library) on Raspberry Pi for several embedded projects. If I needed a mobile app related to those devices, I would seriously consider using Buildozer to package up a version of the embedded app, since the UI code would probably not change much.
But if the opportunity presented itself, it might be fun, given the right leadership.
I helped out on a mobile app a few years back, but I can't remember the platform. The decision was made to go with Windows Phone because we were a windows shop, but I can't remember if it was some native stuff.
Anyway, I was just helping here & there, so never got truly into it. I do remember the markup being very clumsy and hard for me to get used to. But, that could've been just inexperience too.
Am just about to do this for a client. They asked for a webpage (actually a page within a Wordpress site) which I delivered; THEN they asked for it to run as a standalone app on "all" mobile devices. Adding the extras to make it into a progressive web app seems the simplest solution with no rewriting of existing code required.
If it goes well I might write it up as an article here...
I started testing with UWP because some of its features suited for the desktop and I found that the same code and design with little adaptation code also worked in the now discontinued Microsoft Phone.
And I've been lucky, because thanks to the UNO Platform, now I can share the same UWP code and design for several Mobile and Desktop platforms including WebAssembly.
I've written exactly three apps, the last in 2015. Not really a part of our business plan. Since I usually code in C++ Java was simple enough and Studio replaced Eclipse while I was writing the first one. Our usual software has to run inside AutoCAD so phones are a foreign land that I have only visited.
I have been using Flutter for a few of my apps and it provides a great experience. Dart turned out to be a great language, and for those who have Java or C# experience, language has similar constructs.
Flutter itself is a good tool and similar to React Native, but with Dart as the programming language.
Not sure about others, but I like the way views and business logic are made available in one place, unlike with native tools where an XML file is to be used with a back-end programming language. Overall, I would give it a good rating and a recommendation to be at least considered for a development trial.
As for the survey: I would develop with any tool and every tool as long as it does not use a WebView to render my apps, the app should be native.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
With a web app, you can support not only mobile, but any device. I would use a local db for local state and MongoDb on the server (it's works great as long as you know what you are doing...including security).
I have written mobile apps before...after doing so, I got rid of my cell phone.
I had, at one time, interviewed for a position developing X-Ray Proof and Laser Proof nose cones for ICBM's . I was willing to do that as I expected they'd not be used (unlike, say, a Bouncing Betty, which would be used to kill and maim).
Making an application for a Mobile device? There are limits as to how far I could stretch my moral core and contribute to the demise of the species.