Mobile banking app for fast and secure operations.
Mobile banking app PoC / 3-month engagement / 5-person team
About the project
MoBank is a PoC of a mobile banking application for our European customer. It’s a one-stop location for all user’s money needs - from checking balance and transferring money to trading stocks. One of its core features is the ability to buy and sell shares directly through the banking app without the necessity to create an additional account. Users see the latest market news in real-time to make better investment decisions.
Users can use mobile application to scan QR code and login without passing login/password pair in the web application.
We detect suspicious logins and transactions based on various parameters collected over the time of usage.
We provide users with an ability to confirm their actions through mobile application.
System testing tool
In order to test application load we have built a custom tool to generate stock market data.
Trade on the go
All the core features from the web application are available in the mobile app.
Real time charts
We display stock prices on a real-time chart updated every second.
To ensure users understand their cash flow we provide them with convenient dashboards to display basic statistics.
We secure transactions data by encrypting sensitive data at rest as well as in transit.
UI / UX Design
Frontend: React / Redux / Sagas / Tailwind
Backend: NodeJS / Express / RabbitMQ
DB: Postgres / Sequelize / MongoDB / Mongoose
CI/CD: Docker / GCP
1 QA engineer
The solution architecture
Radical Efficiency illustrations
Mobile app with Flutter
Choosing Flutter allowed us to build a high-performant cross-platform app without having to write a different codebase for iOS and Android. This, in turn, helped us to significantly reduce expenses on human resources as we didn't need to establish differently iOS and Android development teams.
We used the GCP App Engine service and Docker to deploy our application. This allowed us to see the first results quickly right after the first week of the app development. The process was performed by one of the developers and didn't require dedicated DevOps engagement at that moment.