DESIGN/VISUALS: Launch Experience - Flesh out additional design gaps

[bdellasc]

Open Issues

Misc Issues

• [ ] Resolve open questions to Dev (as of 2 April)

  • [ ] OSO Select Target Environment screen: Dev Comment: User needs to select a cluster they've provisioned. UX Question: Is this something they would do during the OAuth experience, or before that?

  • [ ] OSO Authorize Git Provider: Dev Comment: We didn't have an "Organization" dropdown for launch, but I guess we could add it. UX Question: Do you mean that you don't have that capability in the launch experience, or that you're expecting a "organization" dropdown here? If it is the later - organizations are shown in the location dropdown, along with user's repo area.

  • [ ] OSIO Import Create Application Screen: Dev Comment: underscores are invalid characters. UX Question: Are the requirements different between Launcher and OSIO for this?

  • [x] OSIO Import Summary Screen: Dev Comment: Do we need to check if any application with same name already exists? UX Question: In cases where they rename the application here, we'd probably need to run the same validation as the beginning of the flow. Can this be checked on that initial screen where the user names the application? Erik's answer: "there is a validation endpoint"

  • [x] OSIO Import Summary Screen: Dev Question: What are the default values provided for application name, maven artifact, group ID, version? Do we need validation on client side? Cat tagged Erik on the thread. Erik's answer: "these values used to come from the backend that is true, as they are just example values they could just as well be generated from the front-end values used where: groupId: io.openshift.booster artifactId: booster + missionId + runtimeId version: 1.0.0-SNAPSHOT and for node, we didn't display the groupId and made the version 1.0.0 and re-named the artifactId field "Name"

  • [ ] OSO/OSIO Navigate Away From Status Screen Mid-Process: Dev Comment: The way it has been build now closing the browser or navigation away will not stop the process it will only stop you from monitoring the progress UX Question: If the user navigates away and there is an error during the processes, can the user get back to this status screen to see what happened and remedy the problem? If they cannot, what kind of mess will they need to deal with if this happens?

• [x] #888 Update mockups for Create space overlay

  • [x] Design 1/2 - #813 Create Space
  • [x] Copy
  • [x] Design 2/2 - (updating copy)

• [x] #912 "Import application" flow gaps ???

  • [x] Design - Laura's Wireframes
  • [x] Design draft
  • [x] Copy
  • [x] Design (updating copy)
  • [x] Cancel completely out of launch experience
  • [x] Design 1/2
  • [x] Copy
  • [x] Design 2/2 (updating design & copy in larger InVision flow)

Overall Consistency of Language/Voice in the Launch Experience

• [x] We have a lot of placeholder text throughout the design. We should start filling that out with real info (where available). Stacy created a document for the main Launch Experience flow

Update Launcher Experience InVision Mockups for Analytics Team reference

• [x] Discuss which updates to apply to the InVision Flow mockup based on testing
• [x] Update full InVision Flow mockups based on discussion & these stories + more to potentially come out of discussion
  • [x] Create Application Overlay
    • [x] #889 Create Application Overlay (will be added to larger Invision flow later)
      • [x] Copy
      • [x] Design (updating copy)
      • [x] Design (add to larger InVision flow)
    • [x] #896 Update Mockups for Create application screen - Launch vs. OSIO
    • [x] Launch scenario (Part of the larger InVision flow)
      • [x] Copy
      • [x] Design (updating copy)
      • [ ] Design (add to larger InVision flow)
    • [x] OSIO
      • [x] Copy
      • [x] Design (updating copy)
  • [x] Runtimes & Missions panel
    • [x] #860 Launch Experience UI Copy - Runtimes & Mission
      • [x] Copy
      • [x] Design (updating copy)
      • [x] Design (add to larger InVision flow)
    • [x] #905 Additional inline text in mission and runtime selection boxes
      • [x] Copy
      • [x] Design (updating copy)
      • [x] Design (add to larger InVision flow)
    • [x] #901 Rework Row Label visuals
    • [x] #900 Prerequisite Tag
      • [x] Copy
      • [x] Design (updating copy)
      • [x] Design (add to larger InVision flow)
    • [x] #902 Contribute Tag
      • [x] Copy
      • [x] Design (updating copy)
      • [x] Design (add to larger InVision flow)
  • [x] Select Target Environment panel
    • [x] #862 Launch Experience - Select Target Environment
      • [x] Copy
      • [x] Design (updating copy in larger InVision flow)
  • [x] Github panel
    • [x] Copy
    • [x] #903 Github panel, rework with new content [did draft as part of import flow)
    • [x] Design (add to larger InVision flow with copy updates)
  • [x] **Pipelines panel
    • [x] Copy
    • [x] Design (updating copy)
  • [x] Set Up Status Screen
    • [x] Set Up Error Scenario - Launch & OSIO
      • [x] Design 1/2 - #913 Status Screen for Create Application (will be added to larger Invision flow later)
      • [x] Copy - story TBD
      • [x] Design 2/2 - (updating copy)
    • [x] Cancel Set Up Scenarios - Launch & OSIO
      • [x] Design 1/3 - #913 Status Screen for Create Application (will be added to larger Invision flow later)
      • [x] Copy - story TBD
      • [x] Design 2/3 - (updating copy)
      • [x] Design 3/3 - (add to larger InVision flow)
  • [x] #863 Launch Experience UI Copy - Additional Content
    • [x] Copy
    • [x] Design - (updating copy, adding to larger InVision flow)
• [x] Upload new mockups to InVision

Closed Issues

• [x] #895 Mockup Updates for round 1 & 2 testing

1. Canceling out of experience:

• [x] from initial application naming screen
• [x] from scrolling UI itself

2. Left bar behavior:

• [x] If user returns to a completed section, and makes a change that affects subsequent sections in some way, what happens? For example, if the user changes the working method from "Download ZIP" to "Code Locally, Build and Deploy Online", what happens to the left bar? Any warnings triggered before the change takes effect? Do sections just get cleared without warning?
  • [x] Spoke with @dlabrecq RE: the content of partially-completed launcher experience sections. They are written to a client-side file, and not captured by the system until submitted for setup to the back end. So, as of now, no ability to save a "work in progress" application.
• [x] If user skipped a couple of sections, came back to complete a section, then clicks OK, where does that OK navigate to? The next section in the UI? The next incomplete section?

3. "Create Application Set Up" Progress Screen:

• [x] Error states - representing line item/overall status (started working on it in current InVision flow)
  • [x] #878 Flesh out Additional Launcher Status Use Cases for Error/Partial Error States
  • [x] #913 Status Screen for Create Application
• [x] Handling of setup status messaging when user navigates away from screen
• [x] Integrate more guidance in the layout for things the user can do from there. Links to resources? Something else? InVision notes here
  • [x] this line item can be folded into story #863

5. Other UI consistency issues

• [x] Disable "Login & Authorize" button when user has a GitHub account associated with OSIO, per @dlabrecq 's suggestion

[Essjaysee]

Adding some thoughts/expansions on what you have here:

• Consider w/ cancellation what to do with the information already entered: do we allow for a save? Has anything been written before the final submit button?
• In that wizard we worked on a couple years back, if they went back to edit something, OK just took them to the next page, because they might want to reconsider the subsequent information in light of what they just changed.
• The copy is going to need some input from SMEs, so let's get that rolling first.

[bdellasc]

I added the first bullet to my original list.

@Essjaysee RE: the OK behavior, @dlabrecq added functionality where the button will jump them back to a section that they haven't completed yet. We should look at it to see if it feels alright given that we want to encourage someone to "play" within this construct.

[bdellasc]

Addressed all but one issue in this story, and added some additional screens to the alt screens section in the InVision flow. Still need a bit more information on the Progress Screen based on the comments made in InVision a while back.

[bdellasc]

Added/reorganized this list since there are so many interconnected stories. I broke down sections of the launcher to a more granular level, since the stories we wrote for it have a copy and design component to them. This gap list is up-to-date as of 16 March 2018. @stacymcauliffe

[bdellasc]

Made a lot of progress updating the larger flow today - have not uploaded it to InVision yet.

[bdellasc]

Completed most of the edits. There are a few stragglers (around errors) that @stacymcauliffe is working through. I uploaded the entire experience to InVision

[bdellasc]

Added the specific open questions on the InVision Flow. All are awaiting Dev's reply.