Product engineerinterfaces -> release

Bring me a messy flow or a Figma with gaps. I’ll turn it into mobile-first software that feels clear when someone actually uses it.

Selected work

Work highlights.

Curated product work chosen for shipped proof, visual polish, and real workflow depth.

Proof stack

9+product buildsselected work
5+years buildingmobile products
iOS/Androiddeliverycross-platform
Remoteteamsworldwide

Practice

I stay close to my work.

I build, refine and take responsibility for the details.

Contribution graph
@TheNomadInOrbit
MonWedFriJunJulAugSepOctNovDecJanFebMarAprMay

How I work

I keep my work clear from idea to release.

Flutter is what I do best. I also care about structure, state, design details, copy, and getting the product ready.

01

Use case first

I check what the screen needs to solve. With Figma I follow it closely. Without it I help shape the flow.

02

Readable code

Architecture, state, folders, names, and boundaries matter. Version one should not make version two painful.

03

Details people feel

Motion, hierarchy, copy, spacing, loading, and empty states all count. That's where polish shows.

04

Flutter first, wider when needed

Most work is Flutter mobile. When needed I can also handle web, CMS, APIs, dashboards and desktop tools.

Testimonials

In their words.

Short notes from people I’ve worked with closely, included here as proof of how the work feels from the other side.

Load Ranger
Usman stepped in during a last-minute issue before a client meeting and helped steady the product when the team was under pressure. His speed, ownership, and execution made a real difference at exactly the right time.

Project Manager at Allied Technologies

Recognized in team chat

Behind the finish

The tools behind the work.

The tooling, languages and systems that move through the process and become products.

Personal builds

Work beyond Flutter.

Side projects across TypeScript, Apple platforms and smaller experiments that keep my skills sharp.

Glace VS Code theme showcase.
Developer toolingOngoing

VS Code theme

Glace

One-click theming with backup, restore, and host-aware styling.

TypeScriptVS Code API
Private extension
Vision MCP Server cover image.
AICompleted

AI tooling

Vision MCP Server

Tooling work shaped around utility and model-workflow ergonomics.

TypeScriptMCP

Contact

What are we building?

Reach out to connect or collaborate. Flutter is my main focus, but I’m open to product and web work when it fits.

Portrait of Usman.

Usman

Available

Building Quark Studio

Senior Flutter engineer.

FAQ

A few straight answers.

For people deciding whether we should work together.

Sixty years of experience sounds great..

I'd rather see sixty good decisions than sixty years on paper.

Time = where you worked, not how you think. Your work shows that.

I care about the thought process behind the screen: why this flow, why this state, why this detail nobody asked for.

Have you worked in this domain long to know what's good? Have you made mistakes to learn from?

AI speed helps.. it still cannot fake exposure.

Seeing your work and understanding how you think is more important. If your work makes sense without a lot of explanation that's more valuable than a number of years of experience.

Flutter product work. Especially when the idea is clear enough to care about, but not clear enough to build blindly.

New builds, messy flows, product decisions, screens that need thought before code.

I can improve an existing app too. I just like work where there is still room to shape the product properly.

Yes. You work with me directly.

No middle person. No one else is involved.

I do the work. I tell you what I did. I keep the process easy to follow.

If we need to make a decision about something, I will let you know right away.

Yes.

I do not like walking into a project loud. First I understand the current setup: how the code is shaped, how the team works, where the fragile parts are.

Then I start helping.

I work better when people are straightforward with me.

I like it when people tell me what is really going on.

Tell me the real problem. Tell me what cannot break.

Then give me room to work.

I will show progress. If something feels off, I will let you know away.

I do not need the whole "we are a family" speech.

Be fair with me. Take the work seriously. I can work with almost anyone.

Yes. Things change.

That is normal.

Just tell me early.

If the real requirement changed, we change the plan.

If it is just panic in the moment, I do not want to treat that like a new product direction.

I do not like guessing in the middle of a project. Tell me what changed and I will adjust.

You do.

When the project is finished, you keep the code, assets, notes, and anything else created for the work.

I do not hold work hostage.

Flutter is my main ground.

If the product needs it, I can work around it too: TypeScript, Next.js, Swift, APIs, dashboards, small tools.

I will not pretend every stack is my strongest one. Fit matters.