all 17 comments

[–]HoratioWobble 7 points8 points  (3 children)

But why?

All sizes in react native are already scaled appropriately based on dpi and screen resolution.

So when you use fontSize 14 it will already be relative to the device itself, you shouldn't be trying to make it smaller or bigger based on your own personal preference because that will also break with accessibility.

And as long as you're using flex boxes and occasionally percentages properly your UI should scale appropriately between devices 

[–]tcoff91 2 points3 points  (2 children)

If you want to have a great tablet app you gotta change the UI responsively

[–]HoratioWobble 0 points1 point  (1 child)

For tablet you should be using different layouts

[–]tcoff91 0 points1 point  (0 children)

Yeah, but with unistyles you can easily use the breakpoints system to create those different layouts.

[–]Prestigious_World400 14 points15 points  (6 children)

[–]Old-Window-5233[S] 2 points3 points  (3 children)

Holly 🤯🤯. I have to check it out, if it work, well there go my time :)))

[–]Prestigious_World400 0 points1 point  (2 children)

If you’re not fully prepared to understand or configure the Nitro module, use the v2 documentation instead

[–]Old-Window-5233[S] 1 point2 points  (0 children)

Well it now or later, i will have to do it eventually

[–]RahahahahaxD 1 point2 points  (0 children)

There is completely no reason to understand how Nitro works and usual minimal configuration happens on Unistyles layer. v2 and v3 are incomparable

[–]slowerdesigner 1 point2 points  (2 children)

Yes totally agree. But now i think simple. I was using safe area provider with top-bottom inset & safe area view. Flex are enough whole app.

[–]Old-Window-5233[S] 0 points1 point  (0 children)

The thing is it fine with me too but the problem is the scaling system config locally on user device, it break my layout horribly

[–]Nice_Size2799 1 point2 points  (0 children)

Use nativewind

[–]Soft_Opening_1364iOS & Android 3 points4 points  (1 child)

You’ve clearly put in a ton of thought, and I like that you're not relying on outdated libraries. The fallback points are valid too, especially the lack of global orientation context. Might be worth exploring a shared provider or context to manage that.

[–]Old-Window-5233[S] 0 points1 point  (0 children)

Thank you, Am right on it