EdT
macrumors 68020
What I want would take several years, but I wish they would start:
- An OS (every device) that is stable from day one. There may need to be improvements but it shouldn’t crash your device frequently OR repeatedly. Old functons should work and new ones shouldn’t be death traps.
- For similar software options especially across different hardware invoking/using that feature should be similar from device to device.
- If it ain’t broke quit fixing it. Quit changing how and where things need to be turned on or off or setup. Leave the name and procedure alone unless NOT changing it is more confusing than changing it is. If you are trying to find how to turn a setting or feature on or off or set an option and you do an online search you will frequently be given an old and useless answer because the top search answer is based on an OS that may only be a year or two old but where and how it is used has changed.
- In the official Apple help forums don’t rely on user votes to determine top or accurate answers. Because of item 3 above a spot-on accurate answer one year can be useless when the options are changed or the parent location where you set the options/preferences for it is moved. If a forum post or FAQ is outdated name what OS it is still valid and what and when that has changed.
- Consistent naming. If a feature is called something in commercials or other Apple correspondence and definitely in support documentation then make sure it’s called the exact same thing everywhere-ads, online help, FAQ’s, videos, EVERYWHERE. If a feature is renamed then help searches Using the old name should find the new documents and highlight both the new name and the old one and implicitly say this method and name replaces the previous one in a new OS.