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

Reloading UITableView while Animating Scroll in iOS 11

Reloading UITableView while Animating Scroll Calling  reloadData  on  UITableView  may not be the most efficient way to update your cells, but sometimes it’s easier to ensure the data you are storing is in sync with what your  UITableView  is showing. In iOS 10  reloadData  could be called at any time and it would not affect the scrolling UI of  UITableView . However, in iOS 11 calling  reloadData  while your  UITableView  is animating scrolling causes the  UITableView  to stop its scroll animation and not complete. We noticed this is only true for scroll animations triggered via one of the  UITableView  methods (such as  scrollToRow(at:at:animated:) ) and not for scroll animations caused by user interaction. This can be an issue when server responses trigger a  reloadData  call since they can happen at any moment, possibly when scroll animation is occurring. Example of s...

What are the Alternatives of device UDID in iOS? - iOS7 / iOS 6 / iOS 5 – Get Device Unique Identifier UDID

Get Device Unique Identifier UDID Following code will help you to get the unique-device-identifier known as UDID. No matter what iOS user is using, you can get the UDID of the current iOS device by following code. - ( NSString *)UDID { NSString *uuidString = nil ; // get os version NSUInteger currentOSVersion = [[[[[UIDevice currentDevice ] systemVersion ] componentsSeparatedByString: @" . " ] objectAtIndex: 0 ] integerValue ]; if (currentOSVersion <= 5 ) { if ([[ NSUserDefaults standardUserDefaults ] valueForKey: @" udid " ]) { uuidString = [[ NSUserDefaults standardDefaults ] valueForKey: @" udid " ]; } else { CFUUIDRef uuidRef = CFUUIDCreate ( kCFAllocatorDefault ); uuidString = ( NSString *) CFBridgingRelease ( CFUUIDCreateString ( NULL ,uuidRef)); CFRelease (uuidRef); [[ NSUserDefaults standardUserDefaults ] setObject: uuidString ForKey: @" udid " ]; [[ NSUserDefaults standardUserDefaults ] synchro...

Xcode & Instruments: Measuring Launch time, CPU Usage, Memory Leaks, Energy Impact and Frame Rate

When you’re developing applications for modern mobile devices, it’s vital that you consider the performance footprint that it has on older devices and in less than ideal network conditions. Fortunately Apple provides several powerful tools that enable Engineers to measure, investigate and understand the different performance characteristics of an application running on an iOS device. Recently I spent some time with these tools working to better understand the performance characteristics of an eCommerce application and finding ways that we can optimise the experience for our users. We realised that applications that are increasingly performance intensive, consume excessive amounts of memory, drain battery life and feel uncomfortably slow are less likely to retain users. With the release of iOS 12.0 it’s easier than ever for users to find applications that are consuming the most of their device’s finite amount of resources. Users can now make informed decisions abou...