mobx-persist VS ordinary-puzzles-app

Yeah - there's a library that I typically use for this: https://github.com/pinqy520/mobx-persist

For example, if you’re using MobX, then mobx-persist (https://github.com/pinqy520/mobx-persist) is a good option. Redux and other state management libs will no doubt have their own options. The main benefit of these libraries is that you don’t have to manually serialise or de-serialise the data, and whenever the value changes in state, it’ll be persisted to storage.

Last, because you're supporting multiple platforms in a single directory, it's easy to end up with confusing indirections and branches in platform-specific files. This may be just a "me" thing, but I find it hard to navigate around configuration files of projects that support multiple platforms. At first glance, it may look like all platforms use the same configuration files. But once you dig a bit deeper, you realize that each platform requires some ad-hoc tweaks to the configuration files (for Metro, Babel, Webpack, etc.). Want an example from a codebase I wrote? Check out Ordinary Puzzles, which is a mobile, web, and Electron app. It's not easy to understand what files are used by which platform (e.g., what platform build phase is using babel.config.js?)

Can't say for sure. It's highly likely you'll need to make some changes to the metro bundle config when you update React-Native. But at least these changes should be less painful to deal with than having to mess with the native code (which you would do if you don't use nohoist). Personally, I prefer this approach to the known alternatives — which are not using a monorepo at all (which can get confusing as soon as you start supporting multiple platforms) or using a monorepo without nohoist. But it might be just a matter of preference 👍

I recently needed to wrap a React app generated with Create React App (CRA) with Electron (well, the app itself uses React Native for Web, but it doesn’t matter). My goal was to stay within the Create React App limits as much as possible (without ejecting). There’s no shortage of guides on how to do it online. Still, I couldn’t find one that fully follows the Electron security guidelines and provides a distribution setup using Electron-builder. So, here’s yet another tutorial on how to wrap an app built with Create React App in Electron — from the initial scaffolding up to the distribution workflow.

Ordinary Puzzles - Mobile and web puzzle game built with React-Native