UX Feedback: "Save and publish" misleading text

[camelgod]

When clicking "Publish Scene ..." in top right to save and publish your Spoke project, you are met with the following buttons in the modal:

Clicking "Save and publish" in this dialog does not actually publish the scene.

To add to the confusion, you get a loading indicator with a modal title "Publishing scene..." and text "Exporting scene...".

• As a user I would expect the scene to be published on load finish.
• The entire "Save" context from the first button is lost. As a user I have no information if the scene was saved or not, and I don't get this information at any time through the flow.

After the loading you are met with the Performance Check and THEN the "real" publish scene button.

In my opinion this wording should be changed to something more intuitive such as: After clicking "Save and publish" you go to a "Saving..." loader, then stepping (in tune with the first button word order) into the performance check to finally publish the scene.

Even when aware of this I always tab out when it says "Publishing scene..." and then forget to click the final "publish". Probably not the only one who has done this. :)

┆Issue is synchronized with this Jira Task

[matthewbcool]

This issue was recently discussed in discord and I wanted to add a few points related to the language used here:

"Deploy" might be a better alternative to "Publish"

More information/clearer copy about what "Allow Mozilla to promote my scene" means would be useful since several users have reported confusion around this language. ie: ""promotion" checkbox enabled it does then go into the moderation queue and will show up in search results for scenes after it has been approved"

[camelgod]

"Deploy" might be a better alternative to "Publish"

In my opinion publish is a nice word for it as it is a "creative work" by someone that is made available to others/the gallery/the list of scenes. I dont know the context but deploy is not as intuitive to me. This is just from a HC user perspective but we also already use the word deploy in our pipeline for actual deployment of HC.

Do you have any reason why deploy would be beneficial, or issues relating to the current use of "publish"?

[matthewbcool]

Suggesting a change because we have seen many examples of confusion around what publish means in this context. It creates an idea that anyone will be able to access the scene or their scene will be available to the public. Technically this is true, but there is privacy in the obscurity of the link. e.g: It's extremely unlikely anyone will actually visit one of my published scenes unless I 'publish the link' somewhere.

e.g. from discord user:

"The initial fear/misunderstanding in doing "publish" to preview was that I was worried that it was going to be visible to others while I'm still working on it."