2. Cool icon. No idea what it means, but digging the brush strokes.
3. Scroll down. Not really sure how this works or if I’d like it.
4. Alright, let’s give it a spin. Click “Get Started”.
5. Immediately get presented with a modal asking me to login and “agree to our Terms and Agreements” (I think you mean “Terms and Conditions”).
6. Close page.
The title says “Show HN”, so why aren’t you showing what your project is? Give people a way to try your idea or at least something that closely represents what it’s like to use it and how it could fit into someone’s daily usage.
Thanks for the feedback!
I have been convinced that people can’t understand what the site is like and how to use it intuitively.
This site needs to be more user-friendly.
This whole thing is about performance, but what I'm not seeing any of is actual measurements. Is this actually useful enough to justify all the overhead of writing code in a catered way? Right now I highly doubt it. Is this beneficial at all? After all you're adding some extra overhead and delays which might or might not be made up for by the fact that things are chopped up. The whole of the work doesn't change, you're simply adding breaks in the middle.
I agree with you.
It is difficult to measure how to improve the site performance concretely by using idle-task, but I will do this with my application.
2. Cool icon. No idea what it means, but digging the brush strokes.
3. Scroll down. Not really sure how this works or if I’d like it.
4. Alright, let’s give it a spin. Click “Get Started”.
5. Immediately get presented with a modal asking me to login and “agree to our Terms and Agreements” (I think you mean “Terms and Conditions”).
6. Close page.
The title says “Show HN”, so why aren’t you showing what your project is? Give people a way to try your idea or at least something that closely represents what it’s like to use it and how it could fit into someone’s daily usage.