@angel54689 Not directly no, it's a complete re-write from scratch, so has breaking changes. But we do have a migration guide where you can find all the information. https://docs.nativebase.io/migra...
@angel54689 You can keep using v2 for your existing apps(If you don't want to the effort of porting the existing codebase to v3).
But, if you start a new project consider using v3, I am sure you would really like the new API, we have made a conscious effort towards making NativeBase, a library with great developer experience.
If you do try it, let us know your feedback :)
P.S: You can also join our discord server, some people there have gone through the process of porting their existing apps, and can help you if you start going that path :)
Months of hard work in building the component library for mobile & web, it's finally out 🥳
The team is trying to solve our problem of recreating building blocks for every project so that you don’t have to. NativeBase v3 components are accessible, mobile-first, dark-mode enabled, customizable and performant.
NativeBase v3 is targeted for React Native, React (Next, CRA).
Docs: https://docs.nativebase.io/
Kitchen Sink: https://github.com/nativebase/ki...
Features:
🎨 Highly themeable
♿ Accessibility powered by React Native ARIA
🛠 Utility props
📚 Rich component library
🖥📲 Responsive
📈 Consistent across all the platforms
🌓 Supports dark mode
👩💻 Shared codebase between React Native & React (Next, CRA)
Top priorities:
• Unified Navigation with Next.js & React Native
• Reduce runtime overhead
• Bundlesize & Treeshaking
Go and start building and report issues! We are here to fix it!
I have been using NativeBase since the v2 and I have always liked the vast amount of components it supported at that time. Now, with v3 (have been playing around with it), I love the majority of features required to build a mobile app (specifically React Native) such as accessibility, theming in general, dark mode, etc are in support and have options to customize them.
Highly recommended!
@yan_h Welcome to the 21st century :) It's how we write codes for the past 2 years, and the web version is based on React native web, which is used by Twitter Mobile Web version.