Now in this specific case the top whitespace may be a bit smaller, but still, the basic limitation still applies which rules out extremely tall designs for example. Notice the shape keyboards take on mobile devices on the mockups drawn below:ĭownload bmml source – Wireframes created with Balsamiq MockupsĪny designs have to work in the restrictions of virtual keyboards. Following are a couple of considerations not made by the other major designs and mockups implementing these considerations: Mobile virtual keyboards shapes So, as I was writing a couple of pretty long comments on the other answer, I felt inclined to present it as an answer as well. So then I thought: What if I put numbers on 2 rows of 5, and then add removal buttons onto one letter row of 3 each? And this is probably the one I'm the most satisfied with:īut I should probably flip the order, right? Starting the top row with 1, 2, etc. So, in adding a "clear" button, I thought of arranging the hex characters in a 4x4 pattern, and then having bigger "removal" buttons underneath:īut this still doesn't feel right! In particular, because mixing letters and numbers seems confusing. Now, 16 is pretty neat for ordering things, but 17 isn't. In removing the dash and the space bar, I would be left with 16 buttons, plus backspace. Which has an unnecessary dash and a space bar that is there more for tradition and coherence than anything else. So, I have begun toying around by modifying this keyboard by Vasili. In addition to this, they need a backspace, and possibly a "clear" button. Users will only need to input 0-9 and the letters A-F. I am to design a web-based, on-screen keyboard for a touch interface.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |