Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue Native (2018)

vue-native.io

Post reply on HN
Print view View original

41–50 of 190 posts

Re: Vue Native (2018)

#41

Post by dvfjsdhgfv »

u678u wrote: post #23
ktpsns wrote: post #5

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 https://doc.qt.io/qt-5/signalsandslots.html or https://libsigcplusplus.github.io/libsigcplusplus Furthermore, MVC is , when done correctly, a sane two way data-GUI binding. However, I have never seen…

Hopefully one day we can get to where Visual Basic was in the 90's.

I regret Delphi is a niche product now as it's quite powerful now, with native apps also for mobile platforms. Pity that the Community Edition doesn't support Linux.

Re: Vue Native (2018)

#42

Post by danpalmer »

u678u wrote: post #23
ktpsns wrote: post #5

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 https://doc.qt.io/qt-5/signalsandslots.html or https://libsigcplusplus.github.io/libsigcplusplus Furthermore, MVC is , when done correctly, a sane two way data-GUI binding. However, I have never seen…

Hopefully one day we can get to where Visual Basic was in the 90's.

"Low code" on trend, many devs using Visual Studio (Code), we're nearly there.

Re: Vue Native (2018)

#43

Post by breakfastduck »

mrtksn wrote: post #30
oakesm9 wrote: post #25

Earlier quoted context omitted.

The advantage is that you can access ~100% of the mobile market with a single codebase for about 10% extra work compared to native on a single platform. Performance is roughly the same and you have access to most of the platform features that most apps need.

That's the obvious value proposition but There's a reason why sporks did not make spoons and forks obsolete. I messed around with a few cross platform tools a bit and my impression is that if you want to make something that is better than a WebApp you actually have to learn a lot more tools and frameworks and everything feels like falling apart and you are depended on multiple vendors to upkeep the tooling. The momen…

I like that analogy!

Re: Vue Native (2018)

#44

Post by newsbinator »

mrtksn wrote: post #22

What are the trade offs/Adventages to use cross platform tools for app development in 2021? The advantages of native iOS development, off top of my head: 1) Swift is very pleasant to use and it is fast. 2) The UI libraries that I need to learn: UIKit and SwiftUI. SwiftUI is also very pleasant to use and it is getting there. 3) No hoops to jump for integrating API that makes an App do things that WebApp cannot do. 4)…

I like not having to learn Swift or dust off my 15-years-ago Java.

I can build stuff the same way on a Thursday for mobile that I do on a Tuesday for web.

Re: Vue Native (2018)

#45

Post by sbarre »

mrtksn wrote: post #22

What are the trade offs/Adventages to use cross platform tools for app development in 2021? The advantages of native iOS development, off top of my head: 1) Swift is very pleasant to use and it is fast. 2) The UI libraries that I need to learn: UIKit and SwiftUI. SwiftUI is also very pleasant to use and it is getting there. 3) No hoops to jump for integrating API that makes an App do things that WebApp cannot do. 4)…

It depends on what your goals are.

If you are looking to develop for iOS (or any single environment) only, then all the points you make are great, and you should absolutely stick to native development for that environment.

However, if you are looking to target multiple platforms (and by that I don't just mean mobile, but potentially also web, desktop, and more), then some of these frameworks start looking a lot more interesting.

React Native has split the UI from the rendering, and as such now has render targets for much more than just iOS and Android.

And while you can't share 100% of your code, you can develop a shared component library that can all feed into various native shells as needed. That shell can handle your environment-specific bindings and integrations, while your shared components provide your application's UI and interactions.

Of course it all depends on what you are building, and not all apps would be a fit for this approach.

Re: Vue Native (2018)

#46

Post by ppeetteerr »

vlz wrote: post #17

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. [1]: https://github.com/GeekyAnts/vue-native-core says as much.

I just saw this as well. I realize that some people might be more familiar with Vue than React, but wrapping RN seems overly complicated and adds yet another layer of abstraction.

Re: Vue Native (2018)

#47

Post by dvfjsdhgfv »

mrtksn wrote: post #22

What are the trade offs/Adventages to use cross platform tools for app development in 2021? The advantages of native iOS development, off top of my head: 1) Swift is very pleasant to use and it is fast. 2) The UI libraries that I need to learn: UIKit and SwiftUI. SwiftUI is also very pleasant to use and it is getting there. 3) No hoops to jump for integrating API that makes an App do things that WebApp cannot do. 4)…

