Mentors

@Rajan Maurya @Chinmay Kulkarni @Shashank Priyadarshi

Length

Large - 350 hours

Category

Mobile - Android SDK | Kotlin Multiplatform

Overview & Objectives

The goal of this project is to migrate Android field officer kotlin multi-module application to Kotlin Multiplatform and rewrite network layer by adopting fineract-client-kmp-sdk, make all the network calls are working as expected. The Android client will be the first of the Mifos mobile apps which consume the SDK, reducing repeated network layer code in mobile apps, improving developer experience, and making it easier to migrate to newer versions of Apache Fineract 1.x and Student would work on designing offline sync functionality in background.

This year we are totally focusing on migrating to Kotlin Multiplatform, writing Unit and Instrumentation test and writing github actions to automate release process using fastlane.

Description

In 2025, The student will be working on implementing the following things:

1. Update the Android client to latest dependencies

2. Rewrite Network layer of Android client to consume fineract SDK using coroutines instead of RxJava implemented code.

3. Migrate kotlin multi-module codebase to Kotlin Multiplatform

4. Write appropiate unit and integration tests.

5. Update CI/CD to build APK and analyses code quality

6. Implemented Playstore release github action pipeline

7. Integrate google playstore API for better and faster release flow.

8. Update corresponding documentation for building the app.

Helpful Skills

Android, Kotlin Multiplatform, Kotlin, Jetpack compose, navigation-compose, MVVM, coroutines, Flow, multi-module architecture.

Impact

1. High performance using jetpack compose

2. Clean code and easy understandable code because of multi-module and coroutines implementation.

3. Kotlin Multiplatform support to build application for Android, IOS, Desktop, Web.

4. Overall stability by increased testing coverage through a more stable and error-free codebase.

5. Improved developer experience through faster build time.

6. More seamless release management and upstream contribution

7. Reduction of time to upgrade

Other Resources

QA & Testing - https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=195730042

2024 GSOC Final Report (Aditya Gupta): https://gist.github.com/Aditya-gupta99/f0bad77037ae76f32dddb933b6cb1c2a

Development Repository

https://github.com/openMF/android-client

Github

https://github.com/openMF/android-client

https://github.com/apache/fineract

https://github.com/openMF/fineract-client

https://github.com/openMF/fineract-android-sdk

Project Discussion

Slack: https://mifos.slack.com
Channel: #mifos-x-field-officer-app

Mentors

@Rajan Maurya @Avinash Vijayvargiya

Length

Large - 350 hours

Category

Mobile - Mifos X | Core Development

Overview & Objectives

2025 development will focus on refining our current Mobile Wallet to be a strong reference implementation of feature-rich and secure mobile wallet application for G2P use cases. While our mobile wallet is a powerful tool for all fintechs and financial institutions, we want to powerfully and simply demonstrate the ability for governments to disburse G2P Payments to highly functional mobile wallet and then be able to transact with that wallet by paying for bills, sending transfers, and paying for goods and services via merchants. We provide a reference mobile wallet application for consumers and merchants that has been developed by our Google Summer of Code interns from 2017 to 2024. The mobile wallet provides an extensible mobile wallet framework to support the basic use cases of a mobile wallet as documented in the Level One Project mobile wallet requirements. This extensible framework should support both merchant and client use cases as well as be capable of integrating with a Fineract back-end

Over time, we would like Mifos X to be more generically a wallet management system and this reference application is a powerful tool to support that. 

In 2025, we will also focus on enabling real-world merchant flows based on requirements from in-country users using the wallets for consumer to merachnt transactions.

Description

The initial mobile wallet framework along with 2 reference apps, PixieCollect and MifosPay, were developed in 2017. Later we decided to continue with MifosPay application only which as mentioned uses the mobile wallet framework.

In 2019, these functionalities were extended further by Shivansh including improving user experience and redesigning the app, support for Kotlin, integration with two Mojaloop transaction flows via the Paymeht Hub, adding improving Deeplinks, support for standing instructions and more well-rounded support for merchant transactions.

