As a long-time Android user with a fascination for innovative launcher and keyboard projects, I have to say that I'm very happy to see the amount of progress made and success enjoyed by Minuum in just one year. Minuum is the most innovative Android keyboard approach I've seen since 8pen (which didn't turn out nearly so well).
At this point, I keep three keyboards installed: SwiftKey because I've used it for so long and can still manage the highest WPM output with one hand using it, Minuum for all the reasons mentioned in my previous paragraph, and Google Japanese Input because neither of the former two keyboards offer Japanese input yet.
I would of course be happy to uninstall the Google Japanese Input keyboard the instant SwiftKey or Minuum offers Japanese input as I much prefer unified applications over fragmentation, but I recognize the logistical difficulties in implementing a language that doesn't fit well in an alphanumeric design.
What I'd really like to know is, are you considering implementing a swiping functionality into Minuum, and do you think this would be feasible or effective? In your Indiegogo campaign you featured a video that demonstrated twisting a controller left or right to move a letter-selecting dial along the Minuum line.
I thought since then that it would be an inevitable innovation for Minuum to add the option for swipe-based input, such that a user could run their finger back and forth along the line switching direction when they hit the approximate location of the letter they want. My thinking is that this style of input would work similarly to tap input--a change in direction or pause constitutes a tap, and a pause followed by lifting the finger constitutes a tap plus a space--and as a result Minuum could be just as easily used one-handed and would appeal more to SwiftKey users like myself.
I don't have much of a programming background, so I'm imagining this as being fairly simple but perhaps there are some barriers I'm not considering. What do you think?
hanakon1 karma
Hi there, and happy birthday!
As a long-time Android user with a fascination for innovative launcher and keyboard projects, I have to say that I'm very happy to see the amount of progress made and success enjoyed by Minuum in just one year. Minuum is the most innovative Android keyboard approach I've seen since 8pen (which didn't turn out nearly so well).
At this point, I keep three keyboards installed: SwiftKey because I've used it for so long and can still manage the highest WPM output with one hand using it, Minuum for all the reasons mentioned in my previous paragraph, and Google Japanese Input because neither of the former two keyboards offer Japanese input yet.
I would of course be happy to uninstall the Google Japanese Input keyboard the instant SwiftKey or Minuum offers Japanese input as I much prefer unified applications over fragmentation, but I recognize the logistical difficulties in implementing a language that doesn't fit well in an alphanumeric design.
What I'd really like to know is, are you considering implementing a swiping functionality into Minuum, and do you think this would be feasible or effective? In your Indiegogo campaign you featured a video that demonstrated twisting a controller left or right to move a letter-selecting dial along the Minuum line.
I thought since then that it would be an inevitable innovation for Minuum to add the option for swipe-based input, such that a user could run their finger back and forth along the line switching direction when they hit the approximate location of the letter they want. My thinking is that this style of input would work similarly to tap input--a change in direction or pause constitutes a tap, and a pause followed by lifting the finger constitutes a tap plus a space--and as a result Minuum could be just as easily used one-handed and would appeal more to SwiftKey users like myself.
I don't have much of a programming background, so I'm imagining this as being fairly simple but perhaps there are some barriers I'm not considering. What do you think?
Cheers, Cory
View HistoryShare Link