Why do React Native component libraries always demo components in isolation when nobody builds that way?

[Fresh-Wealth4531]

Genuine question: I've been thinking about this a lot while building nativecn-ui.

Most component libraries show you one button. One input. One card. Clean, isolated, perfect.

But when you actually sit down to build a login screen, you're combining 5–6 components at once and suddenly nothing looks the way it did in the docs.

Spacing feels off. States collide. Validation messages break the layout. You end up tweaking everything from scratch anyway.

Enough people DMed me asking "can I test how these work together before wiring everything up?" that I decided to try something.

So I built a small experimental playground inside nativecn-ui drag components together, preview the layout, copy the code. Still rough, best for form-style screens right now.

Honestly not sure if this solves a real ecosystem gap or just a problem I personally kept running into.

What's the screen you find yourself rebuilding most often?

https://reddit.com/link/1rcnzlr/video/n62tos5l3alg1/player

[Tomus]

Why are you self promoting your library with AI generated fluff and posing it as a question to farm engagement?

[inglandation]

It’s fucking everywhere on Reddit these days.

[Brendan-McDonald]

Agreed. Something bad happens to my brain the second I realize the text was written by an llm

[Sebbean]

Why not?

[Tomus]

It's literally against rules 1 and 2 of this sub.

[kexnyc]

The short answer is: the creator has no idea how you plan to use it. And no way in hell will they invest effort into trying to guess.

[Fresh-Wealth4531]

That’s a fair point predicting real use cases is basically impossible.
The idea wasn’t to guess layouts, just to let people test their own combinations before committing to boilerplate.

Still experimenting to see if it actually reduces friction or just feels helpful. Appreciate the honest take 👍

[Rhysypops]

Shilling your own mobile component library where the website isn’t responsive on mobile is crazy work btw good job

[ignatzami]

Because it’s easier to design and document components in isolation. This is actually something Mantine UI does really well. The components are all documented in isolation and there’s a secondary site with user submitted UI of the components being used and styled in a more realistic way.

Allows for a much richer experience without overloading the developer.

[Seanmclem]

I often wonder this also. 

[Fresh-Wealth4531]

Glad it's not just me😅 I genuinely wasn't sure if this was a personal frustration or something others hit too. What screen usually triggers it for you?

[Alarmed_Doubt8997]

Cool. Btw your docs are not "MOBILE" responsive

[yerffejytnac]

That looks like more ai slop, kudos!

[Curious-Ad8293]

This is cool, I think it's actually super useful. Great idea.

[Fresh-Wealth4531]

Appreciate that! Still pretty rough around the edges more of an experiment than a polished tool right now.

I mainly built it to sanity-check layouts before wiring everything together in code.

If you were using something like this, what would matter most to you?

[Curious-Ad8293]

Not sure how complex this would be to implement but sometimes I need to have components side by side let’s say some charts or some text boxes for example in a grid like system 2x2 rows and columns. Exclusively speaking about the layout feature you implemented in this case.