NomadStyle

Day 84. App life cycle

Hey there! I've already learned about different stages of the view controller life cycle. The life cycle of an app is almost the same way.

𝐓𝐡𝐞 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐬𝐭𝐚𝐠𝐞𝐬 𝐨𝐟 𝐭𝐡𝐞 𝐚𝐩𝐩 𝐥𝐢𝐟𝐞 𝐜𝐲𝐜𝐥𝐞:

Not running🔴: The app hasn’t been launched or has been terminated.
Inactive🟡: The app is running in the foreground but isn’t receiving touch events.
Active🟢: The app is running in the foreground and receiving events.
Background🟠: The app is executing code but is not visible onscreen. When the user quits an app, the system moves the app to the background state briefly before suspending it.
Suspended🔴: The app is in memory but isn’t executing code.

We need to know the lifecycle of the app to execute code on time. For example, when the app launches, we could trigger a network call to fetch new data. When the app closes, we can save the user's progress.

Now I need to figure out how delegates work.😬

Day 71-72.𝐔𝐈. 𝐓𝐚𝐛 𝐁𝐚𝐫 𝐂𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫𝐬

Hi there! 🥰

A tab bar controller allows you to arrange your app according to distinct modes or sections. For example, the Clock app is divided into five modes: World Clock, Alarm, Bedtime, Stopwatch, and Timer.
A tab bar interface features a tab bar view, which runs along the bottom of the app’s screen. Each tab can contain its own independent navigation hierarchy, with the tab bar controller coordinating the navigation between the different view hierarchies.

𝐓𝐡𝐢𝐬 𝐝𝐚𝐲𝐬 𝐢 𝐥𝐞𝐚𝐫𝐧𝐞𝐝:
▫️How to appropriately use a tab bar controller
▫️How to add a tab bar controller
▫️How to add view controllers to the tab bar controller
▫️How to customize tab bar items

It seemed to me that switching between view controllers in this way is super convenient. But I'm not sure that in this case the view controllers can interact with each other🧐

Do you use tab bar controllers? What do you think about it?