我认为自动化和便捷方法将始终涵盖常见案例，并且讲故事就是一个例子。便利性极大地简化并加速了开发过程。但是，总会出现这样的情况：在给定的异常情况下，这些方法无法满足您的所有需求。就像使用UI元素一样，并不能阻止开发人员在需要时使用核心图形，核心音频等。我认为，这绝对是iOS开发未来的一部分，但只是意识到这一部分将是一个障碍。所以不会意识到这一点。

I think the automated and convenience methods will always cover the "common" cases, and that story-boarding is an example of that. A convenience which greatly simplifies and accelerates the development process. However, there will always be cases where these methods do not provide you with all you need in a given, unusual situation. Just like using the UI elements does not stop developers from going under the hood with core graphics, core audio and so on when they need to. It is definitely, I think, a part of the future of iOS development, but only being aware of that part would be a handicap. So would not being aware of it.