Please log in to watch this conference skillscast.
Apple’s iOS development platform was released over 10 years ago. Since then, significant changes have been made to the toolset and languages surrounding iOS app development. When a development platform reaches this age it is increasingly frequent that:
- • iOS engineers will encounter ‘legacy’ iOS apps (apps where the majority of architecture was built with outdated language, APIs and toolset references).
- • When encountering such apps, the challenges of working within the constraints imposed will be greater.
- • There will be a need to evaluate the value of continuing development of such a legacy app versus alternatives such as a rewrite.
This talk will be divided into 3 sections:
- • Review of common problems/patterns encountered in legacy iOS apps as well as the typical challenges those introduce to a refactor strategy.
- i.e. KVO, early/immature use of managed object context, etc.
- • Evaluating Refactor vs. Rewrite
- How to evaluate technical complexity of options.
- Risks associated with either strategy and how to weigh these based on you team or product.
- • Execution strategy & business buy-in
- Should be shaped around business success & flexibility.
- Metrics talk (and inform) - use metrics to reach your decision and track your progress through the strategy you choose.
YOU MAY ALSO LIKE:
Legacy iOS apps: Refactor vs. Rewrite
Julietta works as an iOS engineering consultant in Brooklyn, NY. She’s been building software applications for more than 12 years, first learning the ins-and-outs while working as a software consultant for Agile & TDD champion, ThoughtWorks. Since then she’s been an active member of the NYC startup scene, specializing in architecting iOS platforms for startups of all sizes and needs. She’s lead teams and is active in the entrepreneurial community and also runs the Brooklyn Swift Developers meetup.