In theory just just write code once and have the app ran on both platforms. In practice it's much more complicated, and whenever you need to do more than the framework offers your situation is much more complicated than in the case of native development. Also some features are implemented in different ways on both platforms and you need to get into details anyway. So being familiar with native APIs is a great advantage even if you use the cross-platform approach.

Re: Vue Native (2018)

#48

Post by jamil7 »

aceisnotmycard wrote: post #33
jamil7 wrote: post #18

Earlier quoted context omitted.

Not exactly the implementation you described but Kotlin Multiplatform is targeting this workflow. Shared business logic in Kotlin and Native UI on each platform. You can currently compile to iOS/Android/Web and Desktops. I imagine the could support wasm at some point too. Edit: Kotlin Multiplatform not Kotlin Native

I think you meant Kotlin Multiplatform: https://kotlinlang.org/docs/reference/mpp-intro.html . Kotlin/Native is a LLVM-based backend which is used in case of Kotlin Multiplatform for iOS part.

I absolutely did! thanks. Regarding OPs point I just double checked and it does indeed support WASM as a target now.

Re: Vue Native (2018)

#49

Post by oakesm9 »

mrtksn wrote: post #30
oakesm9 wrote: post #25

Earlier quoted context omitted.

The advantage is that you can access ~100% of the mobile market with a single codebase for about 10% extra work compared to native on a single platform. Performance is roughly the same and you have access to most of the platform features that most apps need.

That's the obvious value proposition but There's a reason why sporks did not make spoons and forks obsolete. I messed around with a few cross platform tools a bit and my impression is that if you want to make something that is better than a WebApp you actually have to learn a lot more tools and frameworks and everything feels like falling apart and you are depended on multiple vendors to upkeep the tooling. The momen…

I work on React Native projects for a living and what you're saying is true. You need to use both Xcode with ObjC/Swift and Android Studio with Java to get the most out of React Native. That comes with the additional complexity of also needing to learn how Xcode builds projects and how Gradle works.

That's a lot of extra complexity, but it's also no less than if you had built two native apps. You're now just expecting a single team to manage it.

My background is in "real" native development (both Android and iOS) so I get on fairly well with this, however, for people coming to React Native from the web side of things, it's a lot to take in.

Overall, I still recommend to 90% of my clients that React Native is a good way to go if they have limited time and budget. For larger companies, they might have the budget to build and maintain two apps.

Also, most apps really are just UIs on top of a REST API. And even if you do want to make something more custom, you can always create a native component or module yourself for each platform and wrap it to use it with the rest of your React Native app. That way the "boring bits" like the account management, data handling, etc can all still be shared.

It's a trade off, but just about works out for me.

Re: Vue Native (2018)

#50

Post by Malfunction92 »

user-the-name wrote: post #34
Malfunction92 wrote: post #2

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. Of course it’s probably a little too soon to completely switch live apps to this, at least until it stabilizes a little bit. 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?

If your goal is to actually put out high-quality apps, do not switch away from doing them natively. No cross-platform kit can compete. You are making sacrifices, sometimes big ones, in order to get the cross-platformness.

I've thought a lot about this. My biggest problem is that I'm the only one maintaining the project, and using something like vue + cross-platform would make things a lot easier than maintaining 3 different code bases (ios, android, web).

My understanding is that cross-platform tools have matured enough to be used as replacements to native implementations. Is that not the case?

Post reply on HN