In my experience, letting the client decide doesn't always work.
I've deployed many multi-AP, high throughout networks using MT products. Sometimes there are clear client side issues preventing an optional connection but these are usually solved with OS or driver updates.
However, client devices may connect to the 2.4 Ghz band even when they could have a faster connection to the 5 Ghz band. The only solution I've found to provide my clients is to turn of their wireless card off and back on--their device will invariably connect to the 5 Ghz band afterwards.
Many manufacturers offer ways to mitigate this problem...
In Ubiquity, one can manually adjust the beacon interval so that the client sees the 5 Ghz band first.
ASUS uses a technology they developed called SmartConnect:
*
https://www.asus.com/us/Networking/RTAC ... 87U-sec-05
*
http://www.smallnetbuilder.com/wireless ... ing-manual
And there are other examples...
These techniques aren't uncommon--I believe many manufacturers implement them because client devices can oftentimes be unreliable when deciding which band of a wireless network to connect to.
Back to my original statement, many of my clients notice very quickly when their devices aren't connecting at the higher speeds--the client devices are a mix of Mac and Windows, so I don't believe the problem to be platform specific. I've also noticed the same problem on my own Mac laptop at client sites (it will oftentimes connect to the 2.4 Ghz band, after turning its wireless off and back on, it will connect to the 5 Ghz band).
The short if it is that many manufacturers use techniques on the AP themselves to help "steer" clients to a better connection. I agree that it would be nice if MT offered a similar option.