I love functional concepts such as stateless systems, but young folks should acknowledge that two way event binding is something graphical desktop toolkits are doing since decades. For instance, Qt signal-slot mechanism <a href="https://doc.qt.io/qt-5/signalsandslots.html" rel="nofollow">https://doc.qt.io/qt-5/signalsandslots.html</a> or <a href="https://libsigcplusplus.github.io/libsigcplusplus" rel="nofollow">https://libsigcplusplus.github.io/libsigcplusplus</a><p>Furthermore, MVC <i>is</i>, when done correctly, a sane two way data-GUI binding. However, I have never seen a sane implementation ;-)
Is anyone else sad that we have adopted HTML/CSS as the universal lingua franca for describing views?<p>I understand why (or at least I believe I do): HTML/CSS is an inevitable part of the ecosystem because the web is an important target. A lot of devs will know at least some, and your organisation may already have loads of them because you also need to target the web. Maybe you even already have some view code written for the web platform that you want to re-use. This means that HTML/CSS gives you a head-start due to existing skillsets. It's familiar for some people and they can get going.<p>The problem is that it's <i>bad</i>. I say this as someone who comes from the outside, and isn't an expert ("barely competent" in HTML/CSS is probably accurate). Basic layout of things in a way that copes with different screen sizes/orientations is a surprisingly black art sometimes. There's a lot of history confusing the issue and three ways of doing each thing.<p>Coming at it fresh, it's a lot to learn to build a desktop/mobile UI. Flutter (for example) has its issues, but getting things to lay out correctly did not take a lot of learning. Once you've got the basics (3 days to a week for me, including learning Dart) things behaved predictably - it seems to take a lot of HTML/CSS knowledge before that is the case.
It should be noted that this is a wrapper around React Native.[1] I am a bit in doubt if one can use Vue Native knowing only Vue and never having to learn any React.<p>[1]: <a href="https://github.com/GeekyAnts/vue-native-core" rel="nofollow">https://github.com/GeekyAnts/vue-native-core</a> says as much.
What are the trade offs/Adventages to use cross platform tools for app development in 2021?<p>The advantages of native iOS development, off top of my head:<p>1) Swift is very pleasant to use and it is fast.<p>2) The UI libraries that I need to learn: UIKit and SwiftUI. SwiftUI is also very pleasant to use and it is getting there.<p>3) No hoops to jump for integrating API that makes an App do things that WebApp cannot do.<p>4) Work environment setup is very easy, no scripts to run no tooling that breaks down. It's as simple as creating an new Word document and start doing actual work, not janitorial tasks.<p>5) Despite its bugs, Xcode is a good IDE that natively understand all the tooling I use. Autocomplete might break down sometimes but it can handle project creation, asset management, project configurations and the distribution.<p>6) The only vendor that I rely on is Apple, as soon as they make something interesting it is available to me. The latest API is there right away.<p>7) The apps look in place by default, you actually have to work to make UI unconventional and weird.<p>I would imagine that on the Android side of things are also not that different.<p>Edit: I see that you don't like the question being asked and other perspectives being presented but I think it's a fair question and I would like to know if I am missing out on something.
Looks like the project is seeing <i>very</i> little in terms of contributions of late: <a href="https://github.com/GeekyAnts/vue-native-core/graphs/contributors" rel="nofollow">https://github.com/GeekyAnts/vue-native-core/graphs/contribu...</a>
Just did a deep dive with a group of devs with vue native, nativescript, ionic and more for building a mobile app in vue.<p>We all enjoy building in vue and we're looking to extend that to mobile. However in almost all cases, there were shortcomings and a lack of maturity in support compared to react or angular. A lot of time wasted.<p>Generally, Vue is not a first class citizen in these environments. Yet.<p>Vue Native began with a lot of promise and excitement. Documentation is ultimately sparse and examples either don't exist or are out of date. Compiling the same code on Mac or windows yielded inconsistent build results. Debugging doesn't have much research that is possible. Sometimes you have to compile 4 or 5 times. Still seems early.. Or not developing as quickly as other options. Doesn't seem updated often.<p>Nativescript was next, looked very inviting and welcoming, but trying to reproduce the same resulted in a fair number of issues. It seems nativescript has less of a history with vue than react. Noted the documentation is deeper for other frameworks. Seems to be evolving for vue. Pass for now and check again in 6 to 12 months for progress.<p>Last, but not least, ionic. Right off the bat likely the deepest documentation. It had 2 approaches.. Package a vue.js app for mobile, or use capacitor to try and build more of a native experience. Capacitor is relatively new for vue.js and still maturing. Ran into similar issues as the others. Didn't seem ready for production than using angular or react with ionic or capacitor. Vue supports in ionic are thinner than angular for sure and seemingly react.<p>For now, it was possible to build a vue web app to do what's needed and add ionic to simply package it. No capacitor.<p>It pains a little to say this, but if we were building a more complex app, the react native tooling is what we'd have to consider. It's far more mature and nearly every problem we encountered had a result of how to resolve it in react native.
Flutter web is also becoming a viable option for web apps. I recently wrote a new app in Flutter and it works surprisingly well on the web, not just in native iOS and Android. It has some quirks though but I did not find anything serious.
I was using Cordova with VUE.js and had fantastic results in both iOs and Android, using "Buefy" as my UI framework.<p>I started with Nativescript and ended up in building a WebView which I then simply included.<p>I haven't tested Vue Native yet but wanted to know why Cordova seems to be on the decrease :( I feel like I have to develop in Vue Native or Nativescript soon to not lose track. However, I always liked the Cordova/Vue combination and I could realise fantastic apps with it.
I’ve been putting off switching my native apps to cross-platform simply because I’m too busy to learn react, so it’s great to see that vue is finally an option.<p>Of course it’s probably a little too soon to completely switch live apps to this, at least until it stabilizes a little bit.<p>Edit: never realized this existed for the past two years and is simply a wrapper for react native.. any reason it’s being posted now?
is there any project that would us the same js - native bridge as react native, except with wasm.<p>The idea would be to let us write cross-platform business level code in any language targeting wasm, while using a native UI framework
Two way data binding tends to obscure the rendering process and add a lot of "black box" side effects, which in browser based applications leads to serious performance issues that bog things down at scale. I would like to know how they're going to avoid this.
While this is nice, for mobile -- and even desktop -- apps I find hybrid/electron to be a far more compelling use case. On mobile, if you're stuck in a situation where you need the full power and speed of vendor native then, if you're using Ionic Capacitor, you can spin up an Activity/UIView and code that part in Java or Kotlin for Android and Swift or Obj-C for iOS (or C++ for both if you really want to). Do everything in HTML,CSS,JS that you can and only use the heavy duty tools where absolutely necessary... and the truth is, they <i>aren't</i> nearly as necessary as they used to be.
To be honest, I don't see any reason not to use Flutter if you want to make a cross-platform app these days. Any other cross-platform framework I tried seemed somehow lacking, slow, unpleasant to use etc.
I use to frown upon cross-platform js solutions until I built a cross platform app. While the initial app building part was no problem, packaging them for various platforms (macos, windows) was pure h*l.
I would honestly throw entire salary on this if its built in the direction it claims. Only downside for Vue Developers would be to switch between frameworks(React Native) to develop a native app.
Archive updated today:
<a href="http://web.archive.org/web/20210127141756/https://vue-native.io/" rel="nofollow">http://web.archive.org/web/20210127141756/https://vue-native...</a>
(If you also get error visiting the page now)
Yeah I dunno, react native is a neat idea, in practice it was all pain all the time. Updating, debugging, building, ensuring it worked on all devices, then add in something like Bluetooth LE and the pain grew even more.<p>Would have been easier to create two apps in their native platforms.
Lots of comments on HTML/CSS being hard or non optimal but learning to use things like grid (grid template areas plus designing first for mobile) and flex together really allow all sorts of layouts one would create.
Maybe I just wasnt giving it my full devotion but I spent a day or two just trying to get Vue Native up and running late last year and no success. Maybe if I had more Reactive Native knowledge it would have been easier.
whats the down side of plopping your vue app into a webview then making interfaces to call kotlin code from vuejs?<p>thats what I've been doing to rapids app prototyping...
I see:<p>- "react": "^15.5.4",<p>- "react-dom": "^15.5.4"<p>as npm dependencies.<p>Dumb question - why does it need react as dependencies?