Thanks for this article. though I need to poke some holes in it.

* this "architecture" isnt an architecture: every seasoned and experienced software architect will tell you, that an architecture need to be fully decoupled from the UI. Uncle Bob — who's "Clean Architecture" MVVM(-x) is claiming to implement — describes this as "The UI must be an I/O-Device". this isnt the case for your code. if you would rip out all swiftui stuff, nothing even close to resembling a working app would remain.

* also they would tell you, that an architecture let you defer making decisions, possibly for infinity. Using libraries like combine at the centre of our designs is the opposite of this.

* note, that Jim Lai has much more to say, please focus on the content, not the tone, as he says important things: https://medium.com/@swift2931/coordinatorviewmodelprotocol-is-the-idiocracy-of-swiftui-c88bc54600a7

that said I would like to invite you to read my article on "Khipu" which also implements Uncle Bob's "Clean Architecture" , but does not need to have coordinators, routers, view models… — it is boilerplate-code free: https://decodemeester.medium.com/khipu-rapid-and-sustainable-software-creation-in-swift-using-engineering-and-science-principles-312a933cce57?sk=8359f48cc06571e53de156db8cbc005c