Closed ivelin closed 1 year ago
Name | Link |
---|---|
Latest commit | 337d83dce786c07fbc3eff34f65fb5ee4479f224 |
Latest deploy log | https://app.netlify.com/sites/sporosdaoapp-dev/deploys/639ccbba61bcfa0008b6079c |
Deploy Preview | https://deploy-preview-183--sporosdaoapp-dev.netlify.app/ |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Our CTA on the new website is "Start Your Company." We should be consistent with our language since we're saying DAO here. Up to this point, we all agreed Company is the right word bc Sporos isn't just for 'DAOs' but we should decide if we want to say "DAO" and then be consistent everywhere.
Content changes to marry up with figma https://www.figma.com/file/HjgPX0qjMYgvDjeliS4EwD/Sporos-DAO-App?node-id=637%3A87910&t=VagQAtEtSXEaKrgf-0
Fields aren't showing on the Name screen.
Can't see info inputted into fields. Also background is gray for founder area where should be white.
If a user accidentally clicks "add founder" there's no way to delete a founder in order to continue with the flow. In the example shown here, I've added 4 other founders but I'm really the only founder. I now want to delete the others so I can move on. I'm now stuck.
I'm able to input a ton of characters in the token symbol field. I believe the max supported by blockchain explorers is 11 but not 100% confident in that.
This is what I see when starting the create a LLC flow. Very different colours from lipmans screen. Much of the headings and text on right hand panel are unclear.
Unlike lipmans experience, the company name fields are all showing for me. The panel on the left is clear. Panel on right unclear as in the previous screen.
Founder fields not visible. They do appear when clicked on.
Adding a founder works aside from the visibility.
Good report, Kleb. It shows that the custom theme was not prepared to handle dark mode. I will go through these inconsistencies and replace them with default MUI colors and icons.
As we've discussed before, that's one of the many details that need to be handled when building a custom theme. It's very resource intensive to get it right in all modes on all devices and all browsers. It is not an automatic switch from good looking Figma drawings to production ready code.
On Fri, Dec 9, 2022 at 3:16 AM kleb-33 @.***> wrote:
[image: image] https://user-images.githubusercontent.com/91540657/206667075-ef866a37-062f-4542-86f5-e3f220b1e6e3.png This is what I see when starting the create a LLC flow. Very different colours from lipmans screen. Much of the headings and text on right hand panel are unclear.
— Reply to this email directly, view it on GitHub https://github.com/SporosDAO/sweat-token/pull/183#issuecomment-1344050412, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARBUFO3QQ4MOD3MNGDOZTDWML2IBANCNFSM6AAAAAASRDDMKI . You are receiving this because you authored the thread.Message ID: @.***>
OK, good catch. That is another example with custom theming. It's hard to get it to look good on all devices, modes and browsers. I will go through these and revert to default MUI options. The weird thing is that you seem to be using the same OS and browser that I am testing on and there is still inconsistency in theme color rendering.
On Thu, Dec 8, 2022 at 8:23 AM lipman @.***> wrote:
Path: /dao/create/stepper/42161
Browser: Chrome 107.0.0.0 on Mac OS 10.15.7
Viewport: 1966 x 1177 @2x
Language: en-US
Cookies: Enabled
Open Deploy Preview https://deploy-preview-183--sporosdaoapp-dev.netlify.app/dao/create/stepper/42161 · Mark as Resolved https://app.netlify.com/cdp/resolve?deployID=6390fc105b7a940009d1bcbb&commentID=6391f352957917200ed891b2&resolution=resolved
— Reply to this email directly, view it on GitHub https://github.com/SporosDAO/sweat-token/pull/183#issuecomment-1342814818, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARBUFPFCW3EN7TGYPSMUWTWMHVN3ANCNFSM6AAAAAASRDDMKI . You are receiving this because you authored the thread.Message ID: @.***>
Black font on the green button is automatically calculated by MUI in order to meet usability requirements. Forcing white will break one of the lighthouse tests for contrast or color blind differences. It could be many man weeks of effort to try to get a custom theme working properly. My focus will be on reasonable user experience with MUI defaults for MMP. If we want to launch something soon, a pixel perfect match of figma examples will have to come in a follow up version.
On Thu, Dec 8, 2022 at 8:13 AM lipman @.***> wrote:
Content changes to marry up with figma https://www.figma.com/file/HjgPX0qjMYgvDjeliS4EwD/Sporos-DAO-App?node-id=637%3A87910&t=VagQAtEtSXEaKrgf-0 Browser metadata
Path: /dao/create/42161
Browser: Chrome 107.0.0.0 on Mac OS 10.15.7
Viewport: 1966 x 1177 @2x
Language: en-US
Cookies: Enabled
Open Deploy Preview https://deploy-preview-183--sporosdaoapp-dev.netlify.app/dao/create/42161 · Mark as Resolved https://app.netlify.com/cdp/resolve?deployID=6390fc105b7a940009d1bcbb&commentID=6391f10e74f72b1dbf2786b9&resolution=resolved
— Reply to this email directly, view it on GitHub https://github.com/SporosDAO/sweat-token/pull/183#issuecomment-1342800245, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARBUFMP4DPUSQ7DQGZPV6TWMHUJTANCNFSM6AAAAAASRDDMKI . You are receiving this because you authored the thread.Message ID: @.***>
I'm able to input a ton of characters in the token symbol field. I believe the max supported by blockchain explorers is 11 but not 100% confident in that.
Browser metadata Open Deploy Preview · Mark as Resolved
Good catch. There is no restriction at the contract level, but it's a good practice to keep this short so it looks good in most front ends that expect a short ticker. I set the limit to 11.
Our CTA on the new website is "Start Your Company." We should be consistent with our language since we're saying DAO here. Up to this point, we all agreed Company is the right word bc Sporos isn't just for 'DAOs' but we should decide if we want to say "DAO" and then be consistent everywhere.
Browser metadata Open Deploy Preview · Mark as Resolved
OK. Drop here a screenshot of the latest landing page design with the exact language.
Dark mode has discoloring. @ivelin in Netbee's designs we did not include a dark mode to keep things simple for v1. Idk how complicated it is to create a light mode and dark mode but imo just doing one for v1 is sufficient.
Button font color should be white
Can't see founder fields. Side bar copy and background is discolored.
Can't see settings fields. Side bar with content discolored.
unable to see many of the fields and copy from this screen.
Will we not charge at launch? I see we're waiving the fee. Btw Ignore the ending. I rejected the txn which is why you see the error message.
clicking the menu options doesn't do anything
I mentioned dark/light mode in a previous comment but how do you switch back and forth between the two? I don't see that option.
This top bar was confusing. Almost looks like a search bar but when I clicked the X I saw it took me out of this screen back to the homepage.
First screen still has formatting issues on the right side of the page. Also at the top above "Launch Your Company in Minutes"
Nice! The Founder fields are legible now! See formatting issues with the right side and top of the page. Not sure if the menu options should be clickable but they don't appear to be.
Nice! Settings fields are visible and look great. Right side is still not formatted properly.
Looking good! May consider changing the subheader I've highlighted to a different color bc it's kind of hard to read. Right side of the screen is not formatted properly.
Looking good! See right side of the screen again.
Also getting the invisible fields bug . This is on a WIndows 11 machine using Brave
Nice! The Founder fields are legible now! See formatting issues with the right side and top of the page. Not sure if the menu options should be clickable but they don't appear to be.
Browser metadata Open Deploy Preview · Mark as Resolved
Good feedback.
Navigation tabs are not supposed to be clickable. Just show progress. I did make changes yesterday to make sure the mouse pointer does not indicate clickable items. Also added checkmarks next to tabs that have been completed. If that is still confusing, we can switch to a more standard MUI stepper.
On settings page, field for Voting Period is set to hours. This is not adjustable. If I want to set a voting period to be < 1 hr (e.g 15 mins) the warning message appears telling me 'Voting period has to be a positive number'. 0.25 hrs is a positive number so either:
3 is the best option from user perspective but probably the most work. 1 is the simplest fix in short term.
The Note! section on the right hand panel is not relevant anymore. We had this in the flow when there was no Settings page. As users are inputting their own settings, we can remove this paragraph from the Confirmation page.
Panel on right should read: ' Can I launch my company with more than one founder? Yes. You can add up to 5 founders when you launch your company.'
Minor point but can we remove the capital letters from the words 'Review All Settings' on right-hand panel. Should read: 'Carefully review all settings!'
I mentioned dark/light mode in a previous comment but how do you switch back and forth between the two? I don't see that option.
Browser metadata Open Deploy Preview · Mark as Resolved
Currently the app picks up dynamically the OS mode. Usually light during daytime and dark at night. We can add an explicit switch if users ask for it.
On settings page, field for Voting Period is set to hours. This is not adjustable. If I want to set a voting period to be < 1 hr (e.g 15 mins) the warning message appears telling me 'Voting period has to be a positive number'. 0.25 hrs is a positive number so either:
- Warning message needs to be adjusted to say that voting period has to be minimum 1 hr
- We give users the option of setting voting period to less than one hour
- We give users the option of setting voting period in minutes instead of hours
3 is the best option from user perspective but probably the most work. 1 is the simplest fix in short term.
UPDATE: Implemented #2. Fractional number of hours is allowed as input.
OK, will do 1 for now and see how users react.
Continued work on DAO Formation based on @0xMakka 's Draft PR #148