<code>loadView()</code> is called once, when your view starts loading
<ul>
<li>Initialise and add views</li>
</ul>
<code>viewDidLoad()</code> is called once, when your view finishes loading
<ul>
<li>Not sure what you do here</li>
</ul>
<code>viewWillAppear()</code> is called every time you come back to your view
<ul>
<li>API calls to refresh data?</li>
</ul>
<code>viewDidAppear()</code> is called every time you come back to your view, called after <code>viewWillAppear()</code>
<ul>
<li>We put analytics tracking for page views here. We used to put them in <code>viewWillAppear</code>, but this was not reliable for some reason. Even though theoretically, it should be ok. Logically, it makes more sense to me anyway that you&#39;d only track an analytics page view after the view appeared, rather than in <code>viewWillAppear</code></li>
</ul>

`loadView()` is called once, when your view starts loading
* Initialise and add views


`viewDidLoad()` is called once, when your view finishes loading
* Not sure what you do here

`viewWillAppear()` is called every time you come back to your view
* API calls to refresh data?

`viewDidAppear()` is called every time you come back to your view, called after `viewWillAppear()`
* We put analytics tracking for page views here. We used to put them in `viewWillAppear`, but this was not reliable for some reason. Even though theoretically, it should be ok. Logically, it makes more sense to me anyway that you'd only track an analytics page view after the view appeared, rather than in `viewWillAppear`


View lifecycles

I'm an iOS developer, helping millennials with their finances through US neo-bank, Empower.
Before making the switch to development, I was a strategist and GM in the tech space.
