Slide #47 illustrates the ideal connection structure for Dash7 devices, which is exactly what a p2p mesh network topology such as Bitcoin works well within. An android client that is Dash7 aware can 'mesh' out any transactions that it creates, accepts or otherwise sees via an ad-hoc Dash7 wireless network on the fly. It could
do the same for block headers, or even entire blocks, but considering the likely future size of full blocks and the 500-at-a-time that clients request while bootstrapping, it would be more efficient for a Dash7 aware Bitcoin client to turn on the wifi radio in ad-hoc mode to directly connect to another such client in meatspace. Dash7 mode 2 includes inherent relative location data, so even clients that do not have access to absolute location data (i.e. GPS) do know how close to each other they are, and therefore if they are in range of wifi or not.
Using Dash7 mode 2, a Bitcoin client trying to send or accept an in-person Bitcoin transaction can either transmit the transaction as a broadcast immediately, wait for a semi-random period of time to do the same, broadcast the hash of the transaction and wait till another client requests it, or any combination of the above in order to get that transaction out into the network. If that Bitcoin client does not have ready access to the Internet (and therefore the Bitcoin p2p network), spreading the transaction out to any other Dash7 aware Bitcoin clients increases the odds that one of those clients will have, or will soon have, access to the Internet in order to get that transaction onto the p2p network.