Managing React Native Maintenance: Tackling Developer Departures in Small Teams
A large company had only one in-house React Native developer. When he left, the app ground to a halt. No one in the company could handle the code. They called us, we took over the project, and brought it to the store submission stage. Nothing heroic. It's what we do.
Developer Departures: Challenges and Opportunities
The first thing we did wasn't to see what was missing—it was to understand what was already there and why it was written in that way. With a single developer who left without documentation, that phase tells you everything. The problem wasn't the code—it was that the entire project context existed in the mind of one person. When that person disappears, you don't just lose a developer: you lose the product memory.
We use React Native as the default for enterprise mobile projects. Not for convenience—but because eight times out of ten it's the right choice for those who need to maintain an app with a small team and evolving requirements. But it only works if there is someone who knows how to maintain it. We don't believe native and cross-platform are opposites. We believe a team that only knows how to do one or the other will eventually sell you that, regardless of what you actually need. We were there because we could do both.
Documentation and Code Practices
A client asked us how long it would take to understand someone else's code. We answered that it depended on how well-documented it was. It wasn't at all. We took double the expected time just for the analysis phase—and we told them this before signing.
Documentation is not just an optional, it's a necessity. Our experience indicates that lack of documentation can lead to increased costs and delays in software maintenance timelines. We believe that proper documentation facilitates smooth transitions and aids in comprehending complex code. Thus, we must consider investment in documentation as an integral part of building the project.
Tools and Collaborative Approaches
Submission to the stores isn't the difficult part. The difficult part is reaching submission with code that the next developer—whoever they may be—can understand without calling us every week. The adoption of tools like Git and version control systems can significantly assist. Moreover, regular team meetings for project status updates ensure that everyone is on the same page and knowledge is evenly distributed among team members. React Native allows for the use of the same code for iOS and Android platforms, reducing the amount of work compared to developing two separate native apps.