Currently the title of the view is asked for first. The title however is both not needed to publish or save and also isn't an ideal first action. The experience could be improved by considering re-ordering this field.
Describe the solution you'd like
The recommendation would be to put selection of 'Data Source' before title. Which would result in this possible flow:
There could be optional copy change but that recommendation would be separate from this, specifically this is talking about changing the order of the fields.
Describe alternatives you've considered
Presuming the above is an issue to implement there are other options. Asking for a name on publish is actually more ideal, but does potentially require more of a flow change.
Default name
Another option could be to add a default name and make it visible, the user would just edit that name. This doesn't remove it from the view but it does at least generate and make visible in that field.
On publish ask for name
Asking for the name on publish puts it where it probably belongs in the user journey expectations. They are considering it last in the flow, the priority is to get it setup.
Currently the title of the view is asked for first. The title however is both not needed to publish or save and also isn't an ideal first action. The experience could be improved by considering re-ordering this field.
Describe the solution you'd like The recommendation would be to put selection of 'Data Source' before title. Which would result in this possible flow:
There could be optional copy change but that recommendation would be separate from this, specifically this is talking about changing the order of the fields.
Describe alternatives you've considered Presuming the above is an issue to implement there are other options. Asking for a name on publish is actually more ideal, but does potentially require more of a flow change.
Default name
Another option could be to add a default name and make it visible, the user would just edit that name. This doesn't remove it from the view but it does at least generate and make visible in that field.
On publish ask for name
Asking for the name on publish puts it where it probably belongs in the user journey expectations. They are considering it last in the flow, the priority is to get it setup.