@810ec5be Hey Chris, I'll probably have a long tail of questions/comments as I get back into the project that's using UIView views heavily... Here's the first ;)

Background question: what is the lifecycle of the coordinator? I always thought it was essentially tied to the life of the UIView, but I can't seem to confirm this with docs now that I check.

This is an interesting question because your example code sets `.parent` in `updateUIView` as if the coordinator may have changed... 

 @810ec5be nice! Will look at this a bit more closely over the weekend but those rules reflect my own experience. The devil is in the details 😂 I also love how you used a map wrapper as an example. It’s such a great illustration of the problems one often runs into. 

 @810ec5be Oh boy, yes please! I've had to reverse engineer so much because the docs are crap.

For example, when *exactly* is updateUIView called? Is it called every single time a property changes? And then YOU the developer need to try to figure out what specific binding(s) changed and then update your UIView accordingly? What if it isn't very well behaved in the presence of multiple updates in a short period?

And how do we know Apple won't change an undocumented behavior we rely on? ;) 

 @fc501b69 @9ed45d6a I think GPS has to mean Google Play Services here, not Global Positioning System. But yes I think like 2 versions ago they finally fixed *part* of the broken permissions model for location services lol.