dot i/o: Start with shortest chords

[pulsar ferry]

I was really surprised to find that dot i/o didn't teach the 2 character chords first, then move up to 3 character chords, then 4, 5, etc.

I like that there is a 'custom' option to do this, but it feels so natural to set it up that way: the chord-timing for a 2 key chord is easier to find than for 3 or 4 keys.

Repeatedly succeeding at the beginning for a new user is imperative. It would increase ease of adoption; and therefore increase adoption success, and decrease abandonment of learning.

P. S. This sort of process improvement is what I do for a living, and this bothered me enough to work for free, lol. Feel free to dm me if you want to validate the data.

[true mantle]

I don't think it should be by number of letters in the chord but rather the "chord" itself

Chords with more inputs actually have a lot more relaxed timing requirements

I think there are difficult ones, though

Would be best if we had a way to rank chord difficulty and then use that to start, I do agree

[strong fossil]

dot i/o uses the order of word frequency so user can learn the most frequent words first. https://github.com/iq-eq-us/dot-io/pull/31

[pulsar ferry]

This is good to know; however, please consider validating my suggestion with data.

If Learning Abandonment primarily occurs at the ChM - English 300 stage of www.iq-eq.io this would validate that the current learning track increases in difficulty dramatically (rather than sustainably) for a new user.

I'm not saying that using the most frequent words first is wrong--au contraire it is def the right call--but if further narrowing or curating those words can increase adoption success--I do hope CC considers it.

[strong fossil]

I don't think they are completely conflicted with each other, because frequently used words usually have shorter or easier chords. If you take a look at the current list in the source code, first 10 chords (the, of, and, to, in, for, is, on, that, by) are short ones (two or three-key chords). It seems to me that it is enough for user to get used to how to chord.

[pulsar ferry]

Those are not the first 10 chords the UX presented to me. all but 'if' were 3-letter plus, and I still can't do default 'that' (added a custom chord after failing enough times) and it was one of the first 20.

Did I mess up the UX somehow? Is there a way to reset it?

[strong fossil]

https://typing-tech.github.io/CharaChorder-utilities/#/chord-tools There is a chord timing diagnostic tool. Maybe it can help you check your that chord.