2 ms·
I have a similar skillset to you and to be fair I've seen some pretty horrible React codebases in my time as well. You're correct though the architecture story
by jamil7 7y ago
I have a similar skillset to you and to be fair I've seen some pretty horrible React codebases in my time as well. You're correct though the architecture story is far behind on iOS, SwiftUI and Combine are attempts to address this and in my opinion they work really well. MVVM and Redux / Elm style architectures are really trivial to implement now. There is also a push for more functional approaches in general, if you look at videos from talk.objc.io or pointfree.co both of these focus on functional approaches to common architecture patterns. I hope that these recent developments from Apple are a signal of things to come in terms of providing better developer experience and insentives to use the platform's toolkit. To remain relevant I feel Apple has a huge amount of work to do in this area, documentation, XCode improvements and making SwiftUI a proper UIKit competitor (currently you will have to combine them for anything non-trivial).
- gregkerzhner 7y agoThanks for those examples. The kickstarter app is opensourced and seems to be a good example of the MVVM pattern - https://github.com/kickstarter/ios-oss/tree/master/Kickstarter-iOS https://github.com/kickstarter/ios-oss/tree/master/Kickstart... Ive been out of the iOS game for about two years and now getting back into it. Have you had luck convincing your organization to use SwiftUI? What have been the painpoints? I am finding that people on my team are pretty traditional, even hesitating to use autolayout, so pushing SwiftUI might be an uphill battle.