The idea is to stop depending on these libraries for multiple reasons 1. You will be stuck with the styling they offer. In most cases it is hard to customize the UI as you need. 2. You have no control over the conventions. With every new version you could see components named differently. 3. Lack of support and the projects may be discontinued like this.
Did nativebase helped you in speeding things up? I'm gonna use it for a freelancer project and was wondering if it's the best solution, i'll also use nativewind along with it
@@magne6049 It is very much bloated, i just ended up using the react native paper. It has the MD3 support and most of the components i need. but yeah nativebase is good as well
Even for a smaller project like mine, is so slow when navigating through screens with forms or lists inside.
Keep up bro. Impressive
The idea is to stop depending on these libraries for multiple reasons
1. You will be stuck with the styling they offer. In most cases it is hard to customize the UI as you need.
2. You have no control over the conventions. With every new version you could see components named differently.
3. Lack of support and the projects may be discontinued like this.
It’s deprecated now btw. Debating between Tamagui or React Native Elements.
there is Gluestack UI from them
Did nativebase helped you in speeding things up? I'm gonna use it for a freelancer project and was wondering if it's the best solution, i'll also use nativewind along with it
0:47 he answers
@@magne6049 It is very much bloated, i just ended up using the react native paper. It has the MD3 support and most of the components i need. but yeah nativebase is good as well
How big does the app need to be before the performance issues become noticable on Android?
Hey man do you have Discord? I would love to chat with you about a video you made in the past?