> Doesn't Cook use an iPad Pro as his primary computer?
If he does, then he has a silent, unseen team of people who smooth over the rough edges for him. As a multinational megacorporation CEO who travels the world, I'm surprised he hasn't encountered the following oversights unless someone else is hitting these and silently behind the scenes working around them for him, instead of getting them fixed. In my mind's eye, he primarily interacts with his main device via voice to an assistant team and he uses the device mostly on a consumption as opposed to a content producing role (with the exception of email), and they run into these annoyances; those times that he directly interacts with the device to key in data, in my imagination he relies on that team to fix up inconsistencies or partial workarounds.
1. Key in a phone number, select a label; all the labels are in the order entered, not alphabetically sorted (or better, sorted by a user-customized sort).
2. Key in a calendar appointment, set a timezone; the timezone search never remembers previous timezones you selected, only displays the results of the search default, wasting the user's time to key in the timezone over and over again, and wasting all the screen space on whitespace. Breaks consistency with Calendar's Recents display of locations.
3. Contact information is based upon incorrect first-last name model; search on "Falsehoods Programmers Believe About Names" for all the incorrect assumptions Contacts embeds, for which users devise time-wasting workarounds.
4. In Calendar, setting Travel Time based upon Location still (on flagship iOS 10.2, iPhone 7, unlocked model) takes a very long time (sometimes as long as about a minute) instead of caching the previous 10-20 results, immediately displaying the travel time for them if any of the Location pairs' have a side that matches the currently selected Location, and filling in from the background as the search unobtrusively continues. Used to lock up Calendar and crash it about half of the time, but under 10.2 seems to return "Cannot Provide Directions: Network lost." error now with the same frequency. This happens because the feature depends upon a reliable network connection to function, and any disruption, poor latency, or just plain slow bandwidth seems to knock it off its feet instead of gracefully degrading to a best guess that is refined in the background with suitable visual cues and notifications.
5. No way to cut/copy and paste Calendar events.
6. Developers aren't invited in to build on top of Contacts and Calendar datastores to enhance with company-specific extensions. Instead, they must build the entire Contacts and Calendar user experience from scratch and try to replace it, or let users waste their time keying in that information into the Comments field.
There are lots of odd little omissions and oversights like these accreting over the years. Internal promotions at big organizations like this are not built on top of fixing these, so they are allowed to fester and gradually pollute the user experience until they become hygiene issues with the platform. A way to address this is a CEO-sponsored group who is charged with fixing these, and the members of the group are granted fast-track promotion status in exchange for addressing these issues. For Apple, this should be treated as an ongoing critical area to address, because it pierces their "Just Works" veil; the only way to keep up that customer stickiness for that sobriquet is superb attention to detail.