Scaling iOS, a story of technical debt, and how to get through it

updated 9 months ago; latest suggestion 9 months ago

Context

The talk is centered around the experience of working on the same project for a long period of time, and dealing with change. Over the years, my team has been through a lot: we inherited an app from contractors, went through a rewrite, a fast growth of the team, layoffs... I'd like to talk about some of the things we learned along the way.

The talk

The talk will focus on two parts of the story: some decisions made during the rewrite and how we dealt with their long lasting impact.

We made a few technical choices early on that had unexpected impacts years later:

  • an external dependency
  • a storage layer
  • a testing framework

These choices not only taught us some valuable lessons, they also informed the team's strategy going forward, which is the second part of the talk: how we tailored the technical solution to the team's problems and targeted our refactorings to have the maximum impact.

Takeaway

You almost only hear about success stories at conferences, and I wanted to share something a little different. What happened to our app, and how we managed to evolve our architecture to deal with it. We've been in the app store for a while now, close to 8 years, and the app has is in the top 20. It's going to be interesting for the audience to hear what happens behind the scenes.

What I would like the audience to take away from this talk is that mistakes can and will happen; what matters most is how you deal with them once you've realized things went wrong.

Suggestions

  • The proposal author responds 9 months ago

    Hi,

    Thank you for the suggestion!

    You almost only hear about success stories at conferences, and I wanted to share something a little different. What happened to our app, and how we managed to evolve our architecture to deal with it.

    What I would like the audience to take away from this talk is that mistakes can and will happen; what matters most is how you deal with them once you've realized things went wrong.

    I'll update my proposal with an additional paragraph.

  • 8b2f2d3e6553c2b4048b93300959895ab76b4154?size=100x100 8b2f2d3e6553c2b4048b93300959895ab76b4154 suggests 10 months ago

    What do you expect attendees to take away from this talk?