But it, in itself, has some glaring product design and marketing issues. In that - it's an afterthought. Which, given that this was a learning experiment, is more palatable for me, than as a service I'm actually expected to signup for and use.
Regarding the current try before signup behavior: i'm not actually trying the app before signing up, when i fill in a form. I'm, filling in a form and then being forced to signup after. Instead, it would be better for users to explore an existing (demo) account's data and tinker with entering results and exploring charts, and then decide to signup if it's good.
If this was a food delivery service, where an account signup could impede potential users from using and where it may not even be required, this approach would make more sense - just let them start using right away. But because it is a collection of data, you would be better off showcasing dummy data.
Also, just to let you know that my timezone is CET :)
Part of making this service was to learn React/Redux and see how different it is to Angular. I've read quite a bit but there's nothing quite like learning by doing something bigger than a todo app - the front-end is open sourced on Github and I plan on writing a few blog posts on what I've learnt building Ewolo, hence the title.
Regarding the text, I wanted to let people know that they can try out the interface without needing an account. I agree with you that it sounds a bit dumb and I'll try to word this better :)
If you have any more ideas on what it would take to really hit it out of the park, I'm all ears!