Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX Refactoring #103

Open
andreareginato opened this issue Aug 26, 2014 · 0 comments
Open

UX Refactoring #103

andreareginato opened this issue Aug 26, 2014 · 0 comments

Comments

@andreareginato
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant