Skip to content

About

I unblock mobile releases.

I am a Senior Mobile Engineer and Tech Lead. Most of the work I am called for looks the same from the outside: something is shipped, or about to ship, and it stopped.

Over 14+ years building and leading mobile products, I have worked across iOS, React Native, Android, backend and cloud — usually at the point where an engineering decision meets a release deadline.

The pattern I keep seeing is not a lack of talent. It is that a blocked release is a different problem from a feature backlog. It needs someone who can read a rejection message, a crash report or a signing configuration and say, with reasons, what the shortest safe path is.

So I productised that. Fixed scope, fixed price, written answer. You do not buy my calendar; you buy a decision you can act on.

How I work

  • I write the diagnosis down. If it is not in writing, it is not a deliverable.
  • I state confidence honestly. "Probable cause" means probable, not certain.
  • I scope implementation separately, so a diagnosis never turns into an open-ended project by accident.
  • I tell you when I am not the right person, before taking the work.

Working together

Describe the block in two or three lines — what you shipped, what stopped, and what you have already tried. That is enough for me to tell you which service fits, or that none does.