Thank you for taking time and responding.

In programming it's said think before you code because you want to get the design right before your implementation. There are many good articles written on this topic just google them.

The article does not promote to dump everything inside a single file, my apologies if it gave that impression but as mentioned one should follow decomposition and separation of concern.

Swift is protocol driven and hence the language by default promotes abstract programming, so I see no harm in making sure good abstraction practices are being implemented.

ViewModel class conforms to the ObservableObject and then calls other layers like service or database and the View can listen to published properties inside the VM, isin't that the whole point of ObservableObject? I knew I should've drawn a diagram showing this

Lastly, I don't want to be on the pinnacle of clean coding, I am just a developer who wants to do the right thing.