Just don't get into the car industry's habit of many features that are distracting and most drivers do not want and have to turn off every time they start the car.
Maybe Innuos should consider that any "new" feature has a default of "OFF" yet explain much clearer in each Release Notes what the "New features" are, how they function and importantly how to turn them "On" if the user wishes.It’
It’s exactly this isn’t it.
Every time Mrs. H. starts her car she has to remember to turn off the feature which beeps at her every time she crosses a white line as well as two other features. She’s currently researching a new car from the same manufacturer and one of her first questions was about that specific software and whether this functionality has been recognised as needing to be reversed. If not, then she will be buying a new car from the company whose software doesn’t do that.
This position might also save many users finding their unit is "misbehaving" and starting "Help" threads when there is no need, would save time of @Dan and @Stephen having to reply to "ghost" faults which appears to be increasing in number.
This is an excellent point and one I’m sure will be noted by Innuos. The fact there were people on here asking why their device was suddenly playing music they’d not selected tells you both that people may do the updates but they don’t necessarily pore over the release notes
and that the approach of “off by default” is the sensible business decision. When new features are off by default but loads of people start threads on “Why doesn’t Sense have x?” when it actually does, then of course I’d be willing to reconsider my position.
@iSP I’m not clear why you think your post ends this thread? Your points are all valid but the discussion we’re having right now is not about whether the likes of Smart Q are good features - they’re good for some and not so for others - it’s about whether they should be enabled by default. There is, I think, a sensible grown up discussion to be had around the pros and cons of that but the likes of
@frank7036 seem to think this is the sort of forum where being unpleasant is okay and confrontation is okay. Thus the passive aggressive laughing or liking of posts rather than engagement in the substantive point. His point seems to be the simplistic “I like it therefore it should be on by default and the fact you (me) don’t like it means it should be off by default.”: Misses my point by a country mile. Whether I like a news feature is nothing to the point. It’s about good practice. Good practice is off by default.
Sidebar but an interesting point. I’m a beta tester for the iOS app for a well known UK national newspaper with international editions. I have repeatedly fed back on whether new features were good or bad. It varies hugely. I have consistently fed back that they should be off by default. The development team agree but one developer in there absolutely does not. I win each battle for off by default but then that specific developer moves onto a new feature and a beta update appears which enables that one by default instead. It’s been like playing whack-a-mole. Eventually I wrote to the lead developer and pointed out that they appeared to have no overarching ethos on such things. They do now. The developer who refused to comply and kept on turning on
his new features by default has been moved on.