Skip to main content

How to Implementing Auto-Complete With UITextField - Swift

Auto-Complete Text



I recently wanted to add a Safari-like auto-complete feature to an iOS app I've been working on. Specifically, I wanted the app to proactively suggest a complete word based on some initial characters entered by the user, similar to how Safari suggests URLs based on the first few letters in a web address:


As in Safari, tapping Return would allow the user to confirm the suggestion.

Since this is not a feature that Apple provides "out of the box," I thought I would share the approach I took in case it is of interest to anyone.

In this example, the text field will suggest values for the user's fav color:


As the user types, a list of options is consulted to determine which value to suggest. For example:


Suggestions are defined as an array of strings:


let suggestions = [ "red", "orange", "yellow", "green", "blue", "purple" ]

To handle user input, the view controller assigns itself as the text field's delegate and implements the textField(_:shouldChangeCharactersIn:replacementString:) method, as shown below:
func textField(_ textField: UITextField, shouldChangeCharactersIn range: NSRange, replacementString string: String) -> Bool {
 return !autoCompleteText( in : textField, using: string, suggestions: suggestions)
}



This method simply invokes the following method, which searches the suggestion list for the first entry with a prefix matching the user's input. It then updates the text value with the identified suggestion and selects the remaining characters in the text field:

func autoCompleteText( in textField: UITextField, using string: String, suggestions: [String]) -> Bool {
 if !string.isEmpty,
  let selectedTextRange = textField.selectedTextRange,
   selectedTextRange.end == textField.endOfDocument,
   let prefixRange = textField.textRange(from: textField.beginningOfDocument, to: selectedTextRange.start),
    let text = textField.text( in : prefixRange) {
     let prefix = text + string
     let matches = suggestions.filter {
      $0.hasPrefix(prefix)
     }
     if (matches.count > 0) {
      textField.text = matches[0]
      if let start = textField.position(from: textField.beginningOfDocument, offset: prefix.characters.count) {


       textField.selectedTextRange = textField.textRange(from: start, to: textField.endOfDocument) return true
      }
     }
    }
 return false
}


The method returns true if a match was found and false otherwise. The delegate method returns the inverse of this value so the text field will continue to process keystrokes when a match is not found.
Finally, the controller implements the delegate's textFieldShouldReturn(_:) method to "confirm" the suggestion:
func textFieldShouldReturn(_ textField: UITextField) -> Bool {
 textField.resignFirstResponder() return true
}
Note that the text field's autocapitalisationType and autocorrectionType properties were set to .none

Note that the text field's autocapitalisationType and autocorrectionType properties were set to .none and .no, respectively. Disabling auto-capitalisation ensures that the lookup logic will correctly identify matches, since all of the suggestions begin with lowercase letters. Turning off auto-correction ensures that iOS's built-in suggestion bar is not displayed, since suggestions will be made by the text field itself.

Hope you find it useful. For more ways to simplify iOS app development, please see my projects on GitHub:

MarkupKit - Declarative UI for iOS and tvOS
HTTP-RPC - Lightweight multi-platform REST

Comments

Popular Posts

How I Reduced the Size of My React Native App by 85%

How and Why You Should Do It I borrowed 25$ from my friend to start a Play Store Developer account to put up my first app. I had already created the app, created the assets and published it in the store. Nobody wants to download a todo list app that costs 25mb of bandwidth and another 25 MB of storage space. So today I am going to share with you how I reduced the size of Tet from 25 MB to around 3.5 MB. Size Matters Like any beginner, I wrote my app using Expo, the awesome React Native platform that makes creating native apps a breeze. There is no native setup, you write javascript and Expo builds the binaries for you. I love everything about Expo except the size of the binaries. Each binary weighs around 25 MB regardless of your app. So the first thing I did was to migrate my existing Expo app to React Native. Migrating to React Native react-native init  a new project with the same name Copy the  source  files over from Expo project Install all de...

How to recover data of your Android KeyStore?

These methods can save you by recovering Key Alias and Key Password and KeyStore Password. This dialog becomes trouble to you? You should always keep the keystore file safe as you will not be able to update your previously uploaded APKs on PlayStore. It always need same keystore file for every version releases. But it’s even worse when you have KeyStore file and you forget any credentials shown in above box. But Good thing is you can recover them with certain tricks [Yes, there are always ways]. So let’s get straight to those ways. 1. Check your log files → For  windows  users, Go to windows file explorer C://Users/your PC name/.AndroidStudio1.4 ( your android studio version )\system\log\idea.log.1 ( or any old log number ) Open your log file in Notepad++ or Any text editor, and search for: android.injected.signing and if you are lucky enough then you will start seeing these. Pandroid.injected.signing.store.file = This is  file path where t...

Video Calling In IOS Objective C

Video Calling Sources Project homepage on GIT — https://github.com/QuickBlox/quickblox-ios-sdk/tree/master/sample-videochat-webrtc Download ZIP - https://github.com/QuickBlox/quickblox-ios-sdk/archive/master.zip Overview The VideoChat code sample allows you to easily add video calling and audio calling features into your iOS app. Enable a video call function similar to FaceTime or Skype using this code sample as a basis. It is built on the top of WebRTC technology.            System requirements The QuickbloxWebRTC.framework supports the next:     * Quickblox.framework v2.7 (pod QuickBlox)     * iPhone 4S+.     * iPad 2+.     * iPod Touch 5+.     * iOS 8+.     * iOS simulator 32/64 bit (audio might not work on simulators).     * Wi-Fi and 4G/LTE connections. Getting Started with Video Calling API Installation with CocoaPods CocoaPods is a dependency manag...