Findings from the Finnish pilot to be solved

[jaakkokorhonen]

Password complexity requirement Help Text missing.
Scrolling is not fluent. People appear bored while scrolling, and forget what they were doing. Seen anecdotally on Mozilla both in Mac and Android. Not on all browsers.
Users cannot intuitively find annotation. The mouseover activation is not familiar to all users. Maybe Replace mouseover with clicking the chapter?
Submit registration -button cannot be seen with a Windows Mobile phone with IE10.
Annotation is not saved with an enter-button.
Android 4.1.2 default browser would not respond when pressing the mobile menu-button.
When editing a comment, the button says “Edit” instead of “Save”.
When user adds a keyword, system announces “Keywords saved”, but when viewing keywords in keyword list, they are not visible. This suggests Notification Engine does not have keywords to consume, and cannot deliver value for the user.
Registration was caught by Hotmail spam filter.

[jaakkokorhonen]

There is a separate ongoing work regarding the issues that are considered unsolvable d-cent/patterns#60.

[jaakkokorhonen]

Design challenges are in #68

[gvilarino]

@jaakkokorhonen

Password complexity requirement Help Text missing.

There's no password complexity check built into DOS; that would be additional development. Validation mechanisms are there, just not the complexity check.

Scrolling is not fluent. People appear bored while scrolling, and forget what they were doing. Seen anecdotally on Mozilla both in Mac and Android. Not on all browsers.

Performance depends a lot on the device/browser combination. I've seen this happen sometimes when there's a lot of participation in one topic; again it depends on the user stack.

Users cannot intuitively find annotation. The mouseover activation is not familiar to all users. Maybe Replace mouseover with clicking the chapter?

Aesthetics; a simple CSS intervention should do the trick.

Submit registration -button cannot be seen with a Windows Mobile phone with IE10.

I'm at a loss there; it probably has to do with some browser characteristic not being fully compatible with webkit; we never had windows phones to try DOS on.

Annotation is not saved with an enter-button.

Neither is commenting or replying; we aim to keep the same UX for all content inputs.

Android 4.1.2 default browser would not respond when pressing the mobile menu-button.

Yeah, Android default browsers are usually really lacking on modern web compatibilities; we know a lot of stuff doesn't work on Android default browsers. Probably why most Android users get Chrome. We don't have plans on providing support for that since every Android version seem to change their web-compatibility strategy.

When editing a comment, the button says “Edit” instead of “Save”.

Yes, that's by design. If you want to change it it's on the language file.

When user adds a keyword, system announces “Keywords saved”, but when viewing keywords in keyword list, they are not visible. This suggests Notification Engine does not have keywords to consume, and cannot deliver value for the user.

It works for me, and Francesca reportedly tested it and worked for her as well, so I'm not sure what you mean with this. Notifier does work only for existing system tags, not for any given string.

Registration was caught by Hotmail spam filter.

Sometimes happens; free mandrill tiers can do that. Using a paid account may solve this. Then again, it has a lot to do with the mail provider.

[jaakkokorhonen]

Well, Validation mechanism help text is missing. how to add? No point making every user guess the validation requirement, right?

[jaakkokorhonen]

Ok if scrolling is a node client performance issue, let's avoid scrolling. Do we know if this is for all node apps?

[jaakkokorhonen]

Maybe change the save-link to a save-button. Shouldn't be too hard, we'll have a look.

[jaakkokorhonen]

Let's try edit-change and see if they get it. Still a bit funny if it needs to be same text.

[jaakkokorhonen]

There are thousands of potential keywords when reading Decisions API data. Should we insert them all in forehand? Where are the instructions for this?

[jaakkokorhonen]

We'll see if there is window to change outgoing email to a @okf.fi address.

[gvilarino]

Well, Validation mechanism help text is missing. how to add? No point making every user guess the validation requirement, right?

I guess a simple validator in the form with a regex for the validation strategy should do the trick.

Ok if scrolling is a node client performance issue, let's avoid scrolling. Do we know if this is for all node apps?

It's not a node issue, its a client-side, javascript performance issue. Older devices and browser can get skippy on this.

There are thousands of potential keywords when reading Decisions API data. Should we insert them all in forehand? Where are the instructions for this?

It's by creating tags, which you have done already from /admin.

We'll see if there is window to change outgoing email to a @okf.fi address.

The outgoing email address is a notifier env variable: MANDRILL_FROM_EMAIL

[jaakkokorhonen]

it will not be feasible to insert thousands of keywords by hand. any better ideas?

[gvilarino]

Make a json dump of all available keywords and a script to load them in the tags collection in the DCENT database; always respecting the format that tags already have. This is all explained in the wiki