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

Implement Auto-Update UX for Composer Electron #2226

Closed
tonyanziano opened this issue Mar 10, 2020 · 13 comments
Closed

Implement Auto-Update UX for Composer Electron #2226

tonyanziano opened this issue Mar 10, 2020 · 13 comments
Assignees
Labels
R9 Release 9 - May 15th, 2020 Type: Electron

Comments

@tonyanziano
Copy link
Contributor

Work with @DesignPolice to implement in-app UX for automatic application updates.

@tonyanziano tonyanziano added the Needs-triage A new issue that require triage label Mar 10, 2020
@tonyanziano tonyanziano added R9 Release 9 - May 15th, 2020 Type: Electron labels Mar 10, 2020
@DesignPolice
Copy link

Sounds like fun, what are the requirements for this... Any ideas on the number of buttons or copy... or I can do some searching on others who have gone before us. @tonyanziano

@cwhitten cwhitten removed the Needs-triage A new issue that require triage label Mar 10, 2020
@DesignPolice DesignPolice removed their assignment Apr 2, 2020
@DesignPolice
Copy link

@sangwoohaan @tonyanziano @srinaath @cwhitten

Hey gentlemen, Marieke would like Sangwoo to take a pass at this before dropping it to me to verify the visuals we want to use -

Sang here are a couple of the screen grabs from Emulator that has a similar auto update, though there are some key differences.

Edu16_STEM_05
Picture1

@sangwoohaan
Copy link
Contributor

My two cents :
In the first screen where you select an option, it would make more sense if there were just two options (download and update manually / install and restart), and have 'Automatically download and update' as a checkbox option for the future.

@srinaath
Copy link
Contributor

srinaath commented Apr 6, 2020

I agree too @sangwoohaan especially until Composer becomes super stable and we get into a normal release cycle, we should not show the option for "Automatic Updates".

@tonyanziano
Copy link
Contributor Author

tonyanziano commented Apr 8, 2020

Here are some of the auto update lifecycle events we can key off of (points at which we can show / update the UI):

  • started checking for an update
  • update is available
  • update is not available
  • download progress has updated
  • update has been downloaded
  • encountered an error

@DesignPolice
Copy link

Might be worth exploring using the (Bell) notification option in the header? then start the modals - We don't currently use any of the User Log in or settings up there, but could be a familiar way to surface needs if people aren't using the autoupdate option.

Screen Shot 2020-04-08 at 11 20 45 AM

@sangwoohaan
Copy link
Contributor

The first draft
https://www.figma.com/file/LlTlh5vXwq91zjGnFtrUUR6l/Composer-master-design-spec-UI-library?node-id=1212%3A11996

@tonyanziano
Copy link
Contributor Author

tonyanziano commented Apr 16, 2020

@sangwoohaan do you happen to know the name of the icon in the app header? I can only find a similar icon with the direction of the arrow reversed on the Fabric / Fluent website:

image

If not, we could flip the icon horizontally.

@DesignPolice
Copy link

Hey Tony
I don't think it makes a big difference on the direction, but here is the icon.

Screen Shot 2020-04-16 at 11 57 28 AM

@DesignPolice
Copy link

https://www.iconcloud.design/home/FULL%20MDL2%20Assets/Fabric%20MDL2%20Assets/e81c

@tonyanziano
Copy link
Contributor Author

Sounds good! Thanks

@tonyanziano
Copy link
Contributor Author

tonyanziano commented Apr 17, 2020

@DesignPolice @sangwoohaan

Functionally, I believe this feature to be complete. Here's what I have:

Update available
update-available

Update available - popup minimized
update-available-minimized

Update failed
update-failed

Update progress - waiting for total
update-progress-1

Update progress
update-progress-2

Update succeeded - user chose install
update-succeeded-1

Update succeeded - user chose download manually
update-succeeded-2

Update unavailable
update-unavailable

I added an extra "Update unavailable" state for the future, when we add a button that will allow users to explicitly check for updates through maybe the app menu or some other piece of UI.

I also changed the copy on the progress bar from reading out the total in GB to MB, because our updates should never surpass the size of 1GB. If we do ever get to that point, we can switch over to GB.

@cwhitten
Copy link
Member

addressed via #2721

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R9 Release 9 - May 15th, 2020 Type: Electron
Projects
None yet
Development

No branches or pull requests

5 participants