2 more data density opinions:
1) Facilitating quick scans - I like, for example, seeing Estimated Time in my lists, a field which is now buried in the Inspector. In OF1 I could quickly scan a list of actions either to glean my Estimated Time information or to at least look for empty fields to fill, but now I have to click on every action to achieve this via the Inspector. This design seems to impede efficiency relative to OF1 in this case.
Maybe one option would be to let users select what fields show in the list window, so that people who, say, don't care about Estimated Time don't have to see it while people who do care about it can see it.
2) Check box target - The circle seems to be larger than it needs to be. I understand wanting to achieve greater design uniformity between iOS and Mac versions. This cuts down the learning curve from platform to platform, and, as fast as our phones are catching up to desktop-like benchmarks, in 5 years time our phones probably will be our main desktop computer (AirPlayed to a monitor and physical keyboard), so in anticipation of this rapidly approaching future this is another reason for design "merging." Yet, when design uniformity becomes an impediment (as with a click target that is the size of a touch target and thereby by its size needlessly hampers optimal data density) I think it should be reconsidered.
