> actually implemented in-depth testing beyond the anemic xcode support
I think this is the key motivator for people looking at alternative architectures. My guess is most people wouldn't stray very far from basic UIKIt/MVC if the established practices weren't so hard to unit test.
I see the experimentation with alternative approaches as the iOS community going through a phase of maturity, and is a positive signal. Many people in the community care deeply about issues of code quality and testability and while striving for simplicity. The increase in iOS architecture related articles is an indication of unrest and an active search for better practices. I suspect that it is only through these experiments that we will discover the balance we are looking for.
Similarly, I think articles like the OP are a healthy resistance against the pendulum swinging too far the other way. Although I agree with several points made I'm disappointed that testability isn't even mentioned and thus many points ring hollow.
I think this is the key motivator for people looking at alternative architectures. My guess is most people wouldn't stray very far from basic UIKIt/MVC if the established practices weren't so hard to unit test.
I see the experimentation with alternative approaches as the iOS community going through a phase of maturity, and is a positive signal. Many people in the community care deeply about issues of code quality and testability and while striving for simplicity. The increase in iOS architecture related articles is an indication of unrest and an active search for better practices. I suspect that it is only through these experiments that we will discover the balance we are looking for.
Similarly, I think articles like the OP are a healthy resistance against the pendulum swinging too far the other way. Although I agree with several points made I'm disappointed that testability isn't even mentioned and thus many points ring hollow.