manoj.dev

Manoj Dvs, Senior Software Engineer

Hi, I'm Manoj.
I build software used by millions.

8+ years across native Android, Flutter, and the services behind them. Based in Bengaluru, India.

01 · About

A bit about me

📍 Bengaluru, India

💼 8 years shipping mobile

I have spent eight years building mobile applications, beginning in native Android with Java and Kotlin and moving into Flutter as the framework matured. That native grounding continues to inform how I approach performance, platform constraints and the parts of an application users never see.

My work spans both ends of a feature. I build the Flutter modules — Clean Architecture with BLoC and Riverpod — alongside the NestJS services, REST contracts and data models behind them. Owning the full path from interface to endpoint removes the coordination overhead that typically sits between mobile and backend teams.

Years shipping mobile
8+Years shipping mobile
Production releases
80+Production releases
Users reached
MillionsUsers reached
Mobile · Web · Backend
Full-stackMobile · Web · Backend

02 · Skills

Things I work with

Mobile

  • Flutter
  • Dart
  • Android
  • Kotlin
  • Java
  • iOS

Architecture & State

  • BLoC
  • Riverpod
  • GetX
  • Provider
  • Clean Architecture
  • MVVM
  • Modularization

Web

  • React
  • TypeScript
  • JavaScript
  • SPA architecture

Backend & Data

  • NestJS
  • Firebase
  • REST
  • GraphQL
  • gRPC
  • Node.js
  • SQLite
  • MongoDB
  • Hive

DevOps & Tooling

  • Docker
  • Fastlane
  • GitHub Actions
  • Codemagic
  • Bitrise
  • Sentry
  • Firebase Crashlytics
  • Kubernetes
  • Google Cloud
  • Bitbucket Pipelines

03 · Products

Things I've built

Digital banking, investments and travel in one app — now handling millions of transactions.

  • Core engineer from zero to launch, and still owning the platform years later.
  • Built biometric onboarding and real-time expense tracking end to end.
  • Modularised the codebase so feature teams could ship without waiting on each other.
FlutterBLoCRiverpodClean ArchitectureNestJS

Live music and podcast app, migrated from native Android to Flutter.

  • Led the bridge of existing Java/Kotlin functionality into Flutter during the move to cross-platform.
  • Built audio streaming for podcast content and a ticketing flow for live concert events.
FlutterKotlinJava

StatLedger BrewCollect

Supply-chain app for breweries, tracking inventory from the field.

  • Real-time, brand-level field data capture for stock moving through the chain.
  • Custom-charted dashboards surfacing collection and logistics metrics for operations.
Flutter

04 · Capabilities

What I own

6 areas I am accountable for end to end, not just contribute to.

Design systems
A centralised Flutter design system of 25+ components adopted by 5+ product teams, with standardised API response contracts — killing duplicated UI work and visual drift across the app.
Release engineering
Own the bi-weekly Android and iOS release train: 80+ production releases through GitHub Actions and Bitbucket Pipelines with staged rollouts.
Full-stack ownership
Ship the Flutter module and the NestJS service behind it — 10+ REST endpoints, data models, middleware and the contracts between them.
Performance
Cut cold-start time and removed visible jank on data-heavy screens by restructuring deep widget trees, adding image caching and moving blocking work off the UI thread.
Standards & mentoring
Set and enforce code review standards for a team of 6, mentoring on architecture, state management and testing.
Cross-functional delivery
Work with Product and Engineering leads to define technical roadmaps and API contracts, holding feature parity between mobile and web.

05 · Integrations

What I've integrated

Payments & money movement

  • Razorpay

    Custom-UI checkout on razorpay_flutter_customui — own payment-option surface, UPI collect requests and response handling, instead of the drop-in widget.

  • UPI

    Collect-request flow plus an installed-app picker for intent handoff, wired into add-money and recurring top-up journeys.

  • Autoload mandates

    Recurring account top-up over UPI collect — mandate setup, lifecycle screens and the failure states around them.

  • Transfers & deposits

    Fund transfer, add-money and fixed-deposit payment flows shipped across two retail banking apps.

Identity & onboarding

  • Karza

    Liveness authentication inside the video-KYC journey — auth model, repository layer and the retry paths when a check fails.

  • Video KYC

    VKYC onboarding and re-KYC end to end: agent-assisted webview, scheduling and settings sheets, link-not-sent and NESL retry flows.

  • Aadhaar

    Aadhaar capture through a dedicated in-house Flutter SDK consumed by the onboarding flow.

  • Document capture

    MRZ passport scanning and ML Kit barcode scanning for identity and card-linked journeys.

  • Instant onboarding

    Insta-onboarding and insta-card journeys — the shortened path from signup to a usable account.

Platform & tooling

  • Firebase

    Crashlytics for crash-free-rate tracking, Firestore driving remote static content and config, and Cloud Messaging for push delivery.

  • CleverTap

    Event instrumentation across the onboarding and add-money funnels.

  • Mixpanel

    Product analytics — funnel and retention tracking across feature journeys.

  • Sentry

    Error and performance monitoring, with issues triaged per release.

  • Freshchat

    In-app support entry points, including inside video KYC where drop-off is expensive.

  • Twilio

    Programmable SMS and voice for verification and transactional messaging in earlier consumer apps.

  • OneSignal

    Push notification delivery and audience segmentation across Android and iOS.

  • Modular architecture

    Feature work split across dozens of internal Flutter packages so teams ship independently of the host app.

06 · Craft

How I build

Performance is a feature

Cold start under 1.5s, jank-free scroll, memory that behaves after 30 minutes of use. These are not optimizations — they are requirements. I measure before and after every change that could touch them.

Offline-first, always

Networks fail. Users on 2G, on planes, in basements, in tunnels. I design for the sync engine first and the online path second — it forces cleaner boundaries between UI, cache, and remote.

Architecture that survives Year 2

Any pattern looks clean at week 1. I care about how a codebase reads after two years of features, three engineers rotating out, and one major refactor. Boring choices usually win.

Tests that catch real bugs

Widget and integration tests that mirror how users actually use the app. Golden tests for anything visual. Unit tests for logic that could rot silently. Skip the tests that only test the framework.

Ship deliberately

Feature flags, staged rollouts, crash-rate gates before promotion, and a runbook for the release. The exciting part of shipping is that nothing exciting happens.

Read the platform docs

Flutter, Android, iOS — the platform teams write the definitive answers. I go there first, then to StackOverflow, then to LLMs. In that order.

07 · Contact

Let's build something

Have an interesting mobile problem, or an idea worth building? Reach out — email is fastest.