3 ms·

Great stuff! I think you need a clear pitch of what you're offering users. Something that can leverage word of mouth: short, easy to grasp, exciting. (Of cours

by 13ren 18y ago

Great stuff! I think you need a clear pitch of what you're offering users. Something that can leverage word of mouth: short, easy to grasp, exciting. (Of course, maybe through following supermemo's seeding the geek market, you don't need it for us) The offer is to "help them to learn stuff, by ... ", how? The first part is clear (cute: elephant=memory), but "how" it helps is not clear. "2. We intelligently organize when to study" That doesn't give me a sense of it (sounds like "in the morning"?, "after exercise"?, "at night"?) It's cute having your info as the first scheduled training, but maybe more effective to also have that info available before trial. :-) It's probably just me, but (though cute), I found scheduling that a bit pushy. I'd also feel more comfortable having a clearer sense of when training will occur: what's the scheduling for this deck? I don't think it's needed for the learning task; but it would make the user feel more informed and in control; and not at the whim of a machine (users don't like that). But I think you could have something really successful going there.

jasonb05 18y ago
some good points. I really like your comment about knowing the schedule for a deck. We do have an overview in the train page, and some more information in the stats page, but a clear visualization of a decks complete schedule would be a great addition. thanks.
- 13ren 18y ago
  You're welcome - I had seen the schedule on train page, but not the one on the stats page (this may be because I'm on a tiny eee PC, and didn't happen to scroll down... for this (rare) case, I think some sites have subtle guides in the design to suggest the page isn't finished more lower down - I see you have narrow vertical margins, but the RHS is off my screen... as said, a rare case (and it could just be me). It would be nice to know which each deck is scheduled when (just different colours and a key) - ie, the visualization you suggest. But you've basically answered my issue - actually, the basic schedule you have now is very important, because you need to know, so you visit the site when the next learning is scheduled. One way is (optional) email alerts, to remind people. (Of course, a serious user would be at the site every day anyway). BTW: somehow, the info on train and profile pages seems a bit confused to me... maybe there's a better principle to organize it by, in terms of what the user needs, in their work flow. (but I think it's OK as it is - this is just a refinement). Don't know if any of that helps, but thought I might as well pass on my reactions, just in case they do.

by 13ren 18y ago

jasonb05 18y ago

some good points. I really like your comment about knowing the schedule for a deck. We do have an overview in the train page, and some more information in the stats page, but a clear visualization of a decks complete schedule would be a great addition. thanks.

13ren 18y ago
You're welcome - I had seen the schedule on train page, but not the one on the stats page (this may be because I'm on a tiny eee PC, and didn't happen to scroll down... for this (rare) case, I think some sites have subtle guides in the design to suggest the page isn't finished more lower down - I see you have narrow vertical margins, but the RHS is off my screen... as said, a rare case (and it could just be me). It would be nice to know which each deck is scheduled when (just different colours and a key) - ie, the visualization you suggest. But you've basically answered my issue - actually, the basic schedule you have now is very important, because you need to know, so you visit the site when the next learning is scheduled. One way is (optional) email alerts, to remind people. (Of course, a serious user would be at the site every day anyway). BTW: somehow, the info on train and profile pages seems a bit confused to me... maybe there's a better principle to organize it by, in terms of what the user needs, in their work flow. (but I think it's OK as it is - this is just a refinement). Don't know if any of that helps, but thought I might as well pass on my reactions, just in case they do.