I'm designing an app that controls a connected object.
In one of the screens of the app, the user can activate or disable a nightlight and set the hours of lightning (e.g. 8pm - 7am).
In the first version, the app developers coded the screen so that the data is sent to the server only when the user has leaved the screen. Thus, if the user wants to switch on the nightlight immediately, he will have to leave the screen to see the nightlight switching on.
In my opinion, the user might think that the object is not correctly connected and that the parameters have not been saved.
What are the best practices for that type of usage? These are the options I was thinking of:
- Option currently coded: Saving data when user leaves the screen
- Option developers don't like for server consumption considerations: Saving data each time the user change a parameter in the screen (e.g. disable or change the hours)
- Adding a button to save the data