iOS Address Autocomplete: Google Places or Free MapKit

Address autocomplete is one of those small features that quietly decides whether a checkout or signup succeeds. Typed addresses are error-prone; suggestions fix that. You can power it with the Google Places API or with MapKit’s free native completer, and the UI is the same either way. VP0 is the free, AI-readable iOS design library builders start from for the search field and suggestion list, so the experience feels native whichever backend you choose.

Who this is for

You are building an iOS app, maybe with Cursor or Claude Code, with an address or place field, at checkout, signup, or a delivery form, and you want fast, accurate autocomplete without a surprise bill. This is the pattern, with both options.

Two ways to power it

The Google Places API returns predictions as the user types and has broad global coverage and rich place data, but it is a paid service and you must protect your key. The native alternative, MKLocalSearchCompleter, is built into MapKit, returns completions as the user types at no API cost, and needs no extra key, which makes it the natural first choice for an iOS-only app. Build the field in SwiftUI and you can swap the source behind the same list.

Choosing between them

Factor	Google Places	MKLocalSearchCompleter
Cost	Paid per use	Free
Key management	Server-side, protected	None needed
Global coverage	Very broad	Good, Apple Maps data
Place detail	Rich	Solid for addresses
Best for	Global reach, rich data	iOS-only, no cost

For many apps the free native completer is enough; reach for Google when you need its global coverage or detailed place data. Either way the suggestion list and selection flow are identical, which is why starting from one clean design works for both. In practice most teams ship the free native completer first and only reach for Google when a user in a region it covers less well asks for better results.

Debounce, or pay for it

The one technical rule that matters most: debounce the input. Calling the backend on every keystroke is slow and, with Google, expensive. Wait a short moment after the user stops typing, then send one request, so a five-letter street is one call instead of five. The BBC lost an extra 10% of users for every additional second of delay, and a flickering, laggy suggestion list feels exactly that slow. With Google, also group the autocomplete and the final details into one billing session and keep the key server-side. The same map-setup discipline appears in a map configuration and layout guide, and a route-following companion in a Mapbox driver route template.

A worked example: a delivery address

A customer starts typing their street at checkout. After they pause for a moment, one request goes out and four suggestions drop into the list. They tap theirs, and the app fills the structured fields, street, city, postal code, and a place identifier, all at once, with no chance of a typo in the postal code. Because you grouped the calls into a session, Google bills you once for the whole address, not once per keystroke. Had you skipped debouncing, that single address would have fired a dozen requests and shown a jittery list. Instead the customer got a fast, clean pick, your bill stayed small, and the order shipped to a valid address the first time. Multiply that across thousands of checkouts and the difference is fewer failed deliveries, fewer support tickets about wrong postal codes, and a noticeably smaller API bill, all from two small decisions: debounce the input and group the calls into one session. Neither is hard, and both are easy to forget when an AI scaffolds the field and calls the API on every keystroke by default.

Common mistakes and fixes

• Calling on every keystroke. Debounce so one address is a few calls, not many.
• Exposing the API key. Keep Google keys server-side.
• Ignoring the free option. MKLocalSearchCompleter covers many iOS-only apps.
• Not using sessions. Group autocomplete and details to be billed once.
• Free-typing the result. Fill structured fields from the selected place.

Once you have a clean address, organizing the rest of the operation is the next step, as in a property management app.

Key takeaways

• Autocomplete cuts address errors at checkout and signup.
• Use Google Places for global reach, or the free MKLocalSearchCompleter on iOS.
• Debounce input and use sessions to keep speed up and cost down.
• Fill structured fields on selection, from a free VP0 design.

Frequently asked questions

The FAQ above covers building the autocomplete UI, the free native alternative, avoiding a big bill, and why debouncing matters.