In 2020, Devansh Aggarwal further added complete support for standing instructions, integrated with Fineract CN for core use cases by mapping Fineract back-office APIs to Fineract CN APIs, added multi-theme support, completed integration with Payment Hub EE, added support for Hover, and converted Java code to Kotlin (in progress). For more details refer this

In 2021, Kinar Sharma, worked on developing a new multiplatform mobile wallet application using Kotlin multi-platform. This new application consumes FineractCN APIs and is built upon clean architecture. Kinar completed the data, domain and presentation layer (only for Android) for usecases available in FineractCN.

In 2022, Prashant Singh continued to evolve the app.

In 2023, Rachit focused on refining the architecture, streamlining the design and implementing some of the G2P use cases.

In 2024, Pratyush focused on migrating codebase from single module app into kotlin multi-module application by migrating xml to jetpack compose.

In 2025, we are targeting to make production-ready our cases for G2P, update dependencies, consume more uniformly our SDKs fix pending issues and introduce new features. Functional enhancements include:

• Integrate latest version of Payment Hub EE

• Integrate Mifos' notifications framework to provide support for usecases like merchant request to pay.

• Implemented Apple Store and Desktop apps release github action pipeline

• Update wallet framework to be make use of Mifos' Android SDK

• Improving the security framework to integrate more seamlessly with middlewares, API gateway, and identity management software

• Exploring proof of concept architecture or redesigns to align with movements like the Open Wallet Foundation.

• Write end to end Unit and Instrumentation test suite.

Helpful Skills

Android, Kotlin, Kotlin Multiplatform, Jetpack compose, Ktor, Room, Git

Impact

By providing an extensible mobile wallet framework, allow partners a complete reference stack of back and front-end applications to offer digital financial services to clients.

Development Repository

https://github.com/openMF/mobile-wallet

Other Resources

2024 Mobile Wallet Final Report (Pratyush Singh): https://gist.github.com/PratyushSingh07/6509549e64dbee0d695b98c6657a17b2 | Aditya Kumdale: https://gist.github.com/AdityaKumdale/83324009b2e676f8fbc623df4f953497

2023 Mobile Wallet Final Report: https://docs.google.com/document/d/1xHDVzmxuBj5KA0vHiJS_UGrs0Zb6IrpqwRmSdW3uExM/edit#heading=h.h4y8eq18ezr9

2020 Mobile Wallet Progress: https://gist.github.com/devansh-299/e2041c07d9ab55a747391951e9090df4

Mobile Wallet Framework: Source Code | Issue Tracker  | Slack

See https://openmf.github.io/mobile-wallet/

Project Discussion

Slack: https://mifos.slack.com
Channel: #mifos-pay

Mentors

@Aleksandar Vidakovic @Victor Romero

Length

Large - 350 hours

Category

Back-end Platform | Modules

Overview & Objectives

Users of Mifos have long had a need to have greater control and flexibility over creating loan and customer onboarding workflows that incorporate internal processes/steps as well processes involving external systems. This project would center around creating an external integration with a workflow engine such as Flowable or jBPM using the Mifos X REST API as the glue. The auto-generated client library from the back-end enforces the contract between the workflow engine and core banking system. The core banking and its REST API act as the glue. The result would be a UI-driven workflow engine to allow non-technical users to define these new custom workflows where they could drag and drop the different steps of the process. 

Description

Assumptions:

• BPMN should be adopted as a standard so which can make the workflow engine independent of the technology stack. 

• BPMN editors allow end users to sketch the workflow and generate a machine readable and executable output. 

• Workflow actions or business logic would be written in Java as part of Fineract so adapters will be need to be created on the workflow engine to execute actions on our side. 

• External processes would be sub-flows that could be used like lego bricks and included in the parent workflow context. 

Steps:

• Intern would select a workflow engine to integrate with and then build adapters to trigger and transfer fm BPMN form data into specific core banking back-office REST API calls. 

• Currently business logic such as creating a customer is triggered by an API call in Fineract. For this project, the intern would define a BPMN form with all the data that is needed which could be defined as a human task. Proceeding through each step triggers an adapter that transforms the generic BPMN form data into specific core banking back-office REST API calls

• Intern would go through the entire REST API building these adapters to trigger transformation of BPMN into core banking back-office REST API callsCurrently when creating a customer, API by API, the intern would define 

