Recovering a mobile app project built by an overseas team

Situation

All Nation Security was developing a mobile app with an external development team based in India. The app was critical to their operations and needed to support field reporting, communication workflows, and internal coordination.

The project had been in development for some time, and progress appeared steady based on updates.

Problem

Despite regular updates, there were growing concerns:

• The app did not feel as advanced as expected
• Communication gaps made it difficult to understand real progress
• There was uncertainty around code quality and long-term maintainability
• Timezone differences slowed down coordination and decision-making

The core question became: should they continue with the current team or change direction?

What I reviewed

• The current state of the application
• The structure and quality of the implementation
• How progress had been evolving over time
• What would be required to continue vs transition

What I found

The application had usable components and could serve as a base. However:

• Continuing with the same team would likely introduce more friction
• Coordination challenges were slowing down meaningful progress
• Execution quality needed tighter alignment with the company's expectations

The issue was not that everything had to be rebuilt — but that execution and coordination were limiting the project.

What changed

• Continued from the existing codebase rather than restarting
• Transitioned execution to a team working in a compatible timezone
• Improved visibility and alignment during development

Result

The company:

• Avoided restarting the project from scratch
• Reduced communication friction significantly
• Regained better control over execution and delivery

The project moved forward with clearer structure and improved delivery confidence.