Understand the problem
Review the codebase, build setup and release process with your team. Reproduce the blockers and separate urgent defects from longer-term maintenance work.
An app doesn’t have to be beyond repair to need outside help. Perhaps every release is difficult, a handover has left gaps, or the next feature keeps getting buried under old problems. I help teams understand the code they have and make a practical plan for improving it.
For teams taking over an unfamiliar app, maintaining a Java codebase or struggling to make changes with confidence.
Review the codebase, build setup and release process with your team. Reproduce the blockers and separate urgent defects from longer-term maintenance work.
Agree which user journeys and failures matter most, then address them with focused implementation and appropriate regression checks.
Move Java code towards Kotlin, replace problematic dependencies or improve architecture around the features you are actually changing.
A focused review is a useful first step when the scope is unclear. We agree which parts to inspect, discuss the findings and prioritise the work. From there I can implement changes with your team or take on an agreed piece of the recovery work.
Modernizing an established Android app and its surrounding platform.
A connected coffee machine app, rebuilt across Android and iOS.
Android development guidance and architecture support.
Not automatically. Existing behaviour, release constraints and the cost of maintaining a replacement all matter. A targeted change may be the better starting point.
Yes. We can start with the repository, build instructions and known issues, identify the gaps and agree a manageable handover and implementation scope.
Yes. A review can be a standalone engagement. Its scope and expected outputs are agreed before work starts.
Tell me what the app does, what is blocking delivery and whether there is a deadline. Please leave credentials and customer data out of the initial email.