Mobile apps
iOS and Android apps that feel native and ship from a single codebase. We drop into Kotlin or Swift when the platform actually needs it, not as a default.
Flutter · Dart · Kotlin · SwiftI'm Muhammad Aamir. For 10+ years I've turned business ideas into software that ships, 40+ apps and counting. Today I run ETechViral, an AI app development house of 30+ engineers, building AI-powered mobile and web products for founders who need to ship fast and scale.

I started writing software a decade ago, and most of what I've learned since has come from shipping things. Not prototypes, not slide decks. Real products, with real users, and the quiet responsibility of keeping them running. Forty-plus apps later, that's still the part that matters.
The work spans healthtech, SaaS, productivity, and creator platforms, from Finden, an AI workspace launched on Product Hunt, to DentaSmart and StressGuru, two AI health apps live on the stores. Along the way ETechViral grew into a team of 30+ engineers, and the work earned Top-Rated status on Upwork with clients across the US, UK, Germany, Switzerland, Australia, Sweden, and Turkey.
The pattern across the work I'm proudest of is the same. We sit with the problem long enough to actually understand it, build the smallest version that solves it, and refine until it earns its place in someone's daily workflow. I work across the stack on purpose, AI, mobile, web, and the cloud underneath. The best software almost always comes from one team that sees the whole picture, not five teams handing pieces over the wall.
The work nobody screenshots is the work that ships.
iOS and Android apps that feel native and ship from a single codebase. We drop into Kotlin or Swift when the platform actually needs it, not as a default.
Flutter · Dart · Kotlin · SwiftLLMs, vector search, custom models, and the glue between them. AI that solves a business problem, not just a demo on a tweet.
LLMs · Vector Search · CNNs · Transfer LearningFast, typed web products on Next.js and React, with Node.js APIs and the edge-deployed infrastructure to scale them. Built like real products, not landing pages.
Next.js · React · Node.js · TypeScriptThe hardest part of building isn't writing the code. It's deciding what to leave out. The features I'm proudest of are usually the ones we said no to.
Auth, sync, error handling, retries. The parts nobody screenshots are the parts users actually rely on. Get those right and the rest of the product survives its edge cases.
Real shippability includes monitoring, rollback, and a way to know when something breaks at 3am. A feature is finished when you can sleep through it, not when the code runs.