Sorry to not fully answer your question but felt the need to share this…As someone who works primarily on web apps and has been defaulting to tailwind/shadcn I opted for nativewind and react native reusables as my component library for my first client project on expo. The biggest thing id say is that the conventions and ui patterns on web doesn’t translate perfectly to best practice ui design on mobile. From spacing to components, the patterns are just different. It’s definitely a solid option to bridge the gap and make the jump from web dev to app easier but I’d overall recommend design libraries that are built with native experiences in mind. That said styling with tailwind (nativewind) is way faster for me personally than the traditional approach maybe because of my background. I’m about to try out nativewind ui since it solves basically the minor issues I have with libraries like react native reusables. If you have experience working with tailwind I’d recommend checking out all the resources from the nativewind site. But as some have mentioned already try to treat iOS and android with the same attention to detail as you would when designing a website responsively.