HumanInterfaceGuidelines—CustomKeyboards
Since the last Echo sharing session, I've made up my mind to clean up my act and be good with the basics, so I've started this part, aiming for two months of non-stop updates and writing about Material Design and components in iOS (learning English by the way) so that I'm not at all vain when using it in the future.
Custom Keyboards
Human Interface Guidelines link.Custom Keyboards
Keyboard extension replaces the standard keyboard with a custom keyboard。 Customize the keyboard in the“ set up” applicable“ conventional (weapons)”>“ keypads” initialization。 after activation， Except when editing the security text field and the phone number field， The keyboard is available during text entry in any application。 People can enable multiple custom keyboards， and switch between them at any time。
Custom Keyboard
-Make sure you do need a custom keyboard
Customizing the keyboard makes sense if you want to use unique keyboard features system-wide, such as novel ways of entering text or entering languages not supported by iOS. If you only want to use a custom keyboard in the app, consider creating a custom input view instead.
-Provides an obvious and simple way to switch between keyboards
It is known that when you enable multiple keyboards, the Globe key on the standard iOS keyboard replaces the emoji key, allowing users to quickly switch to other keyboards. Users expect a similarly intuitive experience on a custom keyboard. Note that when you have more than one keyboard, the Globe key will replace the emoji key.
-Do not copy the functions provided by the system keyboard
On the iPhone X, the Emoji / Globe key and Dictation key automatically appear below the keyboard even when using a custom keyboard. Your app cannot affect these keys, so please avoid repeating them on the keyboard to avoid confusion.
-Consider providing keyboard tutorials in your app
People are used to the standard keyboard and it takes time to learn a new one. By providing instructions for use in your app, rather than in the keyboard itself, it can make the learning process easier. Shows people how to use the keyboard, how to trigger it during text entry, how to use it, and how to switch back to the standard keyboard.
Custom Input Views
Custom input view will replace the standard keyboard with a custom keyboard, but only in your app, not system wide. Use custom input views to provide a unique and efficient method of data entry. For example, use a custom input view to enter data values when editing a spreadsheet.
Custom Input View
-Make the function obvious
The controls on the custom input view should make sense in the context of the app. Data entry should be clear and intuitive so that no additional guidance is needed.
-Play standard keyboard clicks during typing
When the user strikes a key on the keyboard， Keyboard clicks provide auditory feedback。 Clicking on a custom control in your input view should also produce this sound。 Please note， This sound is only available for the visible custom input view， One can find the information in the“ set up”>“ sounds” The sound is completely banned in。
-Provide input accessory view if necessary
Some apps use other custom input accessory views that are displayed above the keyboard. In Numbers, the input accessory view helps the user to enter standard or custom arithmetic.