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 · SwiftAbout me
Founder.Engineer.Builder.
I'm Muhammad Aamir. For ten years I've been turning business ideas into software that ships. Today I run ETechViral, where my team builds mobile apps, AI products, and the automation that keeps businesses running.
- Mobile
- AI / ML
- Automation
- Full stack
- Founder
01The story
Ten years of shipping, not pitching.
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.
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. The automation work alone has roughly doubled the speed of the processes it touches across the enterprises we've worked with.
The part of the job I enjoy most is the translation work. Taking what a business is actually trying to do, sitting with the constraints, and shaping that into something real. I work across the stack on purpose. 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.
02What I build
Three categories. One team that owns the whole pipeline.
AI products
LLMs, 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 LearningAutomation
Process automation that takes manual work off people's plates. The work consistently delivers roughly 2x speedups across the workflows it touches.
Workflows · Integrations · OAuth03How I work
A few opinions I'd defend.
01
Most product decisions are scope decisions.
The 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.
02
The boring code carries the load.
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.
03
If you can't deploy it on a Friday, it isn't done.
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.
Want to talk?
Let's connect