Indeed. But it's worth pointing out "falling back" to flexbox isn't a solid backup plan-- most versions supporting flexbox also support grid, or are evergreen.
Assuming you can target browsers that support both, when does one pick flexbox over grids and vice versa? or does grids entirely replaces flexbox use case?
The community has been saying to use flexbox when you are only working with one axis, but I am not too sure that is true. Grid has adapted so many of flexbox’s rules, browser support seems to be the only differentiator.
I have a site in flexbox and planning to move it to grid to learn.
There are typical 1D places (stacks of divs, basically), so typical for flex. But since I can do the same with grid I wonder if I should use flex anywhere now (even for 1D).
Note: browser compatibility does not matter for this site
I guess if you really try, you can probably do all/most things flex can do with grid. However grid isn't really meant to have flexible responsive grid-cells, e.g. "how will the item1 grow in relation to item2 if we have additional space available?". Grid is more meant for scenarios where you wan't to completely change the layout of components of the site when you cross breakpoints, and when you have to do 2d gride-like layout (...duh!).
I doubt it - React Native's implementation of flexbox is different enough to make it very difficult to produce the same layout using the same out.
It's almost like an uncanny valley effect - its similar enough to lure you into a false sense of security, until you realise that defaults for flex-direction are reverse, or it implements flex/flex-grow/flex-shrink/flex-basis completely differently.
https://caniuse.com/#search=flexbox https://caniuse.com/#search=grid