Another +1 I hate when my browser back button is hijacked. And it really upsets me. Other than this let me list out some more constructive feedback.
At first glance the design looks nice. And after messing around with it I would say overall I still feel this way, but it needs a bit of polishing. I also encountered one major issue described below.
Design/Aesthetics/UI/UX
Pluses:
- I do appreciate the minimalist approach to UIs for tools like this.
- However, I do like the small touches in the UX that aren't really minimalism. For example the wave/color burst effects on the buttons on the left hand side sidebar.
Minuses and nitpicks:
- Project overview
-- The project overview contains widgets for both the project overview and the dashboard. The language in one says "Task" in the other it says "Tasks" (plural). Small mismatch there.
- Dashboard screen
-- The text alignment on the header cells of the gant chart doesn't line up with the task names.
- New Task workflow
-- It can be annoying to add lots of task if there is not some sort of streamlined interface for bulk task creation.
-- On the third page of the "New Task" modal.
--- The purpose of the "Status Bar" control is not immediately clear. I wasn't sure what it was for until I created a few tasks. I would name it something like "Completion %" (i'm sure there are better names for it).
--- The start date and due date fields don't have validation. It is possible to create a task where the due date < start date. And this crashes the app.
- Email invite to teammate modal.
-- I'm able to send an invite email to myself even though I already have an account with my email. No sane user would do this, but a hacker might for various reasons.
- The team member Invite email
-- In the invite email the invite I sent to myself ends up displaying as an invalid invitation. This is good, but I would double check to make sure me doing that didn't crash your backend or cause some data consistency issues.
-- I would remove the footer that says "Email sent via Emailjs" if possible. It makes the invite feel cheap.
-- I would also include information about *who* invited me. Maybe not personal information like email address, but the name/username of the teammate who invited me in addition to the project name already there.
-- On the above point you can then use this to make the email subject line more friendly. So instead of just "Invitation to join Test in Workarise" it could be something like "Ethan invited you to join the Test project in Workarise!"
Unfortunately after creating the test task with a due date before it's start date.. the entire frontend is now broken for me so I can't give any more feedback. If you want to delete the last task I created I can continue testing out the product :)
Also! because the UI is failing right now due to the bad data I actually don't have a way to log out. I also don't have a way to reach any kind of support for resolution. And because it automatically redirects from the homepage into my project if i'm logged in.. I can't check for any kind of support email address on the homepage. I would recommend against automatic redirect from the homepage into the project overview.
Small edit: You might be interested in reading this thread: https://twitter.com/pie6k/status/1638317917207945216 I would say I also want to just in general know more about you, the reason for building this product and so on. On the homepage before needing to sign up. It can help give users a "human" reason to want to use the product. Also this guy has a pretty good screen tool if you have a mac and wanted to record tutorial videos of how to use your product :)