![]() Reading those blogs, I was convinced of this myself. On top of that, most iOS developers thought that in Objective-C we wrote better code. I followed all the “best practices” of the MVC pattern, so I expected the reviewers to recognize the brilliance of my code.īut the verdict was different than I expected.Īlthough the code base was solid and the app worked well, the conclusion was that my code was:įor starters, unit testing was not widespread at the time in iOS, so who cared about testing? Xcode did not have any support for it, and you had to use mocking frameworks like OCMock. So my final code had to go through a third-party review before the app went live.Įven though at the time I had only three years of experience in making iOS apps, I felt quite confident in my abilities. And, since it was a banking app, it needed extra security features.īanks are very risk-averse businesses, and rightly so since they manage people’s money. Instead of the classic REST API returning JSON, I had to work with SOAP API and parse XML data. It was a quite complicated app, with many screens, charts, and interactive features. One of these was an investment bank in Amsterdam that wanted an iPad app to allow clients to browse their portfolios. Years ago, in 2011, I worked for an agency that made apps for big clients. What happens when you blindly follow iOS app architecture “best practices.” ![]() This will highlight the five problems an architectural pattern needs to address. In this section, I will analyze in detail the most popular iOS design patterns: MVC, MVVM, and VIPER.īut I will look at them from a point of view that I rarely see discussed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |