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

Device UX Review #2427

Open
6 of 15 tasks
joepavitt opened this issue Jul 7, 2023 · 2 comments
Open
6 of 15 tasks

Device UX Review #2427

joepavitt opened this issue Jul 7, 2023 · 2 comments
Labels
area:frontend For any issues that require work in the frontend/UI epic A significant feature or piece of work that doesn't easily fit into a single release

Comments

@joepavitt
Copy link
Contributor

joepavitt commented Jul 7, 2023

Description

Having just done a UX Review on Devices I've flagged multiple areas of frustration and ideas for improvement that I'll be documenting here:

Setup Phase - Adding a Device

image

Tasks

  1. area:frontend size:XS - 1 task
    joepavitt
  2. area:frontend size:S - 2 task
  3. area:api area:frontend scope:device size:M - 3 story
  4. 1 of 1
    area:device size:XS - 1 task
    Steve-Mcl

Setup Phase - Download YML

image

Tasks

  1. area:frontend size:XS - 1 task
    joepavitt
  2. area:frontend size:XS - 1 task
    joepavitt
  3. 2 of 2
    area:device feature-request needs-triage
    Steve-Mcl

Setup Phase - Binding Device to Instance

This entire step feels very unintuitive. #2334 seeks to move the Devices to nest below Applications, rather than Instances, which would have some level of impact here as currently, to deploy a set of flows to a Device, you need to go via a Snapshot on an Instance first.

image

Tasks

  1. area:frontend size:M - 3 task
  2. area:frontend size:S - 2 task

Action Phase - Setting Target Snapshot

image

Tasks

Action Phase - Developing Flows on Device

Screenshot 2023-07-13 at 15 03 05

Tasks

  1. area:frontend size:M - 3
@joepavitt joepavitt added the epic A significant feature or piece of work that doesn't easily fit into a single release label Jul 7, 2023
@MarianRaphael MarianRaphael added this to the 1.11 milestone Aug 1, 2023
@MarianRaphael MarianRaphael added the area:frontend For any issues that require work in the frontend/UI label Aug 1, 2023
@MarianRaphael MarianRaphael removed this from the 1.11 milestone Sep 1, 2023
@MarianRaphael MarianRaphael added the in-progress Issue for the In-Progress section of the website roadmap label Jan 5, 2024
@GogoVega
Copy link

To filter devices, "type" is used but that doesn't give many options to filtering. Would adding a "room" option be useful?

I think I saw a request (yeah #723) to show a list of existing types, perfect.

I understand the reason for the "Last Known Status" (devices page) but visually I am missing a "Not Responding" flag which would allow me to filter these devices (?)

The device page where "Status" is listed is not correct, it is either "Last Know Status" or use the "Not Responding" flag.

@joepavitt
Copy link
Contributor Author

I am missing a "Not Responding" flag which would allow me to filter these devices (?)

You can click on the charts at the top of the Devices page, which show the last connected time, and you could filter to device last connected over 3 minutes ago (for example)

@MarianRaphael MarianRaphael removed the in-progress Issue for the In-Progress section of the website roadmap label Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:frontend For any issues that require work in the frontend/UI epic A significant feature or piece of work that doesn't easily fit into a single release
Projects
Status: Started
Development

No branches or pull requests

3 participants