@burke, though I agree with the process of you’ve outlined (though would suggest not being so dev-centric), you’ve mentioned in your additional steps the need to find a React guru. I recognize our bias given we have invested a lot in Angular, but it’s not clear to me why React is the de facto framework of choice.
I think a bigger question to consider is the “glue” that the webapps will be using. We specifically chose angular because it’s a comprehensive framework. We have a single web application that widgets (written in angular) are imported into. I think this is an advantageous approach for reasons we can discuss on another forum. If we proceed using a model similar to OWA’s, which are essentially embedded within the java servlet/tomcat application, then it may make it either easier to be framework agnostic or perhaps react is more appropriate. I worry though that this firs step is not drawing the attention it deserves when considering the framework of choice.
It may seem like this is getting too much into the weeds but I believe this question of “glue” (I can’t think of a better term) needs to be addressed first before other work proceeds on building any applications. There are a lot of implications in terms of routing, state management, low level libraries to interact with the rest api, offline support, and many others which I believe need to be considered before embarking down a particular pathway. Migrating from an existing way of doing things to a new model will not be a straightforward process for any implementation.
I suppose that this group of key stake holders could meet first to decide these questions and then once a framework is settled upon and approach to design, we then look for an expert in that domain to help guide us along.
JJ