Hello, I am Ziad Gamal
A mobile developer who believes
An app is judged
in its first minute
Launch speed, scroll smoothness, and what happens when the connection drops. Those three decide whether anyone opens it a second time.
One app for two platforms, without compromising the feel
I build in Flutter because it saves time and budget, then tune the platform-specific details by hand so the app never feels foreign on either one.
What Ziad owns inside a project
The gap between an app people keep and one they delete after a week shows up in details that never make it into the pitch deck.
Performance on mid-range hardware
He tests on phones three years old, because an app that runs smoothly there runs everywhere. The reverse is not true.
Defined behaviour offline
What stays usable when the connection drops, and what queues to send later. Networks fail in lifts and on the road — this is not an edge case.
Built for the store, not the demo
Icons, splash screen, permissions, store listings, update builds. Publishing is a stage with its own requirements, not a button at the end.
How Ziad builds an app
What is the least that makes the app worth having at launch? The rest ships in an update — an app that never launches learns nothing.
Screens, their relationships, and the path between them, before any interface detail.
Server connection, local storage, and sync once the connection returns.
Android and iOS, different screen sizes, and a deliberately throttled network. The simulator hides half the problems.
Submission to both stores, crash tracking after launch, and fixes for what real use surfaces.
Define the useful minimum
1What is the least that makes the app worth having at launch? The rest ships in an update — an app that never launches learns nothing.
Build structure and navigation
2Screens, their relationships, and the path between them, before any interface detail.
Wire the data
3Server connection, local storage, and sync once the connection returns.
Test on real devices
4Android and iOS, different screen sizes, and a deliberately throttled network. The simulator hides half the problems.
Publish and watch
5Submission to both stores, crash tracking after launch, and fixes for what real use surfaces.
When the project needs an app, not a site
Ziad fits when you need presence on both stores, push notifications, or the kind of repeat mobile use a website cannot cover.
Let’s build something precise, useful, and ready to grow.
Want to talk to the person who'd do the work?
Tell us what you are building, where it is stuck, and what the next step needs to achieve. You will get a straight answer about scope and sequence — and it will come from whoever would actually build it.