If you're going where the Internet is slow, mobile data is expensive, or you can't get online, you can save an area from Google Maps to your phone or tablet and use it when you're offline.Note: Downloading offline maps isn't available in some regions because of contractual limitations, language support, address formats, or other reasons. Step 1: Download a mapNote: You can save maps on your device or an SD card. If you change the way you save maps, you’ll have to download the map again. On your Android phone or tablet, open the Google Maps app. Make sure you're connected to the internet and.
Search for a place, like San Francisco. At the bottom, tap the name or address of the place Download Download. If you searched for a place like a restaurant, tap More Download offline map Download.Save offline maps on an SD cardOffline maps are downloaded on your device’s internal storage by default, but you can download them on an SD card instead. Offline maps that you downloaded on your phone or tablet need to be updated before they expire. When your offline maps expire in 15 days or less, Google Maps will try to update the area automatically when you're connected to Wi-Fi.If your offline maps aren’t automatically updated, you can update them by following the steps below. From the notification.
How to save offline maps on iPhone with the Google Maps app. Launch the Google Maps app and search for the area you want to save. Tap on the menu button and choose Offline areas.
In the 'Update offline maps' notification, tap Update Now. Tap the expired or expiring area on the list. Tap Update. The offline area will update.From anywhere else. On your Android phone or tablet, open the Google Maps app. In the top left, tap the Menu Offline maps. Tap the expired or expiring area on the list.
Tap Update. The offline area will update.
Register for this year’s #ChromeDevSummit happening on Nov. 11-12 in San Francisco to learn about the latest features and tools coming to the Web. Eng Manager, Web Developer RelationsTheProgressive Web App uses IndexedDB for application state and the Pokemondata set while the Cache API is used for URL addressable resources.Internet connections can be flakey or non-existent on the go, which is whyoffline support and reliable performance are common features in. Even inperfect wireless environments, judicious use of caching and other storagetechniques can substantially improve the user experience. In this post, we’llsummarize some ideas around offline data storage for PWAs — think JSONpayloads, images and general static data required to provide a meaningfulexperience offline. RecommendationLet’s get right to the point with a general recommendation for storing dataoffline:. For the network resources necessary to load your app while offline, use the(part of ).
For all other data, use(with a ).Here’s the rationale:Both APIs are asynchronous (IndexedDB is event based and the Cache API isPromise based). They also work with. IndexedDB isavailable.
ServiceWorkers (and the Cache API) arein Chrome,Firefox, Opera and are in development for Edge. Promise wrappers forIndexedDB hide some of the powerful but also complex machinery(e.g. Transactions, schema versioning) that comes with the IndexedDBlibrary. IndexedDB will support, which allow easysynchronization between tabs.Safari 10 hasin their latest Tech Previews. NOTE: Some folks have run into stabilityissues with Safari 10’s IndexedDB and PouchDB and have found it to be alittle slow. Until more research has been done here, your mileage may vary.Please do test and file browser bugs so the folks @webkit and related OSSlibrary authors can take a look.
![Edge Edge](/uploads/1/2/5/3/125398046/305528685.png)
LocalForage, PouchDB, YDN and Lovefielduse WebSQL in Safari by default (due to lack of an efficient way tofeature-test for broken IndexedDB). This means these libraries will workin Safari 10 without extra effort (just not using IndexedDB directly).For PWAs, you can cache static resources, composing your application shell(JS/CSS/HTML files) using the Cache API and fill in the offline page data fromIndexedDB. Debugging support for IndexedDB is now available in(Application tab),Opera,(Storage Inspector) and Safari (see the Storage tab). What about other storage mechanisms?Web Storage (e.g LocalStorage and SessionStorage) is synchronous, has no WebWorker support and is size and type (strings only) limited. Cookies but aresynchronous, lack web worker support and are also size-limited.WebSQL does not have broad browser support and its use is not recommended.The File System API is not supported on any browser besides Chrome. Theisbeing improved in theand specs but neither issufficiently mature or standardized to encourage widespread adoption yet.
How much can I store?