Page MenuHomePhabricator

Minor Phacility onboarding UX gripes
Open, NormalPublic


"New Instance" screen is really wordy:

Screen Shot 2015-09-01 at 9.34.24 AM.png (947×1 px, 129 KB)

Some particulars:

  • Copy can probably be simplified, especially after simplifying the free trial.
  • We haven't had any problems with name abuse, we could probably put that at the bottom of the page.
  • Limitations don't seem to be surprising users either, this could also go on the bottom.
  • Most users will have only one billing account and no clue what that field means. If there's only one valid option, we could hide the field.
  • Name field could maybe be more clear a Name: [__________]
  • We don't currently allow numbers or dashes in instance names but a few instances have ended up with probably-not-their-favorite-names because of this. Noninitial numbers and nonconsecutive, internal dashes are fine.

The new instance page asks you to sit there and reload it:

Screen Shot 2015-09-01 at 9.37.46 AM.png (126×467 px, 13 KB)

Instances usually only take a couple of seconds to start up, but this feels janky. It would be better if we kicked you to a progress bar for like 5 seconds and then sent you here, even if the progress bar was completely artificial and served no purpose but to slow the user down enough that the daemons can usually start their instance.

Alternatively, auto-reloading this page or something.

Minor, but the error-in-objectbox (as here) is something I might want to try tuning a bit more design-wise? It looked a little better to me when it was flush. It ends up looking a little awkward in some of these "status" use cases to me.

I think the rest of this is basically pretty reasonable. Could use a little polish, and maybe move backups to a second screen to reduce complexity:

Screen Shot 2015-09-01 at 9.41.31 AM.png (1×1 px, 246 KB)

You now click "Use Instance" and get asked to authorize:

Screen Shot 2015-09-01 at 9.42.32 AM.png (845×1 px, 101 KB)

There are some technical reasons for this but this isn't great. Even if we can't easily remove this dialog, the generic, technical wording is not as helpful to users as it could be.

Then you end up here, and I think our NUX is just overwhelming if you don't know how to get started:

Screen Shot 2015-09-01 at 9.44.03 AM.png (901×1 px, 135 KB)

I think T5317 is mostly the way forward for this.

Revisions and Commits

Restricted Differential Revision
Restricted Differential Revision
rP Phabricator

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.
fdsfsda claimed this task.
fdsfsda added a subscriber: fdsfsda.


epriestley removed a subscriber: fdsfsda.
epriestley added a revision: Restricted Differential Revision.Sep 2 2015, 7:57 PM
epriestley added a revision: Restricted Differential Revision.Sep 2 2015, 8:12 PM
epriestley added a commit: Restricted Diffusion Commit.Sep 2 2015, 9:21 PM
epriestley added a commit: Restricted Diffusion Commit.

Now complete, although not fully deployed in all cases:

  • Invoices have a print button.
  • Clicking "Manage Payment Account" now gives you a more meaningful error.
  • TOS is now inlined on the instance create workflow instead of on registration.
  • Email verification no longer required to launch instances.
  • Instance launch copy is a bit simpler.
  • Hide billing account if there's only one and you're creating an instance.
  • Hide no-op "Edit Instance" action.

Remaining work:

  • (T9329) Eventually, clean up print CSS a bit.
  • Allow more instance names.
  • Tailor the control a bit.
  • Startup workflow for new instances still rough / reloadey.
  • (T7148) Likely move backups to a backup/export tab.
  • OAuth authorizations.
  • Actual Phabricator NUX.
  • Make "Manage Payment Account" even more meaningful.

Now done:

  • (D14077, etc) Allow more instance names.
  • (D14060) Likely move backups to a backup/export tab.
  • (D14052) Make "Manage Payment Account" even more meaningful.

Tracked elsewhere:

  • (T9329) Eventually, clean up print CSS a bit.
  • (T5317) Actual Phabricator NUX.

Remaining here:

  • Tailor the control a bit (Instance Name: [________]
  • Startup workflow for new instances still rough / reloadey. This also applies to test instances.
  • When logging into an instance, you always need to explicitly confirm the OAuth authorization. This is desirable in the general case but could be implicit if you launched the instance, and probably if it's the only instance you're a member of. There are some abuse cases where an attacker gets OAuth info from me that I don't want them to necessarily have, but no cases where an attacker steals their own info, and probably no useful/meaningful cases where an attacker steals a new user's information.

Any individual tasks here left to do separate from T9303?