Not as part of 3.0.0 anymore, but perhaps for 3.1.0 or beyond, see below.
The main reason why Mekom wasn’t initially supportive of developing a new React form engine was precisely because there was one that already existed with many features and that had been used in production for years at AMPATH.
The second reason was that this seemed like focusing on extra work when we simply needed O3 to work, again at a time where an existing AMPATH form engine was readily available to be included in O3.
Of course React would have been nicer, there is no discussion about this, I’m not challenging this specific point.
Integrating AMPATH forms was also the proof that our microfrontends framework could be of use for seamlessly mixing all the React of O3 with another JS framework (Angular).
So we collectively decided to Carbonise AMPATH forms instead, which was a pretty low hanging fruit to grab to have a whole form engine ready to be used.
Mekom has no resources to address the decommissioning of AMPATH forms until we have a full 3.0.0 release of O3 out there (see Releasing O3 Ref App 3.0.0-beta). Then, at that point, we could help move this goal forward as part of an upcoming 3.1.0 or 3.2.0 if other consumers of AMPATH forms are also ready to support this effort (cc: @jesplana, @jdick, etc) and are on board as well.