Mentors

@Chinmay Kulkarni @Shashank Priyadarshi

Length

Large - 350 hours

Category

Mobile - Android SDK | Core Development

Overview & Objectives

The goal of this project is to upgrade our Android field officer application to its latest dependencies and to rewrite the application to consume the recently developed Android SDK written using coroutines. 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 as well as student would be working on migrating xml to jetpack compose to support multi-module MVVM architecture and adding new features with jetpack compose.
This year we are totally focused on migrating to Jetpack compose and support KMP (Kotlin Multi-Platform)

Description

In 2024, 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 SDK using coroutines instead of RxJava implemented code.

3. Migrate xml implemented features to jetpack compose

4. Implement multi-module MVVM

5. Add kotlin multi-platform support.

6. Write appropiate unit and integration tests.

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

8. Implemented Playstore release github action pipeline

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

10. Update corresponding documentation for building the app.

Helpful Skills

Android, 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. Overall stability by increased testing coverage through a more stable and error-free codebase.

4. Improved developer experience through faster build time.

5. More seamless release management and upstream contribution

6. Reduction of time to upgrade

Other Resources

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

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

Mentors

@Aleksandar Vidakovic

Length

Large - 350 hours

Category

Platform | Core Development | Infrastructure

Overview & Objectives

In 2023 we have made substantial progress in implementing a baseline of behavior-driven tests across the platform using the Cucumber framework. The goal of this project is to expand unit testing coverage across the Fineract platform. Currently most of our automated testing is only through integration tests which take a long time to run and aren’t consistent. Cucumber is being implemented as the unit test framework and this project would focus on converting existing integration tests to unit test and writing new unit tests.

Goals are to increase testing coverage of core modules, reduce run-time at build of completing tests, and implementing some automated reporting to show testing coverage.

Description

The student will be working on implementing the following things:

1. Collaborate with mentor to implement Cucumber framework

2. Collaborate with mentor to implement test containers

3. Refine test data set and scripts

4. Convert high priority integration tests to unit tests

5. Write unit tests for key functional modules

6. Implement reporting to show test coverage.

Helpful Skills

Cucumber, Java, Spring

Impact

1. More frequent & higher quality releases

2. Improved developer experience and ease of submitting pull requests.

Other Resources

Github

https://github.com/apache/fineract

Mentors

@Rajan Maurya @Avinash Vijayvargiya

Length

Large - 350 hours

Category

Mobile - Mifos X | Core Development

Overview & Objectives

2024 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 2023. 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. 

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, 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.

• Incorporate Mifos' new design library

• Migrate xml to Jetpack compose

• Basic implementation of multi-platform

• Implemented Playstore release github action pipeline

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

• Complete migration of Java code to Kotlin

• 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.
  
  

Helpful Skills

Android development, Java, Kotlin, Jetpack compose, Rest, SQL, 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.

Other Resources

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 | Gitter Chatroom | Slack

See https://openmf.github.io/mobileapps.github.io/

Mentors

@Aleksandar Vidakovic @Victor Romero

Length

Large - 350 hours

Category

Fineract Platform | Modules

Overview & Objectives

Users of Mifos and Fineract 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 Fineract REST API as the glue. The Fineract Client library enforces the contract between the workflow engine and Fineract. Fineract Client and its REST API 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 form BPMN form data into specific Fineract 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 Fineract REST API calls

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

• Once all the calls in Fineract 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.

Other Resources

https://github.com/flowable

https://www.jbpm.org/

https://www.bpmn.org/

Mentors

@Chinmay Kulkarni @Devansh Aggarwal @raul.sibaja

Length

Large - 350 hours

Category

Mobile - Mifos X | Core Development | Infrastructure

Overview & Objectives

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

• Could potentially be a valuable upstream project in and of itself to create mobile fintech apps

Description

In 2024, With leadership of our mentors, this project would focus on building on the initial shared components of the UI library based off of the common screens and workflows identified across the various mobile apps. These common flows will be broken down into their-base-level elements and components.
If time permits, these common components could be tested and consumed by building out the UI screens for our reference open banking fintech app using this library.

Design enhancements to customer-facing apps include: 

• Break down common workflows into base-level components

• Refine and update design standards and guidelines

• Create and set up repository to house elements, components, and designs using jetpack compose.

• Design core ui component for our fintech app using jetpack compose.

• Develop and create base-level elements and components accoring to UI design standards and guidelines

• Implement screens and workflows to test out on reference open banking fintech app

• Documentation to ensure how to use UI library and update mobile app when UI library is updated.

Helpful Skills

Android Development, Kotlin, Java, Jetpack Compose, XML, Git

Impact

A clean and simple UI is key for our low-tech audience and professional and consistent look and feel enhances credibility of our stack. 

Other Resources

Recap on 2022 GSOC Project from Rahul Gill: https://gist.github.com/rahul-gill/6700c366627a2c7007a07b96ff6c0785

https://mifosforge.jira.com/wiki/spaces/MIFOSX/pages/3013476363

2020 UI Enhancements: https://gist.github.com/ShivangiSingh17/67b6041387c1e281caa7df23347f549e

Mobile Wallet Framework: Source Code | Issue Tracker | Gitter Chatroom

Mifos Mobile - Android Mobile Banking App: Source Code | Issue Tracker | Gitter Chatroom

See https://openmf.github.io/mobileapps.github.io/

Mentors

Tom Daly

Length

Large - 350 hours

Category

Platform | DevOps | Payment Hub EE

Overview & Objectives

The goal of this project is to improve the deployability of key projects of our stack like Mifos/Fineract and Payment Hub EE.

Kubernetes operators give kubernetes application dev/ops a great deal of reliability and architectural control over kubernetes applications deployments. Reference https://kubernetes.io/docs/concepts/extend-kubernetes/operator/ for details on the benefits of Kubernetes operators. The benefits of Kubernetes operators can also be quite tangible and visibile by looking at those under development from peer projects in the financial inclusion space like Mojaloop vNext whom are building out a Kubernetes operator as a means to improve quality, simplify deployment, and improve reliability and testing.

Description

This project would focus first on gathering the learnings around Kubernetes operators and their patterns. There are many good examples in existence to follow (i.e. Mongo, Kafka, etc). This learning around the design would compose 30% of the project. The next and major focus of the project would be to choose what to move from what’s currently only in Helm to an Operator. Likely there will still remain a small helm chart simply to deploy the operator.

Helpful Skills

Docker, Kubernetes, Jenkins, Bash, Java - Spring, PostgreSQL, MariaDB, Cassandra, TDD With JUnit 4, Gradle

Impact

DevOps and Sys Admins running our projects would experience a more simplified deployment with greater degree of control, improved quality of their builds and greater reliability and ease of testing.

Other Resources

• https://kubernetes.io/docs/concepts/extend-kubernetes/operator/  

• Mojaloop vNext Operator