| You've typically already cached the data. e.g. Driving around a city. Many people have Apple Maps open, to navigate, and the maps data is already downloaded on Phone A. When Phone B starts Apple Maps (or auto-load it without opening the app) transfer the data from Phone A to Phone B (instead of using A or B's network). Continue the propagation for all phones C through Z. Eventually refresh Phone B's data through the network, transfer the data to Phone A. Its a symbiotic relationship for all the neighboring phones. e.g. Traveling to a foreign country. Staying at a hostel/hotel. You need to download Offline Translations for "English to X". Someone else at the hotel, Phone A, has already downloaded it. When Phone B requests to download it (or auto-refresh it), Phone B gets the data from Phone A (without any online network access). Again symbiotic, because Phone A could have gotten it from some Phone Z, or downloaded the same data it would normally have. The same types of scenarios work for Yelp style reviews and menus, Weather data, App downloads, etc. Any data that is public, location sensitive, and highly cacheable. You could think of it as turning every iOS device into a Torrent seeder for certain data sets. At most each phone is paying some extra battery life. Likely negligible given its just data transfer over UWB/BlueTooth, and made up for by using less battery life because of less network access at other times. |