Page MenuHomePhabricator

Tailor Phacility admin NUX funneling a bit
Closed, ResolvedPublic

Description

This is the current NUX on Phacility:

Screen Shot 2015-09-13 at 6.53.22 AM.png (970×1 px, 156 KB)

It's a little unfocused. If a new administrator signs up, they probably want to "Launch Test Instance" most of the time, then start a real instance later (sometimes, they'll want to start a real instance immediately). However, the blue callout pulls them to start a real instance immediately. So we have a weak cue pointing at the wrong place.

After they've launched their test instance, they almost certainly want to start a real instance (or close the browser and never come back if they hated Phabricator, I suppose). However, the blue callout vanishes. So we don't have a "next step" cue.

If a user who is a member of a real instance shows up here, they almost certainly want to use their instance, and are very unlikely to want to launch a test instance. But the button is fairly inviting.

The "Launch Test Instance" and "Instances" UIs are also closely related conceptually, but physically very far apart.

Maybe the left button should be "Launch Instance", and take you to a modal choice between "Test Instance" and "Standard Instance" (although I think this UI element doesn't look right if we only have two options right now)? I don't love putting more steps on this workflow but this feels relatively reasonable to me.

Then "Launch Test Instance" can be "View All Instances" and take you to the browse UI, maybe.

Finally, we can pull cueing up top:

  • If you have no instances, suggest "launch a test or standard instance".
  • If you have a test instance, suggest "launch a standard instance".
  • If you have a standard instance with only one user, suggest "invite users".
  • If you have a standard instance with a bill due, suggest "pay invoices".
  • If you're a member of an instance but don't own any instances, probably no cue.

Revisions and Commits

Restricted Differential Revision

Event Timeline

epriestley raised the priority of this task from to Normal.
epriestley updated the task description. (Show Details)
epriestley added a project: Phacility.
epriestley added subscribers: chad, epriestley.

We just got an instance like testnumber1 created as a standard instance, so I think this is definitely less clear than it should be. But the new "you can use numbers in your isntance names" stuff works!

(No one but me has actually launched a test instance yet, so it's possible that the workflow only works for me and/or is impossible to find.)

I played some with it this weekend and yeah it's a little odd that test instance is so high and real instance feels buried (I was already working on this, so I grabbed the task). I've been rebuilding PHUIActionPanelView and hope to have it in a decent state tomorrow and new Phacility NUX after.

Cool, sounds good. Definitely no rush on this, I just had the same feeling of things being odd.

Not exactly related, but I also want to:

  • Kick test instances out of the staff dashboard active instance count (the count currently includes them, so this number's going to be a bit odd until I clean that up).
  • Add instance type filtering options to the ApplicationSearch thingie.
chad added a revision: Restricted Differential Revision.Sep 16 2015, 9:45 PM
chad raised the priority of this task from Normal to High.Sep 17 2015, 5:06 AM
chad added a commit: Restricted Diffusion Commit.Sep 17 2015, 5:18 PM
chad lowered the priority of this task from High to Normal.Dec 10 2015, 11:46 PM

Anything else we want to do here?

I think we're good on the actual Phacility flow, seems like users aren't running into the same problems they used to (e.g., confusion about ""test" instances").

Kick test instances out of the staff dashboard active instance count (the count currently includes them, so this number's going to be a bit odd until I clean that up).

D16082 eventually did this, moments ago.

Add instance type filtering options to the ApplicationSearch thingie.

Hasn't actually seemed too important. Easy to add if I need it later, zero impact on NUX anyway.