@Octavian:
"The reason is logical. Since usability testing revealed that the feature confuses users it simply has to go."
You might want to learn some logic.
Since usability testing revealed that the feature confuses ***NEW*** users, and new users only, it simply must not be the default.
Try again.
@Octavian:
"The reason is logical. Since usability testing revealed that the feature confuses users it simply has to go."
You might want to learn some logic.
Since usability testing revealed that the feature confuses ***NEW*** users, and new users only, it simply must not be the default.
Try again.