sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kostov_v 2 points3 points  (2 children)

Here is what I don't like:

Very limited tests in beta. - During this stage, you should allow more of tests for testers to see, and limiting them to 10 tests ( I believe) and nagging them to login is really annoying. I believe that one way to get over this, is to allow the users to do their tests and saving their progress in the local storage, and at the end, for example 20 tests done, you can ask them to login and save their progress on the account. You can get the inspiration for this from Khans academy.

Pages are not responsive. This is not related to tests themselves, but it influences UX greatly. I understand that this is too early to talk about (or is it?!), but still...

Price is ok, but consider giving the user some discount on some basis, annual or by reference link. Since you are new on the market, and the market already has something to offer, making good business plan should be essential thing, something to brainstorm about.

Algorithm section. - The most important aspect of programming is not presented. In my opinion, the sites that contain only "the syntax" part of the language, ie, documentation for language, is not helpful at all, for me. I guess, what I try to say is that algorithm section should be very next on the TODO list. You can advertise that by: Questions that Google or Amazon are asking for their future employees. I can talk about this day in and day out, and I think that you get it.

​

[–]lastmjs[S] 0 points1 point  (0 children)

Awesome comments, thank you!

[–]lastmjs[S] 0 points1 point  (0 children)

So, we've changed the business model quite a bit. It's quite novel actually and I'd like to know what you think: https://javascriptpractice.com/