• Once all the calls in Mifos X have been transformed, the integration could provide for triggering any external  customer-specific action/workflow/API call/ system integration

Helpful Skills

Java, BPMN

Impact

UI-Driven interface based on BPMN standard to allow for non-technical users to define customer onboarding and application workflows via a drag and drop interface.

Development Repository

Other Resources

https://github.com/flowable

https://www.jbpm.org/

https://www.bpmn.org/

https://openfn.org

https://n8n.io

Project Discussion

Slack: https://mifos.slack.com
Channel: #gsoc-2025-idea-list

Mentors

@Aleksandar Vidakovic

Length

Large - 350 hours

Category

Front-End - Web

Overview & Objectives

This project would extend up on existing efforts to create a micro front-end approach for our UIs. As the userbase for Mifos/Fineract extends beyond just microfinance and financial inclusion we need to enable developers to easily build front-end user experiences that align with the wide variety of back-end use cases supported by our platform being used by MFIs, credit unions, banks, fintechs and governments. Additionally, many of the flow and screens used by staff as well as customers are common across mobile and web application.

Right now the look and feel and the overal UI development experience is very limited by using Angular and Material Design.

Description

This project would aim to build both the micro front-end framework and leverage a set of res-usable UI components that can be deployed as individual flows or end to end applications. Growing in popularity for its flexibility, ease of development, efficient performance, modular design is the ShadCN UI Library which contains unstyle components offering a higher degree of customizability.

The current standard UI for Mifos X is still the Web App which is the only one that covers 100% of the feature set. While based on Angular and more modern than our previous Community App, the project hard to maintain and - apart from the occasional color change - hard to customize let alone integrate in other web applications. Developers should be able to pick any number of standalone components and integrate them in custom UI projects (where Fineract is one among multiple backends). All Mifos X UI components should be published for easy consumption by other developers.

Intern would aim to replicate the current Web UI which is in Angular using the Material Design library using ShadCN components built on ReactJS.

This project would use the official typescript API client for Fineract.

Tooling should help with consistency and reduce handwritten code as much as possible. Using Monorepos is strongly suggested.

Helpful Skills

JavaScript, JSX , React, Tailwind CSS

Impact

Developers can more rapidly build out user interfaces for different financial service use cases with a greater degree of design flexibility in terms of customizability of the look and feel

Development Repository

https://github.com/openMF/web-app

Other Resources

• https://ui.shadcn.com/

• https://peerlist.io/blog/engineering/what-is-shadcn-and-why-you-should-use-it

• https://tailwindcss.com/

• https://www.radix-ui.com/

Project Discussion

Slack: https://mifos.slack.com
Channel: #web-app

Mentors

@Chinmay Kulkarni @Devansh Aggarwal @raul.sibaja@Rajan Maurya

Length

Large - 350 hours

Category

Mobile - Mifos X | Core Development | Infrastructure

Overview & Objectives

For 2025, our efforts this project will focus on delivering components that can be utilized as part of Compose Multiplatform and in conjunction with resuable components like ShadCN.

In 2022, Rahul Gill, created and completed the first iteration of our UI library for our mobile apps. Our suite of customer-facing mobile applications include our mobile wallet framework, and mobile banking apps for Fineract 1.x and Fineract CN. These are designed to serve as reference implementations for demonstration purposes but also to act as secure and robust starting dough that can be extended and enhanced and white-labeled.

With the move towards more digital financial services, these reference solutions are ever more important and critical and must appear highly polished, clean, and professional. We are working with a designer to provide a set of clean, consistent and professional UI designs and workflows to implement across our customer-facing apps.

This project would focus on implementing these new designs across the customer-facing apps providing a consistent and familiar look and feel. It will build off of efforts in 2020 and 2021 implementing the UI designs previously proposed during GCI. 

Across all our mobile apps, there are common screens and workflows with a lot of redundant and inconsistent design and development from scratch. The creation of a UI library of common shared components and design standards and guidelines would enable the following:

• Improve developer experience and ease of development

• Consistent look and feel of UIs for all apps

• Defined process for updating apps.

• Develop common UI library to ensure consistency of all apps

• Design guidelines, principles, and standards