Nicola reminds that the new architecture is coming, and presents the different initiatives to prepare the community:
Fernando Rojo regularly pushes innovation in the field of cross-platform (see also Moti
). Solito makes it possible to share even more code between web and mobile by offering navigation primitives shared between React-Navigation and Next.js. He’s been working on this for a while, it’s not the first iteration. It also offers a monorepo example
to get you started fast.
*…in all the ways that don’t matter 😄
Jamon recognizes that Flutter is good on many aspects (DX, CLI, e2e tests, upgrades, performance…). He presents the tradeoffs of both frameworks quite fairly. There is no clear winner. Some important points on which Flutter can hardly compete: web support, sharing code and knowledge, and the ability to hire.
Interesting for a React-Native dev (and also related to the article above) because it highlights the limits of its competitor Flutter to support the web (where React-Native-Web works wellà). Flutter web is not a good choice for content sites, but can remain a good solution for heavier web apps. Note that React-Native-Skia on the web will have similar tradeoffs.