I’ve been suggesting:
– either plan to write Obj-C-y Swift
– or budget extra time in feature dev for sometimes migrating or writing adapters
Conversation
Replying to
If you write ObjC-y Swift incrementally, seems to work best starting top of stack down: little ObjC dependency on new Swift.
1
2
(The goal being to adopt more pure-Swift conventions once the full stack is in Swift and there aren't interop concerns.)
Replying to
we went all Swift using only some ObjC pods, but I ended up writing ObjC-y Swift adapters so ObjC code could call our Swift
1