Why you should be using React? Your app has exceeded the bare-minimum complexity to use a library to abstract view-management. You can write good, well-maintained, and easy to read code by using design patterns. The more design patterns you know, the faster you get there. React itself has its own design patterns too. You would be able to leverage these design patterns if you have a firm grasp of design patterns.
If cross-platform is the only concern then developing, a PWA is faster than building a native app. The performance boost you would receive by using a VDOM instead of DOM manipulations is insignificant if your codebase doesn't really take advantage of reconciliation.
Not trying to butcher your post, but sometimes you don't need React even for the reasons that you mentioned.
Why you should be using React? Your app has exceeded the bare-minimum complexity to use a library to abstract view-management. You can write good, well-maintained, and easy to read code by using design patterns. The more design patterns you know, the faster you get there. React itself has its own design patterns too. You would be able to leverage these design patterns if you have a firm grasp of design patterns.
If cross-platform is the only concern then developing, a PWA is faster than building a native app. The performance boost you would receive by using a VDOM instead of DOM manipulations is insignificant if your codebase doesn't really take advantage of reconciliation.
Not trying to butcher your post, but sometimes you don't need React even for the reasons that you mentioned.
Great points and thatβs the crux of being a good developer. Knowing when to pull out the right tools.