Understand the problem
When it happens, who it affects and how to reproduce it. We check what is worth keeping.
An existing product doesn't always need a fresh start. I investigate the problem and propose what can be repaired while keeping the parts that work.
When it happens, who it affects and how to reproduce it. We check what is worth keeping.
Specify what we'll repair, what we won't touch and how we'll check the result.
Check the fix alongside related journeys. Hand over the changes and the known remaining limitations.
The initial review may show that a repair isn't economical. I'll explain that before proposing a larger build. I don't change a live system or its data without agreed permission.
The agreed code, your accounts and handover information. Before work starts, we also discuss third-party services and their separate costs.
We agree support scope and terms separately. Before committing, you'll know what the build price includes and what would cost extra.
My own projects demonstrate experience with iOS, data and user journeys. They are not separate client repair case studies.
EV1 Labs projects →Describe it in your own words. I'll read it and tell you whether I can help and what the next step would be.
I normally reply within one business day.