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

21–30 of 190 posts

Re: Vue Native (2018)

#21

Post by seanalltogether »

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…

Additionally, html documents inside browser windows are naturally stateless content systems, but applications have never had this constraint. The design patterns that are successful on a browser are usually overkill in application development. Android has baked a few of these stateless design patterns into their core frameworks and then spent years coming up with various support libraries to overcome them.

Re: Vue Native (2018)

#22

Post by mrtksn »

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) 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.

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.

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.

7) The apps look in place by default, you actually have to work to make UI unconventional and weird.

I would imagine that on the Android side of things are also not that different.

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.

Re: Vue Native (2018)

#23

Post by u678u »

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.

Re: Vue Native (2018)

#24

Post by M4v3R »

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.

That's a dealbreaker for me. Not only you need to deal with quirks, bugs and feature-parity with lates OSes of Vue Native, now you also need to deal with the same for React Native. This is a bit too much for me, it's nice when it works but sucks when it stops to work and you spend the whole day to nail down some framework-specific issues.

Re: Vue Native (2018)

#25

Post by oakesm9 »

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)…

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.

Re: Vue Native (2018)

#26

Post by onion2k »

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 would imagine that on the Android side of things are also not that different.

The simple fact that there even _is_ an iOS side and an Android side is a large part of what makes cross-platform development appealing.

Re: Vue Native (2018)

#27

Post by um_ya »

M4v3R wrote: post #24
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.

That's a dealbreaker for me. Not only you need to deal with quirks, bugs and feature-parity with lates OSes of Vue Native, now you also need to deal with the same for React Native. This is a bit too much for me, it's nice when it works but sucks when it stops to work and you spend the whole day to nail down some framework-specific issues.

It allows any react native components to work in vue native.

Pretty valuable actually.

Re: Vue Native (2018)

#28

Post by simik »

string wrote: post #10
MatekCopatek wrote: post #7

Earlier quoted context omitted.

FYI - NativeScript has had Vue support for a few years now and is production ready (in my limited experience). Don't know now it compares to this though.

NativeScript unfortunately just can't compare with React Native in my experience. I've been a Vue dev/consultant for several years, I wanted to love NativeScript, but every single time I try to build something with it (last attempt was about 2 weeks ago) I come across a missing feature and end up begrudgingly switching to React Native.

Could you give a couple examples of such missing features?

Re: Vue Native (2018)

#29

Post by IgorPartola »

The_rationalist wrote: post #3
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?

Ionic and quasar already allow you to make Vue on smartphones

Ionic screwed me like a deck screw with their update path being more of a secret way into Mordor. Perfectly good app that can’t be compiled anymore without a full rewrite in what is effectively a completely different framework.

Re: Vue Native (2018)

#30

Post by mrtksn »

oakesm9 wrote: post #25
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)…

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 moment you say that your app is more than an UI to access a database, native on multiple platforms is actually easier.

Post reply on HN