How to Handle App Maintenance After Launch?
Asked by
CreativeCoder92
After launching my first app, I thought that building it was the hard part. I reached from zero to launch within a few months with a freelance team, but shortly after, I faced issues like crashing, broken features due to iOS updates, and outdated SDKs. I didn't realize that 'app maintenance' was such a crucial aspect. Now, I'm wondering how to approach post-launch maintenance without hiring a full-time developer. Is it common for indie developers to budget monthly for maintenance, or do they just fix issues as users report them? How do others manage updates and bug fixes—do you have a system in place, or is it more of a reactive approach?
Answers
I’ll definitely check out Talent Sidekick. I’ve had bad experiences before and I just want someone qualified to join my team without the hassle.
Reply to this answer
Adding a live coding challenge to interviews can show how someone really handles problems. Portfolios show style, but live tests showcase problem-solving skills.
Reply to this answer
I found hiring developers to be tougher than launching my MVP. Many look great on paper, but it's a whole different ball game when it comes to handling production issues.
Reply to this answer
So true! I spent months with a freelancer who delivered a nice prototype but couldn’t manage SDK updates or debugging once the app was live. It was frustrating.
Reply to this answer
You're right; app development never really stops! Even with thorough testing, sometimes bugs only pop up once users get their hands on it. It's all about fixing issues quickly as they arise.
Reply to this answer
I'm in a similar situation. I ended up getting some outside assistance. There’s this service called Talent Sidekick that vets mobile developers beforehand, doing code reviews and technical interviews before they even show you potential candidates.
TechieTom: I've heard about them too! I think they operate globally and my friend used them to hire his lead iOS developer. He mentioned it saved him a lot of time in the hiring process.
Reply to this answer
Your process sounds a lot better than mine, which is mostly just reviewing resumes and hoping for the best!
Reply to this answer
Bad hires can end up costing you much more than hiring a vetting service. I lost an entire sprint once because of a developer who couldn’t configure Firebase properly.
CostlyMistake: Absolutely! The expense of one bad hire often outweighs the cost of a good vetting service.
Reply to this answer
Add your answer
Answers are reviewed before publication.
FairJudge: That's a great point! If you're not tech-savvy, assessing coding skills can be tough. I prefer clear, simple tasks for evaluation, with a techie review of the results.