34 ms·
Vue Native
- jefflombardjr 8y ago> How does it work? This is fork of react-vue https://vue-native.io/docs/how-does-it-works.html https://vue-native.io/docs/how-does-it-works.html
- ivanfon 8y agoHow does this compare to nativescript-vue? https://nativescript-vue.org/ https://nativescript-vue.org/
- hardwaresofton 8y agoIt looks like Vue Native is a wrapper around React Native UIs https://github.com/GeekyAnts/vue-native-cli https://github.com/GeekyAnts/vue-native-cli (in the README) I personally am following/want-to-use https://nativescript-vue.org/ https://nativescript-vue.org/
- Kihashi 8y agoSince the underlying tech is React Native (Vue Native) and Nativescript (Nativescript Vue), here's a comparison (albeit written by someone from Progress/Telerik, who maintain nativescript): https://www.quora.com/What-are-the-key-difference-between-ReactNative-and-NativeScript/answer/Valentin-Stoychev https://www.quora.com/What-are-the-key-difference-between-Re... It doesn't touch on the Vue integration, since that's relatively new.
- dvdhnt 8y agoSite is broken on mobile. Styling issues make it undreadable.
- xrd 8y agoIt's hilarious that you can't view this site on native browsers. How ironic!
- xab9 8y agoProbably they are just people and didn't have the time to write a responsive css, which is not as simple as it sounds, especially if you are not using a grid framework. Feel free to fork the site's code and send them a PR.
- quangio 8y agoSimilar projects: https://weex.incubator.apache.org/ https://weex.incubator.apache.org/ https://www.nativescript.org/ https://www.nativescript.org/ I think Weex has better performance and lighter overhead than this(?)
- kendallpark 8y agoI'd love to get a side by side comparison of Weex and Vue Native.
- shubham_sinha 8y agoWeex lacks english documentation and most of the Weex devs are from China and support forums also tend to be in Chinese. By far RN has best documentation and plugin / package ecosystem. A full fledged app can be built using RN. Whereas it'll be hard for Weex, Vue-Native. Just search for Google Maps package for any of these frameworks, you'll have tough time finding any (barring React Native)
- threeseed 8y agoXamarin: https://www.xamarin.com https://www.xamarin.com Xojo: https://www.xojo.com https://www.xojo.com Flutter: http://flutter.io http://flutter.io
- maxwell2022 8y ago> Vue Native transpiles to React Native. Why would you not use react native directly then? I don't get it
- adamnemecek 8y agoBecause you prefer vue.
- neya 8y agoA lot of us prefer Vue over React, I for one favor Vue over React personally and have been using it in all my recent projects. So, just a matter of preference for those who don't want to use React.
- mieseratte 8y agoI'm curious, what do y'all actually like about Vue over React? I spent over two months doing proof-of-concept migration work for an AngularJS to (React-Redux|Vue-Vuex) and, other than the component-data wiring it does internally, I found it to be worse in nearly all respects. Despite being an "opinionated" framework, Vue provides so many escape hatches and alternatives that it, in practice, hardly seems opinionated. Additionally, the templating language it promotes seems like a step backwards compared to JSX render functions. As it were, the "unopinionated" React, by offering a small handful of primitives, ends up making things simpler and more ergonomic to work with. I really can't seem to grok why folks like Vue over React.
- Kihashi 8y agoI got into Vue because it was much easier to approach coming from a back-end (Python/Flask/Jinja or PHP/Symfony/Twig) perspective. It made it easy to adopt small pieces and learn as I went. React probably allows this sort of thing, too, but the documentation for Vue pointed it out first thing. Since I've started working with it, I haven't gotten a compelling reason to change to react or angular.
- 8y ago
- elyobo 8y agoPage consists of an example (useful) and slides (not). Might look again once there's some useful content; slides aren't _quite_ as bad as a video, but it's pretty awful. Edit: ah, the get started links to real content. Missed that.
- zpr 8y agoMaybe you also didn't notice you can scroll down on the slides to get more info on the headlining topic (I missed it at first).
- rubyn00bie 8y agoPardon my ignorance on the matter, and I’m truly sincere when I ask, but why does there need to be a *-native library for “each” different JavaScript framework? Why this instead of say Electron or something that seems, to me, to be more general purpose and thereby useful[1] (I’m not coupling my mobile apps to a single JavaScript framework). ... I suppose “React” is more of an API now-a-days, and so it may not be so bad to port to another transpiler/compiler/build system? But I still feel like I’m missing something. Are folks writing games in React or something that requires the performance optimization’s from a specific build system? If so would anyone mine showing an example? Or just learn me in general? Many thanks. 1. Don’t take “useful” personally please. I mean it mostly in the context of shipping and supporting an app for a few years. Which... is probably not the best _use_ of “useful.”
- tmh79 8y agothere is some react-vr code for occulus
- ehnto 8y agoIt just seems like an odd tooling choice. The rest of the VR ecosystem uses completely different tooling and languages. Why not build a good GUI library in one of those? I just don't see what React brings to the table I guess.
- omeid2 8y agoI think it basically boils down to the prominence of what I call Universal User Experience, which is basically an attempt to give users a similar experience across different device and form factors. I believe this UUX is the powerhouse behind this second(?) weave of Write Once Run Anywhere and why we have so many libraries with web/html and iOS, Android, and various desktop frontends.
- danielrhodes 8y agoI've been down this road: it did not end well. Facebook also went down this road and seems to have realized something similar (and hence why they pulled back on HTML5 on mobile and have not attempted to make React Native fully cross platform). The reason why is essentially every platform (iOS/Android/web) has its own characteristics, charms, quirks, habits, and behaviors. Trying to smush these all into one unified UX experience is producing something that feels and acts weird on every platform, and people notice. Trying to unify is a solution for a developer problem, not a solution for a user problem -- and thus it's not really a problem. What this comes down to is focus. Developing across multiple platforms is a hard problem and requires a lot of work. It's really only suitable for larger teams. As a small team, it is better to focus on one platform, do really well, and then later when you can afford it, go to other platforms.
- baybal2 8y agoI'm no longer a career webdev, but when I still do need to do something front-end related, Vue is a tool of choice. I really like Ethan's non-doctrinal approach, and that Vue is as isolated from dreaded committee designs of opens source projects invaded by corporate types. I still regard GTK+ as one of the best C GUI toolkits. Particularly when it comes to thought-through design of layouting mechanism and that the widget lib was build with ergonomic in mind. When you work with UIs in plain C, you invariably come to getter-setter pattern. I wonder, can Vue guys somehow glue Vue components to GTK widgets?
- tribby 8y agowhat's the difference between this and react-vue?[1] I would prefer to be using weex, but that project has seemed stagnant ever since it became part of the apache foundation. or at least, they haven't really updated their site or fleshed out the docs etc. it's very hard to get buy-in from other developers because of that. 1. https://github.com/SmallComfort/react-vue https://github.com/SmallComfort/react-vue
- htormey 8y agoCan someone explain what the differences are between React and Vue? Why is this a good idea and what benefits would it afford me as a React Native developer?
- shubham_sinha 8y agoVue is more beginner friendly. It's easier to learn (particularly for people coming from Angular Js background). As a RN developer you won't be getting any benefits as such. If you're already comfortable with React and JSX then jumping to Vue-Native won't be of any use. But if you're purely a HTML, CSS, jQuery dev and want to get into mobile app dev, I guess Vue-Native will be quite easy to learn and build production ready apps.
- neya 8y agoThis page is a good start, it discusses the differences in detail: https://vuejs.org/v2/guide/comparison.html https://vuejs.org/v2/guide/comparison.html My personal experience wasn't that positive with React and then, the whole treatment of JSX as a first class citizen isn't really my style (although you're allowed to use React without involving JSX). Vue just feels more mature (personal opinion) and much, much easier to reason your code about, down the line in 6 months. I've had super-complex apps that required so many nested components and I had no problem picking them up after about 6 months. With react, you have to be careful as it's easier to shoot yourself in the foot (personal opinion). Also there's flux, redux which do require a bit of a learning curve if you want to architect your applications using them. Vue has something called Vuex which again, in my opinion is slightly friendlier to beginners. I re-wrote my entire teaching syllabus for my programming course to use Vue instead of React, simply because it's much better to maintain Vue apps rather than React apps after 6 months, which is the most important value add for me in any framework. Anyone can pick up a trendy new JS framework and hack a TODO app over the weekend these days, but if you're working on client side, or some serious projects that require long term commitment and maintenance, then you will realize it's more important to consider the framework's maintainability and code readability. For me, Vue triumphs React in this aspect easily. So, there you go.
- 8y ago
- reilly3000 8y agoThis is the only missing piece that has held me back from jumping into Vue. I know its not the most advantageous aspect of the framework, but my personal favorite aspect of it is the single file components. Being able to create a complete logical unit of UI of in one file feels more natural and produtive. All the speed of inline styles without the guilt and shame.
- sideproject 8y agoYes! :) I've been using VueJS for awhile and my next step was to create a mobile app - either via RN or even Flutter. But, hello vue-native!
- pdanpdan 8y agoYou can also give a shot to Quasar (quasar-framework.org) that will provide you with single code base SPA, PWA and mobile through Cordova, and in a few days also SSR. Disclaimer: I'm also contributing on this project.
- dabernathy89 8y agoDon't forget about NativeScript Vue!
- sjellis 8y agoFWIW, the next version of Ionic (in beta) decouples from Angular, so that people can use the tools and platform support of Ionic to build mobile apps with Vue, or whatever they prefer.
- um_ya 8y agoThank god. Angular is just way too big now. There's way too many files and they try to push you into using typescript.
- sebastienrocks 8y agoThis uses react-native, I would not consider jumping on the Vue ship if you've been waiting for a native solution. This seems more like a hack-y way of going about it. Some other solutions are out there, one of the main ones being nativescript. However it feels like the community still hasn't "agreed" on a solution like React did. To my knowledge, Vue still does not have anything official around native. I would consider waiting for now, unless this proposed solution suits you. (This doesn't mean you shouldn't start using Vue elsewhere however, I have been using it for the past few months at work on a pretty large-scale project and it is my favorite library by far, for many different reasons).
- LeoNatan25 8y agoOh look, another “native” nonsense.
- ilurkedhere 8y agoI'm confused. Wouldn't "native" imply it uses platform widgets rather than HTML?
- hardwaresofton 8y agoI prefer NativeScript[0] & it's vue-specific extension NativesScript Vue[1] due to NativeScript's ability to work with more than one paradigm/framework. NativeScript enables any Javascript application to become a mobile app (along with ones built in Angular and Vue) and I think that's pretty great. [0]: https://www.nativescript.org/ https://www.nativescript.org/ [1]: https://nativescript-vue.org/ https://nativescript-vue.org/
- jbverschoor 8y agoAnd there's no need to make bridges. Simply access the native API from javascript/typescript
- k__ 8y agoNativeScript simply binds to all native APIs by default?
- jinglebells 8y agoEffectively yes, but not like that. You can access all native APIs with a marshalling layer which maps Javascript to Objective C or JAVA. For example, when the Javascript parser sees var className = NSStringFromClass(NSArray); The ObjectiveC side executes NSString *className = NSStringFromClass([NSArray class]); Then creates a link between the JS object and the ObjectiveC object. Any methods/properties you access on the JS object, get executed or read from the native component. It's really quite clever and why we use Nativescript to bring corporate apps to market quickly and cross platform while not worrying about the limitations of the Javascript bit, because you can always access the native APIs anyway.
- k__ 8y agoHaha, nice. First time I heared about this killer-feature :D
- pstuart 8y agoLooks interesting, and it's sponsored by Progress? Looks like old dogs can learn new tricks.
- ivm 8y agoIronically I just saw the tweet about Udacity team removing React Native from their apps: https://twitter.com/n8ebel/status/1006244834351312897 https://twitter.com/n8ebel/status/1006244834351312897
- k__ 8y agoI can understand this. I already planned 3 weeks for the Android port of an app. But probably still better than the 5 months the iOS app took to make. I have to set up an Android build environment and install all the Android versions of my native modules. Since iPhones required dynamic sized UIs for iPhone5/iPhone/iPhone+/iPhoneX anyway, I expect to use most of the UI code without any change.
- mgalka 8y agoIronic the site does not seem to be responsive
- squiggy22 8y agoYes. Its worse than terrible on a mobile. Going to see if its open source and put a pull in for it.
- kingosticks 8y agoIf that doesn't put you off I'm not sure what would.
- sanketsahu 8y agoGoing to fix it ASAP.
- pjmlp 8y agoI get an HSTS error while accessing the web site.
- inopinatus 8y agoTheir website may have repurposed the look and logo of the Vue project, but (unlike React Native's relationship with React) this doesn't appear to have any official association. In particular, Evan You called it an "interesting approach" but added "not endorsing this"[1]. https://twitter.com/youyuxi/status/1006565660091125760 https://twitter.com/youyuxi/status/1006565660091125760
- codesternews 8y agoIt's based on react-vue[1] and It is internally using react-native. 1. https://github.com/SmallComfort/react-vue https://github.com/SmallComfort/react-vue Why but Why.
- patates 8y ago> Introduce react-vue-loader, which compiles the Vue component into a React component. As you might think, your previously written Vue components can run inside the React component, and your React components can also run inside the Vue component How did it come to this?
- securityfreak 8y agoI honestly do not understand how did a large part of the software engineering community get to this point of idiocy. Is this due to the principle of getting to the market first and quick prototypes? I don’t see a quick way back.
- matthewmacleod 8y agoFrankly I find your view pretty offputting. I’m not really that into the idea of JS-as-a-platform, but it obviously emerged because it fulfilled certain requirements that weren’t covered elsewhere. The “way back” from this is for people like yourself to stop dismissing others’ work as “idiocy” and start building better solutions to these problems as you see them.
- walterstucco 8y agoIt just made possible for web developers to jump on the native apps train It's hard to think of it as an improvement The idiocy is in the hundreds of engineering hours spent to build half baked solutions that never work as expected and never will It's developers not wanting to adapt, while if they spent half of that effort on red or even visual basic 6 we would have end up with something better Diversity is king, web everywhere for everything will impoverish the entire developer's community
- 8y ago
- lwansbrough 8y agoHere's my pitch for a better ecosystem: we develop an intermediate standard for fundamental UI building blocks (divs/blocks/layers, images, video, etc.) + a layout engine, sort of like the DOM. Shells (browsers, native platforms like React Native but without the React requirement, etc.) would give JS renderers access to the lowest level painting calls available (ie. "repaint this node") along with programmatic access to the new standard UI API. Renders could then build on top of that API, implement the draw call optimizations themselves based on whatever makes sense for the rendering engine (for instance, React Fiber would be issuing draw calls differently than Vue's rendering engine.) This would allow developers to get native performance out of a web-based rendering context. It would also be theoretically easy to build new renderers around the standard UI API. So you could swap out your backend between browser-native and a mobile/desktop library backed by OpenGL/WebGL, or another headless solution, etc. Importantly, I think you need to limit the scope of this new UI standard (perhaps just to basic shapes, like how SVG is similarly limited), that way you leave UI implementations like dropdown boxes to ecosystem programmers (so you'd have a dropdown box for each React, Vue, etc. -- this sounds bad but people do this already.) Limiting the API scope also means making it easier for new renderers to enter the scene. Compare such a world to the current hellscape that is building your own HTML renderer. The API is so insane it's really only possible for big companies to take it on (Google, Microsoft, Apple, Mozilla.) How this ties back into this post: you could create an _____ Native, which would really just implement everything you want from React Native, but without React. Then you can just plug Vue or React into the renderer and boom you're done. Edit: Observant people will notice my ideal system resembles X11. Indeed, I think X11 is an interesting proposition in "shell" (browser, native) contexts, as shell applications are inherently window-managed and sandboxed. This allows for applications to reinvent the wheel without disrupting the fundamental UX of window management on the system OS.
- mark_edward 8y agoWeb Components?
- lwansbrough 8y agoNo, because web components assume you're using the DOM. Which we definitely do not want. I want to go lower level. Give me a hashmap of nodes currently on screen. Let me design how the nodes are arranged in a render tree. Let me design how the nodes are redrawn. Let me design how the nodes are styled. I shouldn't have to compile my styles to CSS. Make the browser a rendering slave with a small but effective layout engine + UI API.
- EugeneOZ 8y agoApp stores should be abandoned, web app is the only thing you can 100% control. If you can't publish critical update for your app in minutes, just because you use phone vendor's store, then that store is a huge priblem. If store can just uninstall your app in any moment (without user's request) - it is a huge problem.
- mathiasrw 8y agoAnyone else getting "This site is blocked due to a security threat."?
- arendtio 8y agoFor those who haven't heard of it, there is a project to render native desktop applications with Vue too: https://github.com/mimecorg/vuido https://github.com/mimecorg/vuido
- pietrovismara 8y agoThe funny thing? The website renders for desktop on my S8, making it completely unusable.
- snarfy 8y agoAren't native Vue apps already supported with Weex[1]? Why would I use this over Weex? [1] - https://weex.incubator.apache.org/guide/ https://weex.incubator.apache.org/guide/
- deleted 8y ago[deleted]
- steiner_j 8y agoI'm genuinely confused as why this is getting so much attention. The NativeScript-Vue integration is out for over a year already. It fulfils exactly the same purpose, without the additional strange cross-compilation/transpilation.
- jacob019 8y agoSo are all those beautiful UI elements in the kitchen sink demo included?
- pier25 8y agoConsidering there is already Weex and NativeScript with Vue, what does this add? Personally I think Flutter will become the dominant cross platform solution in 2020 or so. ReactNative has always seemed like a hack to me.
- spraak 8y agoWhat about it seems like a hack? Why do you think Flutter will become dominant?
- pier25 8y agoFlutter basically works like a game engine. It has a rendering area and it uses Skia to paint stuff. This means it has a lot of control over what's going on and the bridge to the OS is minimal. ReactNative is basically giving tons of instructions from the JS engine to the OS. Sure the performance of the OS is great, but this has limitations and many moving pieces. For example animations used to be a problem in RN because someone thought it was a good idea to send instructions on every frame from the JS engine to the OS. Of course many devices can't keep up with this, and I imagine Facebook solved this by creating an animation engine on the native side of things and JS only passing start/end states and such.