Awasum - my understanding is that Mifos is working now on a React App. (replacement?)
Regardless, I don't think we want to copy the Mifos *design* (neither React, nor Angular) because we aim to build our backoffice-UI as a generic demonstration concept, not one directly related to microfinance concepts. The idea is that Mifos targets and supports that specific industry and sector, while Fineract is more broadly defined. That design imperative should lead us to new interfaces and approaches. >From the moment that we decided to contribute the MifosX backend code to Finereact (2017), the concept was that Mifos would remain a key vendor in the Apache parlance and the Fineract project would have a broader set of uses that include, but are not limited to, financial inclusion or microfinance. We cannot copy the Mifos code; it's not Apache 2.0 license. Angular is a sound design choice in my view and commonly used across a number of financial industry users. Choosing it is a natural choice for our financial system. On Tue, Mar 10, 2026 at 6:33 AM Awasum Yannick <[email protected]> wrote: > Hello James, > > > If we going to do UI for Fineract, should we consider React with > typescript? > > 1. It prevents people from just copying code across from Mifos reference > app and causing confusion > > 2. React easier to learn and more market share than Angular > > What will be downside to using React instead? > > > > On Tue, 10 Mar 2026, 04:23 James Dailey (Jira), <[email protected]> wrote: > >> >> [ >> https://issues.apache.org/jira/browse/FINERACT-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> James Dailey updated FINERACT-2526: >> ----------------------------------- >> Summary: Fineract Backoffice Interface (POC) (was: Fineract >> Backoffice Interface POC) >> >> > Fineract Backoffice Interface (POC) >> > ----------------------------------- >> > >> > Key: FINERACT-2526 >> > URL: >> https://issues.apache.org/jira/browse/FINERACT-2526 >> > Project: Apache Fineract >> > Issue Type: Improvement >> > Components: fineract-backoffice >> > Reporter: James Dailey >> > Priority: Minor >> > Labels: gsoc2026 >> > >> > To enable a more comprehensive Fineract project, there will be a new >> administrative backend User Interface (UI) component. It will be a >> separate GitHub repository within the Apache Fineract project. >> > It will be aimed explaining the key functionality of fineract to devs >> and to act as the demo infrastructure. It will be aimed at being >> downloaded as part of the Docker container from the ASF, for example. >> > It should include, for the system user and dev, a page showing all of >> the APIs organized in a sensible way, and generated automatically at each >> build. >> > This back office component is NOT THE SAME as the end-user POC that is >> proposed in https://issues.apache.org/jira/browse/FINERACT-2440 >> > This does overlap partially with external open source projects that are >> offered under different licenses. However, this will be apache 2.0 >> license. >> > This project will use Angular. >> > This project should re-imagine the Fineract use cases in a way that is >> visually simple, distinct, and relates to the several user groups that we >> see in the project: Fintechs, embedded lending programs, non banking >> financial institutions (lenders), small banks, etc >> > Use cases will include, but not be limited to: >> > * login and select user type >> > * configure other users >> > * set up a new loan product >> > * disburse a loan >> > * create a savings account >> > * configure global variables >> > * run dashboards >> >> >> >> -- >> This message was sent by Atlassian Jira >> (v8.20.10#820010) >> >
