Finding your way in the navigation of a complex iOS app can be quite complicated.
I know this from experience.
During many years of freelancing, I joined many projects at an advanced stage of development.
When you browse the classes in a project, there is a disconnect from what you see in code and what you see in the app.
And when you find a bug in some screen, how do you know in which class to look?
To solve the problem of visualizing the navigation flow of an app, Apple introduced the concept of storyboards in iOS development.
The Model-View-VievModel pattern has recently become of fashion in the iOS development community.
But it’s not without its controversies.
I, for one, I have my reservations about some of the implementations of MVVM. But I also think that some of its ideas are sound.
Networking nowadays is a requirement for most modern iOS apps.
This often takes the form of interfacing with a remote web service that provides data for an app.
And this web service is often a REST API that returns data in the JSON format.
But writing network code in Swift is not a simple task.
Making asynchronous network calls to get data from a remote API requires the interaction of many complex parts in an iOS app.
Table views are a fundamental piece of almost all iOS apps.
Still, most developers get them wrong, especially using Swift.
This happens in two different ways:
One of the places where most iOS developers make architecture mistakes is passing data between view controllers.
There are many ways to actually do this, but how do you know which ones are the best ones?
Many developers use the wrong solutions because they are quick and easy.
When I started freelancing a few years ago, things did not go well at the beginning.
I started freelancing at a moment in which I was not happy with my employer and I was looking for another job. Back then a friend told me that there was a lot of work freelancing as an iOS developer.
That was what convinced me to make the sudden jump. But it turned out to be quite different.
Many iOS developers seem to go for very complex storage solutions when iOS offers very quick and easy ones that are much better for many tasks.
I myself made such mistake in the past. When the iOS SDK first came out I decided to make a little game for the iPhone. It was a little card game and as such it had to store the values for each card as well as information about the deck and cards the player collected. And I used the worst solution possible.