Valdi – A cross-platform UI framework that delivers native performance

Post by adastra22 » Sun, Nov 09, 2025, 1:48 AM UTC

boguscoder wrote: post #190

adastra22 wrote: post #177

Earlier quoted context omitted.

You are comparing web view apps to web view apps. “React Native” has muddied the waters here with intentional misuse of terminology. With React Native you still write a web view app - it just ahead of time compiles to run without the browser view on device. But it doesn’t use any native UI components, which is what “native app” used to mean.

I may have read your comment backwards but it seems rather wrong: react native DOES use native UI components, thats why it has “native” in its name. It’s also not compiled ahead of time per se, you still execute JS in the app (not in webview, yes) , but its mapped to native components

Post by e12e » Sun, Nov 09, 2025, 2:03 AM UTC

DecoPerson wrote: post #26

bearjaws wrote: post #23

Working at a company that uses react-native I wish nothing more than for the end of app stores and differing platform languages. We're heavily considering just having a website next year with a mobile app using webview, and then native code for the native notifications, GPS and healthkit / health connect. I feel like AI is changing the equation, its nearly better to write your business UI 3 times one for each platfor…

I did this and never looked back. It’s called a “WebView app” and you can get a really good experience on all platforms using them. Just: - don’t make any crazy decisions on your fundamental UI components, like breadcrumbs, select dropdowns, etc - add a few platform-specific specialisations to those same components, to make them feel a bit more familiar, such as button styling, or using a self-simplifying back-stack…

Post by yawnr » Sun, Nov 09, 2025, 2:58 AM UTC

adastra22 wrote: post #191

boguscoder wrote: post #190

Earlier quoted context omitted.

I may have read your comment backwards but it seems rather wrong: react native DOES use native UI components, thats why it has “native” in its name. It’s also not compiled ahead of time per se, you still execute JS in the app (not in webview, yes) , but its mapped to native components

Thank you, it appears I was misinformed and/or conflating my knowledge of how flutter works. Mae culpa. It does seem that many RN apps do React (not native) components when they need to do something custom, which may explain my sub-par, non-native experience with the RN apps I have used.

Post by DecoPerson » Sun, Nov 09, 2025, 3:29 AM UTC

sebmellen wrote: post #196

littlecranky67 wrote: post #51

Earlier quoted context omitted.

There is no reason you can't do that via web. Image capture in a canvas gives you access to the raw image pixmap data.

Trust me, native camera access is extremely important if you need to directly control focus (for example). We have web and mobile apps that scan ID images and our ability to capture high quality images on mobile native devices is 5x better. AVFoundation on iOS especially.

Post by DecoPerson » Sun, Nov 09, 2025, 3:36 AM UTC

tiborsaas wrote: post #109

DecoPerson wrote: post #26

Earlier quoted context omitted.

I did this and never looked back. It’s called a “WebView app” and you can get a really good experience on all platforms using them. Just: - don’t make any crazy decisions on your fundamental UI components, like breadcrumbs, select dropdowns, etc - add a few platform-specific specialisations to those same components, to make them feel a bit more familiar, such as button styling, or using a self-simplifying back-stack…

Isn't there a high chance your app is going to be rejected from app stores because you use a web view? You can change your whole app completely upon approval. Or you ship your HTML/JS and not just embed a URL?