Cotary Create: Feedback February 21st - deployed live at https://daocreator-v2.herokuapp.com

[mrrobot16]

Please write down all feedback that you can come for https://daocreator-v2.herokuapp.com/

For stylings feedback can be checked here #408

Thanks :)

[orishim]

Hours field looks messed up in Advanced view

Also these should not have AM or PM, as they are just a number of hours in addition to the number of days.

Overall it is pretty difficult and glitchy trying to edit the days/hours values.

[orishim]

I think having "Connect to Web3" in the Members step is awkward/confusing.. either it should be at the beginning and we include the user by default as before, or we should move it to the deploy step and not add the user by default.

I am personally in favor of the first option.

[dOrgJelli]

When I export the config, "tokenName" is set to "0"

[dOrgJelli]

Layout on mobile isn't correct

[dOrgJelli]

In the "Advanced Configuration", why does it say "Deploy ${Scheme Name}"

[dOrgJelli]

These input fields are strange to me. Does this mean "30 days & 12 hours"? Maybe have 3 separate input boxes for days, hours, and minutes?

[dOrgJelli]

Some of these boxes have up and down arrows when you select them, and some do not

[dOrgJelli]

(1) I miss having the blockie that takes you to etherscan if you click on it. Personal opinion though, would leave it up to @pimato to make the UX decision.
(2) The input field for this box shows a red curly under my address when I edit it. There should be a way to disable spell check for an input field right?

[dOrgJelli]

When you edit the advanced configuration, the speed toggles turn to grey which is nice, but as a new user I might not understand why this is. I think what might help this is to have a warning popup when a user selects the "disabled" speed toggle, letting them know "your configuration will be overwritten with the present" or something like that. This way the user can say "oh no don't do that, I want to keep my custom config.

[dOrgJelli]

I feel like these boxes should be yellow instead of red, as they're warnings after all. As a user, when I saw this red dialog popup I thought the deployment failed:

[dOrgJelli]

When you resume a DAO configuration after reloading the page, the toggles are changed back to enabled, even if the user has made changes in the advanced page:

[dOrgJelli]

If something goes wrong, it'd be great to allow the user to export a log of what happened. We can do this by storing all logged lines and when the user requests, writing all of these to a file. The V1 UI supports this and could be a good place to look for inspiration.