Earlier quoted context omitted.
Last time I used Qt Quick, native looking widgets were outside of its scope. You're meant to define the styling you want for all of your widgets, and Qt will render them consistently across platforms.
Out of scope for Qt Quick, perfectly in scope for Qt Quick controls. It looks very native on all the platforms I’ve tried, likely due to their experience with Qt Widgets.
Twitter.com's HTML, which is produced by React Native for Web, explained
161–163 of 163 posts
Re: Twitter.com's HTML, which is produced by React Native for Web, explained
#162So why isn't React Native for web, just, you know, React? What's the difference and why?
React-native-web is more or less a component library that re-creates react-native's API. Some will disagree, but react-native's API is much nicer and cleaner than HTML and CSS. It's like they took the best parts of HTML and CSS and left out the 30 years of cruft. The idea is that since react and react-native API's differ so much, it's not really feasible to have one code base cover native and the web. React-native an…
If you’re not making an app would you still use react native web over old stool react for the reasons above?
Re: Twitter.com's HTML, which is produced by React Native for Web, explained
#163Earlier quoted context omitted.
Judging from KDE's Kirigami apps and Subsurface on Android, I would not describe Qt Quick apps as native-performing or feeling.
Because you’re judging one that don’t try. There are demos of Qt Quick apps emulating Android very closely.