Mocks should take into account iphone keyboard

[pcardune]

This screenshot should be pretty self explanatory. If there is a filter for the words in the list, then when the text input is focused the keyboard will necessarily obscure the riddle. Maybe that's desired but it seems funny to me.

[MadeofTin]

I was thinking about that. There are two options. As a user when I am typing do I want to see the riddle I am writing about or the possible answers to the riddle I am writing? I am not convinced of either yet, but I'll add a keyboard layer to the ai images so you can easily turn it off and plus make some pngs of both versions. To see how it feels.

[MadeofTin]

Maybe the way to fix it is to make it a custom keyboard. I know you could do it just for an app. So the riddle is full screen but when you try to answer it the customised keyboard comes up. Then you could make a custom keyboard for each difficulty. Don't know if this would make it harder or easier to develop or how harder or easier. Here is Apples Keyboard Documentation

But I think the custom view is more of what we would need.

[MadeofTin]

How is this?
https://github.com/Tinmen/bellows-riddles-base/blob/master/mockups.md#keyboard
It would mean that the interface would be the same for each difficulty making it easier to use, and it would give us full space for making the Riddle Pretty and Awesome.

• Basic (Have just the answers to choose from)
• Basic Extra (Would have the answers and some fool answers)
• Auto Complete (Would just show words as you type, but only words in the riddle group. So they wouldn't show up at first when you open the app. It would limit the number of words shown and no longer be scrollable)
• Auto Complete Extra (Same as above but with extra words to fool you)
• Super Hardcore Riddle Master (It would suggest words, but it would take them from every riddle in the app. Also limit the number that shows up to a non scrollable view. I don't think it would be fair to have a no suggest feature because of different inflections words can have. Or, we would have to validate a response to a list of inflections which is more difficult and would introduce a new UX element to the user. You could get the right answer but have the wrong inflection and get then answer wrong and then be mad... (I don't want to make people mad) When really, I am not looking for the specific "text" of the answer. I am looking for the "concept" of the answer

[MadeofTin]

On the train I realised that adding in the keyboard would add complexity, but there is no reason we could not build the keyboard in JS. That way we could also test it with the web app. Then it would be cross platform as well. We really have a complete idea of what the person would need to be inputing so we could make it look like an IOS keyboard (or not) but really just be a fancy riddle selection tool. We also don't need the keyboard with text input until we reach difficulty Auto-complete. So we can build an easier one first. I'll do some mockups and start some milestones.