Web applications
Dashboards, SaaS platforms, storefronts. Server-rendered, backed by a real database, with an admin panel that does not need me to operate it.
- Next.js & React
- REST / GraphQL
- Postgres & Prisma
- Admin panels
Web& AndroidDeveloper
I build web and Android applications, and hand them over documented enough that your team can keep going without me.
Mahmoud El-Aidy
Taking work for next month- 48+Shipped to production
- 6Years doing this
- 32Clients
- 5★Average rating
What I do
If your problem is not one of these, tell me anyway — I would rather point you somewhere else than take the job.
Android applications
Native Kotlin with Compose, or React Native when the budget calls for it. Offline-first, because the connection will drop and the app still has to work.
- Kotlin & Compose
- React Native
- Offline sync
- Play Store
Interfaces & design systems
Tokens, components, motion rules. So the tenth screen looks like it belongs with the first — including the screens you add after I am gone.
- Design tokens
- Component libraries
- Prototypes
- Accessibility
Fixing what exists
Inherited something that fights back? I read it, measure it, then fix what is actually costing you — not what happens to be easiest to fix.
- Performance audits
- Refactoring
- CI/CD
- Monitoring
Work
Each one includes the part that went wrong. That is usually the useful part.
Tools
Picked for the problems they solve, not for how they look on a CV.
Next.js, React, TypeScript, Kotlin, Jetpack Compose, React Native, Node.js, PostgreSQL, Prisma, Tailwind CSS, GSAP, Docker, Redis, Figma
How it goes
No retainer traps. Nothing starts before you have seen the price in writing.
- 01
A call
Thirty minutes. I ask about the problem and the people who have it. If I am the wrong person for it, this is where I say so.
- 02
Scope and price
Within two days you get what I will build, what I will not, a timeline, and one number. The number does not move unless the scope does.
- 03
Build, in the open
A staging link from week one. You watch it come together and redirect early, while changing direction still costs a conversation instead of money.
- 04
Handover
Deployment, docs, a walkthrough with your team, and thirty days of fixes on me. Then you own it completely.
Questions
I cannot answer that honestly before understanding the scope, and anyone who quotes you before that is guessing. After the call you get one fixed number in writing. If the scope does not change, neither does it.
A landing page: one to two weeks. A web application: six to twelve. An Android app: eight to sixteen. You get a dated milestone plan before anyone signs anything.
Yes, most of my work is remote. Calls in Arabic or English, whichever you think in. I overlap with European hours comfortably and US mornings with some effort.
You do, entirely, on final payment — repository, deployment setup, documentation. I do not host anything you cannot move, and I do not keep anything you would need to ask me for.
Good, that usually makes things faster. Send me the Figma file. I will build it as drawn, and flag anything that will cause problems in real use before I write it rather than after.
Thirty days of bug fixes are included. After that, either your team takes it — the documentation is written for exactly that — or I stay on monthly. I do not lock anyone into the second option.
Still reading?
Then we should probably talk. Thirty minutes, free, no slide deck. Worst case you leave with a second opinion.