Triage

Before a single line of new code is written, our technical architects perform a detailed analysis of the current codebase. We identify, prioritize, and document the discovered issues. Based on the available budget and timeline, we formulate a solution to address the most pressing issues first.

Reuse / Rebuild / Refactor

Reuse/Rebuild/Refactor

Armed with a clear path of success, we get to work on improving your app. We start by adding tests to pin down pieces of functionality we want to keep and explore areas that need more understanding, or exercise different code paths. With those guard rails in place, we move forward, building a clean, scalable, and structurally sound architecture. Whether we’re rebuilding sections of the app or refactoring existing code, the end goal is a firm foundation for continued development.

Ship

As experts dedicated to mobile we move fast without sacrificing quality. As soon as we’ve completed the crucial fix, we ship to the App Store and Google Play to get the app back into your customers’ hands.

What we hand back to your team is a clean, sustainable, scalable codebase ready for future improvements.

We detected trouble in Care Innovations’s existing codebase. We refactored, building safer, more stable code and a better foundation for their next project. READ THE FULL STORY
We detected trouble in Care Innovations’s existing codebase. We
refactored, building safer, more stable code and a better
foundation for their next project. READ THE FULL STORY

MEET OUR RESCUE TEAM

BRANT DEBOW

Chief Technology Officer

“We were handed an app with zero analytics that needed a seasonal UI makeover. It had almost no documentation other than code. I had to jump in, figure out where everything was and then build in the analytics to tie into their backend. I enjoy the forensic puzzle aspect of rescue projects. Sure, they are not clean and they need a lot of work. But they can be interesting to untangle and you can really see the improvements as you’re making changes.”

AARON HAYMAN

Senior Mobile Engineer

“No software can be written so well as to never need refactoring. Requirements change, the project grows, and perfectly suitable architecture becomes outdated. The better part of being a developer is learning how to take a project in whatever form and make it better. Sometimes that does require a full rewrite but in my experience, those are rare. More often, I find myself taking the system that’s there and improving it as I go along.”

MATT NEUBURG

Senior Mobile Engineer

“Change is inevitable - whether a business is prepared for it or not. Case in point, I recently had to step into an iOS project where a key developer had to drop out. You could see the stress in his code, and some of the compromises he had to make. I found my deep platform knowledge especially helpful in this circumstance because I could divine the code’s intent while still assessing the gap between aspiration and implementation.”

JOSH BRAUN

Director of Engineering

“Rescues are like mini-excavations. You’re almost always trying to piece together why certain decisions were made, and there are always hidden constraints - sometimes from the business unit, sometimes from the domain, sometimes from the tech. But they have to be uncovered. I love the feeling of taking a system that isn’t functioning and righting it, or taking one that needs significant refactoring and reorganizing it to become whole.”

DAN COLEMAN

Senior Mobile Engineer

“When a codebase gets really gnarly, developers often want to shout "rewrite!" But rewriting from scratch is risky, and stressful to the business. The real challenge, and real value, is in fixing the ship while it's still out at sea. Refactoring is an art. It's amazing to finish the last of dozens of small changes, add them all up, and suddenly realize you've totally reworked an area. All without ever missing a scheduled delivery.”

NIK LILLAND

Senior Mobile Engineer

“I was once given a codebase that had been neglected for years. While the temptation to rewrite it was strong I had to put down the axe and pick up the scalpel. Wrapped up in the old, "messy" code were critical pieces I had to document before I refactored. In the end I was able to confidently update the existing code without losing previous developers’ work. The key to code rescues is to respect the work that came before you, no matter the mess.”

BRANT DEBOW

Chief Technology Officer

“We were handed an app with zero analytics that needed a seasonal UI makeover. It had almost no documentation other than code. I had to jump in, figure out where everything was and then build in the analytics to tie into their backend. I enjoy the forensic puzzle aspect of rescue projects. Sure, they are not clean and they need a lot of work. But they can be interesting to untangle and you can really see the improvements as you’re making changes.”

JOSH BRAUN

Director of Engineering

“Rescues are like mini-excavations. You’re almost always trying to piece together why certain decisions were made, and there are always hidden constraints - sometimes from the business unit, sometimes from the domain, sometimes from the tech. But they have to be uncovered. I love the feeling of taking a system that isn’t functioning and righting it, or taking one that needs significant refactoring and reorganizing it to become whole.”

AARON HAYMAN

Senior Mobile Engineer

“No software can be written so well as to never need refactoring. Requirements change, the project grows, and perfectly suitable architecture becomes outdated. The better part of being a developer is learning how to take a project in whatever form and make it better. Sometimes that does require a full rewrite but in my experience, those are rare. More often, I find myself taking the system that’s there and improving it as I go along.”

DAN COLEMAN

Senior Mobile Engineer

“When a codebase gets really gnarly, developers often want to shout "rewrite!" But rewriting from scratch is risky, and stressful to the business. The real challenge, and real value, is in fixing the ship while it's still out at sea. Refactoring is an art. It's amazing to finish the last of dozens of small changes, add them all up, and suddenly realize you've totally reworked an area. All without ever missing a scheduled delivery.”

MATT NEUBURG

Senior Mobile Engineer

“Change is inevitable - whether a business is prepared for it or not. Case in point, I recently had to step into an iOS project where a key developer had to drop out. You could see the stress in his code, and some of the compromises he had to make. I found my deep platform knowledge especially helpful in this circumstance because I could divine the code’s intent while still assessing the gap between aspiration and implementation.”

NIK LILLAND

Senior Mobile Engineer

“I was once given a codebase that had been neglected for years. While the temptation to rewrite it was strong I had to put down the axe and pick up the scalpel. Wrapped up in the old, "messy" code were critical pieces I had to document before I refactored. In the end I was able to confidently update the existing code without losing previous developers’ work. The key to code rescues is to respect the work that came before you, no matter the mess.”

Schedule a Call Today

Many of our projects are rehabs. Regardless of the reason, we understand the urgency and know what’s at stake. Our team does what it takes to refactor your iOS/Android apps, reduce technical debt and get your app into production quickly.