Vue.js原生移动开发平台推荐及Vue转React工具咨询

Hey there! Let me break down my hands-on experience and thoughts on these tools based on my time working with cross-platform mobile development.

I’ve messed around with both for small to mid-sized projects, and honestly, the negative buzz you’ve heard isn’t unfounded. Let’s break them down:

• Weex: When it first launched backed by Alibaba, it seemed promising—Vue-first, native rendering, and cross-platform support. But over time, I noticed major pain points:
  • The community and official maintenance have slowed to a crawl. Documentation is outdated, and when you hit edge cases (like custom native modules or complex animations), finding solutions is like searching for a needle in a haystack.
  • Performance on Android is hit-or-miss. Complex pages with lots of dynamic content would lag, and compatibility with newer Android versions was spotty. iOS was a bit better, but not by much.
  • The ecosystem of ready-to-use UI components is tiny compared to React Native, so you end up building a lot from scratch, which eats into development time.
• NativeScript: This one felt more polished than Weex, with better official integration with Vue. But it still has its flaws:
  • App size is a big issue—even a simple Hello World app packs a larger footprint than an equivalent React Native app. Startup time is also noticeably slower on both iOS and Android.
  • While you can call native APIs directly, the learning curve for bridging custom native code is steeper than React Native. Plus, some UI components lack that "native feel" out of the box, requiring extra tweaking to match platform standards.
  • Community support is better than Weex, but still nowhere near React Native’s level. Troubleshooting issues often means digging through old GitHub issues rather than active, up-to-date forums.

I’ve looked into React-Vue for a side project where I wanted to reuse some existing Vue components in a React Native app, and here’s what I found:

• It works decently for simple, stateless Vue components. Basic UI elements like buttons, cards, or static lists can be converted or rendered without too much hassle.
• But once you get into complex components with Vue-specific features (like computed properties, watchers, or Vuex integration), things start to fall apart. The tool tries to map Vue’s reactivity model to React’s state management, but the translation isn’t perfect—you’ll run into unexpected bugs and performance quirks.
• Maintenance is another red flag. The project hasn’t seen major updates in a while, which means it might not support the latest versions of Vue or React Native. Relying on it for a production app feels risky, since you won’t get fixes for new compatibility issues.
• If your end goal is to move to React Native because of its better performance and ecosystem, my advice would be to bite the bullet and learn React’s syntax directly. React-Vue is a band-aid solution at best, and you’ll save more time in the long run by building your app natively with React Native rather than trying to bridge Vue code over.

内容的提问来源于stack exchange，提问作者mha