Also I don't believe in a strict discipline of 1 to 1 conversion, so I"m afraid that 6 months can stretch. The first "big bang" approach is problematic, because I won't be able to get management support for it.
If we develop a new feature - make it in Swift. "new code in Swift": state that all new code should be in Swift."routine": allocate 1 day of the week for this "duty", and do a top-down migration with well-defined boundaries."big bang": just hack-hack-hack for 6 months and produce a Swift app.So far I've been considering these approaches: If I start the project I want it to be finished within a reasonable timeframe (let's say 2 years). I'm trying to come up with a migration plan that is avoiding a situation where the app is a frankenstein of intertwined Swift/ObjC code without any clear rules or boundaries between the two.
In my rough estimation it would take about 6 man-months to rewrite the app from scratch (including testing). It was written by a small team (~3 people) during 3 years. The app is in Objective-C only with xib-s. What is the recommended approach to migrate an Objective-C codebase to Swift? I'm interested to compare different approaches and their pros and cons, what the development process should be and how architecture should look like.
0 kommentar(er)
