Good to know. If it's more of a technical exploration of implementation, i would prefer you lead with that. This, as the end result of a series of blog posts, w

Good to know. If it's more of a technical exploration of implementation, i would prefer you lead with that. This, as the end result of a series of blog posts, would make a lot more sense to me. 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.