First of all, Hats off to GeekyAnts effort!
It's certainly better than using Vue with Corodova plugin and can be a competitor to Weex as well provided Vue Native will not have any major incompatibility issues with React Native.
Although it caught my attention at first but on a second thought, Vue-native has a direct dependency on React Native. And the repercussions of direct dependencies are high as the incompatibilities rise and optimisations limits to the dependency. Remember the initial days of Scala?. React Native is an abstraction for building a Native App and Vue-Native is an abstraction over React Native. To be more specific, it's
vue-native(abstraction) <-> react-vue <-> react-native(abstraction) <-> native app(what we want)
With these multiple levels of abstractions, even if we compromise build time but most likely app experience will be impacted. When I say app experience, the least I would expect is the Transitions and Animations (this is one of the factors where native app stands out when compared to hybrid app) and React Native is does decent job at this comparative to other hybrid frameworks probably because it uses native OS components for most of the UI elements AFAIK.
Regardless of what I said above, sometimes, just having a native app which serves the purpose and the footprint in the mobile ecosystem will be more important for businesses than to focus upon micro experiences of users. This is when hybrid apps came into picture I guess.
In a nutshell It's good as of now and probably can remain the same as long as it either acts as a reflection of React Native in terms of features and compatibility otherwise Vue Native should eventually move towards it's own version of hybrid framework (which would be awesome!)
Thos who haven't heard of Vue Native, here's a good blog on medium: