This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
Improve application naming UX #3372
Labels
area/app-wizard
area/launcher
area/UX
team/analytics/wizard
team/analytics
team/app-creation
Team works on Getting Started
type/question
Description
We had few discussions over the past weeks on how to make the new Launcher flow smoother, faster and requiring less user interactions. One of the aspect was the naming of the application.
The flow should help the user to provide an application name which will be meaningful to him. At this moment, we default "App-test-1" upfront, at the beginning of the flow, while the user does not really know yet what he will be creating. The user will be giving more context later on (by selecting mission / runtime) on what is the purpose of the application.
One of the thought here is that the application name should maybe not be defined upfront - but at the end of the flow.
When Creating a New Application using the boosters
By knowing the runtime/mission, we could be giving a useful name to the application to be setup (ex: mission-runtime-#). This would be proposed to the user and be editable.
When Importing a new application
By reusing the name of the repository which will be imported.
Links
Referencing comment in the discussion:
#3138 (comment)
The text was updated successfully, but these errors were encountered: