Timeline for answer to Should I hide the multi-language selection button/menu if my app has only one language currently? by RobbyReindeer
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2018 at 12:47 | history | edited | RobbyReindeer | CC BY-SA 3.0 |
added 229 characters in body
|
| Mar 7, 2018 at 12:39 | comment | added | RobbyReindeer | It's like a loading screen. Users feel more comfortable when they know an operation is being carried out even if the feedback is distorted from reality. This we know! | |
| Mar 7, 2018 at 12:38 | comment | added | RobbyReindeer | @Luciano It's context sensitive. You could say yes it is better in a very general case where there is not a close connection between the software company and the users. But if his users are anticipating the feature already, from client-company rapport and feature requests, then it would be beneficial to provide a reassuring message that the feature is under development. | |
| Mar 7, 2018 at 11:53 | comment | added | Luciano | Wouldn't it be better to, instead, have (for example) a splash screen saying "new languages available" when they are actually available? If it's close to delivery sounds like a waste of time, if it's far it might create some anxiety... I feel like this type of progress should be communicated somewhere else (website / blog / twitter) | |
| Mar 7, 2018 at 10:56 | history | answered | RobbyReindeer | CC BY-SA 3.0 |