Mobile/Archive/Virtual Keyboard

Summary

We're not implementing our own soft keyboard - Fennec will use the native soft keyboard on all platforms.

This project is to make sure that our UI is usable and effective even when a softkeyboard is deployed and so is taking much of the screen real estate.

In practice, this will be the result of three design areas:

1. in general, only bringing up the keyboard when it's actually wanted (not prematurely, if the browser is making on-screen suggestions first)
2. making sure that our UI is not obscured by the on-screen keyboard
3. altering the mechanism by which people select a search engine, so that it's only on screen when it has to be -- this is so that we can use the sliver of the awesomescreen that is visible (esp. in landscape) when the user is typing for awesome-suggestions.

Team

• Project Lead:

Designs

Search Flow

Proposals

• Proposal A [Pflippp] https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/Fennec_1.1%2B/Option_A_for_Awesome_screen_layout_revision
• Proposal B [Pflippp] https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/Fennec_1.1%2B/Option_B_for_Awesome_screen_layout_revision

Starting Point (common)

Before the user has started to type, the screen shows the pre-typing awesomelist and the category selectors. Important: we shouldn't bring up the VKB immediately on coming to the awesomescreen; an additional tap on the entry-field should be required.

Initiating Searching

Variant 1

Variant 2

Variant 3

more detail:

Selecting Search Engine

Variant 1

Variant 2