12 ms·

Problem is that they never informed users that they’d changed this behavior. That button no longer does what it’s always done, which violates the Principle if L

Problem is that they never informed users that they’d changed this behavior. That button no longer does what it’s always done, which violates the Principle if Least Surprise: https://en.m.wikipedia.org/wiki/Principle_of_least_astonishment https://en.m.wikipedia.org/wiki/Principle_of_least_astonishm....

jamesrcole 9y ago
I imagine it will be documented in the iOS 11 changes - I mean, as I understand it, it hasn't been publicly released yet. There's a balance to be made between least surprise and the benefits of being able to evolve a design. (Another factor with any OS is there's a constant stream of new users coming to it for the first time)
- tradesmanhelix 9y ago
  > I mean, as I understand it, it hasn't been publicly released yet. Not sure what you mean by this. iOS 11 was released on 09-19-2017, so not sure what you're saying is still awaiting a public release? Regarding your second point, definitely agreed. However, to me this seems almost beyond the scope of Least Surprise and more akin to the Windows 10 fiasco where clicking the red X close button actually accepted the update and installed Windows 10. [1] Bottom line: there are certain established UI conventions (i.e., an on/off button turns things on and off) that you really can't change without causing a lot of issues and user frustration. And if you do change them, please alert your users. Otherwise, it seems shady and is definitely a UX faux pas. [1] http://bgr.com/2016/05/25/microsoft-windows-10-upgrade-trick/ http://bgr.com/2016/05/25/microsoft-windows-10-upgrade-trick...
  - jamesrcole 9y ago
    >> I mean, as I understand it, it hasn't been publicly released yet. > Not sure what you mean by this. iOS 11 was released on 09-19-2017, so not sure what you're saying is still awaiting a public release? I meant that I thought it hadn't but wasn't sure -- I haven't been following it closely.

jamesrcole 9y ago

I imagine it will be documented in the iOS 11 changes - I mean, as I understand it, it hasn't been publicly released yet. There's a balance to be made between least surprise and the benefits of being able to evolve a design. (Another factor with any OS is there's a constant stream of new users coming to it for the first time)

tradesmanhelix 9y ago
> I mean, as I understand it, it hasn't been publicly released yet. Not sure what you mean by this. iOS 11 was released on 09-19-2017, so not sure what you're saying is still awaiting a public release? Regarding your second point, definitely agreed. However, to me this seems almost beyond the scope of Least Surprise and more akin to the Windows 10 fiasco where clicking the red X close button actually accepted the update and installed Windows 10. [1] Bottom line: there are certain established UI conventions (i.e., an on/off button turns things on and off) that you really can't change without causing a lot of issues and user frustration. And if you do change them, please alert your users. Otherwise, it seems shady and is definitely a UX faux pas. [1] http://bgr.com/2016/05/25/microsoft-windows-10-upgrade-trick/ http://bgr.com/2016/05/25/microsoft-windows-10-upgrade-trick...
- jamesrcole 9y ago
  >> I mean, as I understand it, it hasn't been publicly released yet. > Not sure what you mean by this. iOS 11 was released on 09-19-2017, so not sure what you're saying is still awaiting a public release? I meant that I thought it hadn't but wasn't sure -- I haven't been following it closely.