Nope, you can limit the suffering for your devs by using Expo (RN) or Flutter (Needs Dart). The issue is as soon as you stray off the well laid path similar to

Nope, you can limit the suffering for your devs by using Expo (RN) or Flutter (Needs Dart). The issue is as soon as you stray off the well laid path similar to the old create-react-app problems you have to choose "do things their way" or "Suffer all the problems you avoided with the framework + all the problems of the library you added". For example at work I help maintain a React-Native app that is one of the core parts of our business, We investigated Expo but we use sodium in the app for keypair generation and its not supported. So we can't have any of Expo's benefits because of one unsupported library. (its supported in iOS and Web but not Android...) * There are packages that implement sodium in expo but they score too poorly on their security scores for us to use them.