Ongoing
Angel One: fund addition and payments
Rebuilt Add Funds, integrated in-app payments, and reduced biometric authentication latency by about 500 ms.
- ~500 ms fasterBiometric authentication
Role dates and results are from my resume. These are contributions within the team's work; internal measurements and implementation details are not published here.
My contribution
- Rebuilt the Add Funds module using MVVM, Kotlin Flow, and Channels.
- Integrated 1 Click Pay so users could complete payments inside the app.
- Made help navigation remotely configurable and worked on service and analytics refactors.
- Reduced biometric authentication latency by roughly 500 ms.
Overview
At Angel One, I work on the Android fund-addition flow and related support, authentication, and analytics changes.
Problem
Fund addition needed fewer payment handoffs, easier support updates, and clearer state handling in the Android code.
Constraints
- Changes affected a live financial product.
- Support navigation needed updates without a new app release.
- Existing service and analytics integrations still needed to work.
Approach
- Moved the Add Funds implementation to MVVM with Flow and Channels.
- Integrated 1 Click Pay into the in-app payment journey.
- Separated help navigation updates from Android release cycles.
Implementation notes
Flow and Channels in Add Funds
Reasoning
The rebuilt module uses these Kotlin primitives for state and events.
Remote-configurable help navigation
Reasoning
Support routes can change without shipping a new Android binary.
Tech stack
- Kotlin
- Coroutines
- Flow
- Channels
- MVVM
- Android
Result and impact
Users gained an in-app payment option, and help navigation no longer depended on an app release.
Learnings
- A payment feature includes the support and authentication steps around it, not just the transaction.
- Separating configuration from code makes routine support changes easier to ship.