使用flutter_google_places实现自动补全时，如何存储最近搜索位置？

Hey there! I get where you're coming from—flutter_google_places is great for location autocomplete, but it doesn’t come with built-in recent search storage out of the box. Let’s break down some better alternatives to just using SharedPreferences alone:

1. Upgrade to Better Local Storage Solutions #

While SharedPreferences works for simple key-value pairs, it’s not ideal for storing lists of place objects. For a smoother, more scalable experience, consider lightweight local databases:

• Hive: A fast, NoSQL database that lets you store custom Place objects with minimal setup. It’s faster than SharedPreferences for datasets, and you can easily serialize/deserialize place data to save, sort, or filter recent searches.
• Isar: Another performant NoSQL database with strong typing support. It includes features like queries, indexes, and optional encryption—perfect if you need to manage larger sets of search history or add extra logic like removing duplicates automatically.

Both options make it way easier to manage your recent search list (like keeping only the last 10 entries or deleting specific items) compared to basic SharedPreferences.

2. Google Maps API: No Native Storage, But Useful Tools to Pair With #

Unfortunately, the Google Places API doesn’t provide native support for storing recent searches—that’s a client-side responsibility (since it’s user-specific, personalized data). However, you can use its tools to enhance your custom history feature:

• Use session tokens for every autocomplete request (as recommended by Google). This groups related queries together, improves result relevance, and reduces unnecessary API charges. You’ll still need to save selected places locally, but the token helps streamline the autocomplete flow alongside your history.

3. Purpose-Built Plugins (Limited, But Worth Exploring) #

There aren’t many plugins that directly extend flutter_google_places with recent search support, but a couple of options might save you time:

• Some all-in-one autocomplete plugins like location_autocomplete come with built-in history storage, though they may not integrate as tightly with Google Places as flutter_google_places. If you’re open to switching, this could be a quick shortcut.
• Alternatively, look for plugins focused on local place data storage—though rolling your own with Hive/Isar usually gives you more control over how the history is displayed and managed.

Quick Tips for Custom Implementation #

If you stick with building your own history feature:

• Deduplicate entries: Check if a place already exists in your history before saving it to avoid duplicates.
• Set a history limit: Cap the number of stored entries (like 10-15) to keep the list clean and avoid bloating storage.
• Optimize stored data: Save only essential details (place ID, name, address) instead of the full Google Places response to save space.

Hope that helps you pick the best approach for your app!

内容的提问来源于stack exchange，提问作者Soveyyy