Developers and founders building React Native apps or Node.js backends. Most people come to me stuck on a build that will not compile, an app store rejection, an API falling over in production, or a decision about how to structure something before they build it.

I read your code with you rather than guess from a description. We find the real cause, I explain why it happened, and you leave knowing what to change. If the problem is architectural rather than a bug, I will say so instead of helping you patch around it.

I am a React Native and Node.js engineer and lead a small engineering team. I was lead engineer on Fate, a voice-first dating app live on the App Store and Google Play, covered by BBC, The Guardian, AP News, The Times and WIRED.

Yes. Store rejections are one of the most common things I get asked about. Send me the rejection message before the call and I will tell you what it actually means and what to change.

Yes. Store rejections are one of the most common things I get asked about. Send me the rejection message before the call and I will tell you what it actually means and what to change.

That is most of what I do. Metro and Gradle failures, native module linking, iOS signing and provisioning, and works-in-debug-fails-in-release. Bring the error output and we will work through it live.

Both, but I am most useful on the technical side: what to learn next, whether your project is good enough to show, and honest code review. I will tell you what is actually wrong rather than being encouraging about it.