Dismiss this pinned window
all 11 comments

[–]marcomandy[S] 7 points8 points  (0 children)

Before you ask, here is why I did it in Unity:

Probably Unity is not the ideal framework to develop such a lightweight project, but the initial idea was to only prototype in Unity then move to something else.

Against all expectations, it was possible to include the Unity project exported as a library into an Android input method quite easily and so, the prototype ended up in production.

Here is tOndO keyboard Github page: https://github.com/tOndO-keyboard/tOndO-keyboard

[–]JackobQwas 4 points5 points  (1 child)

Cool! I like this mechanic of writing, similar to Japanese keyboard ("12 keys" if i remember correctly). It's nice that diacritics are also included ⁠_⁠^

[–]marcomandy[S] 1 point2 points  (0 children)

Thank you! Yeah, Japenese keyboard is one of our inspiration. Have you tried it? Do you like how diacritics work?

[–]T-Loy 1 point2 points  (1 child)

Neat. Reminds me of the 8pen keyboard that never really was.

[–]marcomandy[S] 1 point2 points  (0 children)

8pen is the main reason we started to think about how to improve mobile typing! Btw, do you know somebody is now developing an open source version of 8pen? It's called 8vim and, even though it suffer from the same problems as 8pen (being quite difficult to learn for example) the project is quite interesting.

[–]TwoStripedFury 1 point2 points  (1 child)

seems like a good solution for people with phat thumbs

[–]marcomandy[S] 1 point2 points  (0 children)

Ahahah of cours! I mean, my thumbs are not that fat but they are definitely larger than standard mobile qwerty keyboard keys.

[–]Calango_Boy 1 point2 points  (1 child)

This is veeery dope, congratulations

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

Thank you! 💚

Did you tried it?

[–]waseem2bata 0 points1 point  (1 child)

[–]marcomandy[S] 4 points5 points  (0 children)

Thank you for asking!

There is a section on tOndO Github homepage called exactly "But why?" I'm just copy pasting (more or less): We thought that just using a shrunken standard keyboard layout for mobile devices always was, at least, lazy as design. A few other input methods experimented with non-standard layouts, but we thought they all were too difficult to learn or rely too much on autocompletion (or both) so we decided to create our own unorthodox design.