Platform thinking
I design the shell, the shared libraries and the boundaries, so each team owns its module and nobody waits on a single release train. At Intermex that meant 5+ microfrontends deploying on their own.
Hi! I'm Madhukumar. For 11 years I've built web platforms and mobile apps that teams can ship on their own schedule, for fintech, industrial safety, cold chain, gov-tech and ports.
I split big frontends so every team can ship on its own, and make them faster while I'm there.
I'm a senior frontend architect in Hyderabad with more than 11 years of building web platforms and mobile apps that real people use every day, from truck drivers in container yards to finance teams moving money across borders.
I started in 2014 writing native Android and iOS apps for port operations. That turned into hybrid mobile with Cordova, then Ionic and Capacitor, then large Angular platforms. Most recently I designed the microfrontend platform behind a cross-border payments product, where four teams now ship on their own schedules.
Teams tell me I'm the person who asks "what happens when the network drops?" before anyone else does. I like mentoring, I like boring, reliable releases, and I've built an AI-assisted delivery pipeline that does the repetitive parts of a ticket while a human still checks every commit.
Tools like ChatGPT, GitHub Copilot and Claude Code have become a natural extension of my workflow. I use them to explore approaches, write tests and handle boilerplate faster, then review every line myself, so the speed goes up without the quality going down.
I also work across the stack with React and Node.js, plus Express and MongoDB, so I can own a feature from the API to the last pixel.
If any of that sounds like what your team needs, let's talk.
Plenty of developers can build the screen. What I add is the part around it: the architecture that lets teams move, the numbers that prove it worked, and the problems I catch before they reach production.
I design the shell, the shared libraries and the boundaries, so each team owns its module and nobody waits on a single release train. At Intermex that meant 5+ microfrontends deploying on their own.
Duplicate API calls, flaky auth on SSR, the screen that breaks offline. I look for these in planning and code review, so they never become a production incident.
I baseline first and report the result after: 40–60% fewer redundant API calls, 30–40% faster first load, 60% faster sign-in. If it isn't measured, I don't claim it.
I've shipped native, hybrid and web. When your product has both an Angular portal and an Ionic app, you get one person who understands both, and one shared design for state, auth and offline.
Most of my work is frontend architecture and hybrid mobile: Angular platforms that scale across teams, and Ionic apps that keep working when the signal doesn't. I also work with React and the Node.js back end. Tap a skill to see where I am with it.
Levels are my own honest self-assessment, not test scores.
A close look at your Angular codebase, build and runtime before you commit to a rewrite or a migration.
I join your team as frontend architect and build the platform hands-on with your developers.
Senior architecture help without a full-time hire, for teams that need their platform kept healthy.
I set up a guardrailed AI coding pipeline that works from your board, with a human check before anything is committed. I built it and run it on a real fintech codebase.
Architect of the Intermex cross-border payments platform: Nx + Module Federation microfrontends, Angular 20 SSR and a shared state, auth and API layer used by every team.
Built the SensiWatch mobile app from scratch for field teams in 10+ countries, with biometric sign-in, live trip maps and push alerts for trip events.
Built the Accela mobile app from scratch in Ionic 5 + Angular, replacing the native map with ArcGIS JavaScript maps.
Built the offline-first Marine Ops & Pilotage app for port pilots, and rebuilt the RDT Web portal (used by 30 terminals worldwide) from .NET into Angular 8.
Built hybrid mobile apps for container yards, including Mobile Gate for truck entry passes, delivered for TCS as the client.
Started on Android and iOS apps for ports: truck appointment booking (VBS) and real-time yard truck tracking (ITV) for Adani Ports.
Four payment domains (Wires, Checks, BillPay, Top-ups) needed to ship independently without duplicating data calls or slowing the first load.
Safety tours, observations, corrective actions, QR asset scanning and digital assessments for industrial workgroups on the plant floor.
Companion app to the SensiWatch Platform, giving field teams in 10+ countries live shipment and sensor visibility on their phones.
A mobile app for Accela built from scratch, where the map had to be fast and reusable across features.
Job assignments and marine-operations information for port pilots, who lose connectivity for long stretches.
A business portal rebuilt from a standalone .NET application into a web app.
Entry passes for trucks picking up or dropping off containers at yard locations.
Hauliers create, move and cancel truck appointments for port access, used by port communities around the world.
Real-time truck tracking in the container yard, telling drivers where to go and which container to carry or drop.
Seven agents take a ticket from Azure Boards through plan, code, test, review and fix, using file-based handoffs. Used on a real fintech codebase.
Searches live listings, scores each one against a skill profile, and keeps an approval queue with drafted cover letters.
Plain HTML, CSS and JS, with working demos of three patterns I use in production. Try them below.
On login, Wires, Checks and BillPay all ask for the same profile and beneficiaries. Fire the burst with the optimisations on and off, and compare network calls.
Remotes normally load when a user first opens a tab. Preloading after login fetches them in the background, so the first click opens instantly.
session: logged out
Features roll out by environment and user role without a redeploy. Change the context and see which UI the user gets.
Often not. If one team owns the app, a well-structured Nx monorepo with lazy loading is usually enough. Microfrontends pay off when several teams need to release on their own schedules. The audit tells you which fits.
Yes. I work in your repo, your board (Jira or Azure DevOps) and your CI, follow your review process, and pair with your developers.
Yes. I've worked with every Angular version from 4 to 20 and moved hybrid apps from Cordova to Capacitor. Upgrades go in steps, behind tests, without a big-bang rewrite.
Yes. I've shipped React in production and work with Node.js, Express and MongoDB, so I can cover full MEAN-stack features. For back-end-heavy projects I'll tell you upfront where I'm strongest.
Yes. Ionic and Capacitor apps for Android and iOS, including offline-first sync, biometrics and store releases. Most of my career started there.
The audit is a fixed fee. Builds are a monthly rate, and the retainer is a set number of hours per month. You get a written quote after a free 30-minute call.
Have a project, a migration that keeps slipping, or an app that needs to work offline? Tell me what's on your mind. I reply within one working day.
Based in Hyderabad, India · local time --:-- IST · working with US, UK and India teams