I agree there shall be a choice of auto..or not to. But for majority of users opt for auto, they put their false hope on a spec/feature maybe you participated in drafting.
Enterprise space - autochannel is akin to herding cats, but perhaps that's also an opportunty - I know Cisco and Aruba have done a lot of work here, but as it stands, sometimes good, sometimes no so... problem there is that within their WLC's, there is a lot of legacy debt, and too many selections outside of auto-tune...
I think there is a great opportunity for someone in the consumer space to refine auto-channel selection - as it is, some work ok, some not so well...
Considering that many tablet/handset's these days, they do support channel/neighbor reporting from their perspective, this is something that could be good for all users - joe six-pack to prosumers to enthusiasts (given that reports could be provided there).
sidebar - One of the neat features of Apple's 802.11n builds - missing with their 802.11ac Airports - is that they would keep a channel list of all AP's within the BSS, which made passive discovery very handy, esp with the DFS/TPC channels* in the 5GHz band - and this was across Broadcom, Atheros, and Marvell - nice feature
*DFS/TPC channels - clients cannot actively probe against AP's there, those channels are all passive discovery which is why some tools won't find AP's there...
I have not seen this feature on any other consumer grade AP/Router... and clients outside of Mac/iOS benefit from that, as it's all standards based... combine this with what ASUS did on their AC1900 class AP's with QBSS load indications... One can find that with enterprise grade, but I think ASUS is the only one that deployed that standards based feature in consumer space...