The Present and Future of NativeBase

Building NativeBase

NativeBase's evolution stems from continuous experimentation. Version 1 functioned as a UI library for dropping components into environments. The second iteration drew inspiration from Material Design with reskinned components. Version 3 became transformative.

"The NativeBase v3 solved many issues the React Native community faced in 2018. At that time, most websites looked like cookies made from the same mold."

Bootstrap CSS and Material UI created this uniformity until Tailwind introduced utility-first design. The team developed a similar approach emphasizing usability and universal code compatibility. Chakra UI's arrival sparked misconceptions about shared APIs, though NativeBase utilized Styled System internally for utility props.

The library launched successfully. Through iterations and bug fixes, the team maintained consistent updates. React Native ARIA development bridged accessibility gaps across React Native and React platforms.

Today

NativeBase now achieves 65,000 weekly downloads, doubling the previous year's volume. Code quality improvements have attracted industry leaders, including a major restaurant chain deployment currently underway.

The team aims to establish NativeBase as the premier UI and component library for React and React Native, empowering developers to "write code once and deploy it everywhere."

The Future of NativeBase

Design systems that align every stakeholder with a click

The organization is transforming NativeBase into a spec-based system. Currently shipping as a component library with design theme, this transformation will enable effortless design system creation across ecosystems.

An upcoming tool will accept minimal inputs (primary color, sizes, fonts, columns) and generate multiple outputs: component libraries matching NativeBase, Tailwind CSS, and Chakra UI specifications. The tool will simultaneously produce design system documentation without requiring NativeBase authentication.

Implementation scenario: An enterprise configures brand colors and design parameters through the tool. A single click generates:

• A component library
• A design system website containing:
  • Design Philosophy
  • Design Assets
  • Component library documentation

This approach aligns developers, designers, and decision-makers while reducing iterations and delivery timelines.

Upgrading the 'build once and deploy everywhere' concept

The team champions unified codebases across platforms. Starter kits will maintain momentum, including a Solito-based kit currently under testing that will become a standard offering (Solito plus NativeBase).

Expo's universal routing development, expected within six months, may enable integrations with the Expo team. The organization also plans revisiting no-code solutions like BuilderX.

Supporting the Community Remains a Top Priority

"NativeBase has always been community first, and that will never change."

The team continues supporting the latest React Native versions and future architectures while maintaining supporting libraries. API unification efforts span all platforms, involving collaboration with Nicolas Gallagher (React Native for Web creator) through React Native pull requests to align web and mobile ecosystem APIs.

Final Thoughts

NativeBase will remain relevant through community engagement and performance optimization. Weekly updates demonstrate commitment to continuous improvement.

"It will only get better from here."