Mohammed Waheed
Experienced Flutter Developer · Full-stack mobile · Product & client delivery
Experienced Flutter Developer · Full-stack mobile · Product & client delivery
Same credentials · told like a build log, not a template
I am a computer scientist who spends most of his time where users actually press buttons: cross-platform Flutter, real clients, and products that have to work offline, online, and under pressure.
Clients rarely arrive with a perfect spec—they arrive with pressure, partial data, and a deadline. My job is to compress ambiguity into a roadmap, then into screens people trust. That is the “full-stack mobile” label, unpacked: ownership from requirement conversations to store-ready builds.
I have shipped inventory and wholesale flows, operations and logistics-style tools, wellness and engagement products, and experiments with ML and smart hardware stories on the client. The through-line is not one API—it is learning the domain until the software fits how people actually work.
Graduating with a bachelor’s in Computer Science gave me the spine—structures, systems thinking, and how machines fail when you push them. Years of shipping real apps gave me the muscle: Flutter, Dart, Java, Firebase, REST, Git, and the stubborn habit of testing on real devices instead of slides.
I still disappear into new stacks and docs the way other people disappear into playlists. If your problem is legal for software to solve, I want to hear the version that keeps you up at night—not the sanitized RFP paragraph.
Get in touchFacts at a glance
Stack lists look the same on every CV. What I build, and how I think, communicate, and ship alongside the code—including content, ideation, and running my own work like a small practice.
Build & ship
Flutter & Dart, iOS/Android releases, performance-aware UI, and polish that survives real devices—not only demos.
Feature boundaries, BLoC-style state, repositories, and structure that still makes sense when the product grows.
Firebase, REST APIs, auth and real-time patterns—comfortable collaborating from the client side with backend contracts.
Differentiators · business, content & execution
Turning vague goals into milestones, trade-offs, and backlog clarity—freelance work taught me to care about outcomes and constraints, not only tickets.
Short-form ideation, hooks and scripts, recording demos, and explaining technical work in a human voice—so products get seen, not only shipped.
Brainstorming product angles, narrative UX, and “what if we tried this?” prototypes before committing engineering time.
Owning delivery end-to-end, clear async updates, aligning with designers and clients, and being the person who closes the loop.
Planning around deadlines, prioritizing when multiple streams compete, and systems that keep freelance work predictable—not heroic crunch.
Material / M3, responsive & RTL layouts, motion with purpose; Git, VS Code, Android Studio, Figma—and knowing when design stops and shipped UI starts.
Tap any project card to open the full case study page.
Older experiments and practice apps—each has a short “progress snapshot” (Spark → Lesson → Trajectory) so you can see how I started, what stuck, and what I build toward now. Featured work is the headline; this tab is an honest growth chart for teams who care about trajectory, not only the latest repo.
Timeline
Switch views — featured is current focus; early holds older experiments.
Feel free to reach out to me through any of the following channels:
Egypt
Karakeep
Edu Nasser
Omica
National Veterinary System
Real Estate ERP System
Herafyyin
