You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to make a deep thought about the device component visual presentation. Here we highlight some of the key features that must be taken in consideration from the users feedbacks.
Handle the "start" action (when you send a request) and the "end" action (when you receive a response) to give a better feedback to the user. Right now for the "start" and the "end" action we make a basic animation of the status.
The user has the instint of clicking the properties.
Settings should be split in different sections (info, privates, connection).
Think about the sensor visualization. Right now when there is a sensor (no status and no functions) we hide some parts of the component and this can be misleading as the visual structure changes for the final user.
Think about handling the missing statuses.
Full study of all animations.
A better way to understand the properties that has been updated.
A visual solution to understand if the device is connected, not connected, simulating, etc.
... add yours
Think about having a chat with Ale and Gian about all of those topics.
The text was updated successfully, but these errors were encountered:
We need to make a deep thought about the device component visual presentation. Here we highlight some of the key features that must be taken in consideration from the users feedbacks.
Think about having a chat with Ale and Gian about all of those topics.
The text was updated successfully, but these errors were encountered: