Why we built gluestack-ui

gluestack-ui v1.0 was launched almost a month back, and we are now 1000+ stars strong on GitHub. But as new users adopted the library quickly, we also got queries and concerns on how gluestack-ui compares with its predecessor NativeBase.

Key concerns were received from users with ongoing and finished projects dependent on NativeBase. We feel that their apprehension is valid and understand their perspective.

The motivation

NativeBase served millions of downloads and powered apps across Android, iOS and the web. But over the years we learned a lot about what developers actually need: more control over styling, better performance, and a smaller, more predictable runtime.

gluestack-ui is our answer to those learnings — a set of copy-paste components and patterns built for flexibility and customizability.

What changes for NativeBase users

NativeBase remains stable and available. There is no forced migration. Teams can continue shipping with NativeBase while evaluating gluestack-ui for new work at their own pace.

NativeBase is now gluestack. The ideas live on, refined.

Learn more

Head over to gluestack.io to explore the new library, components and documentation.