Local considerations across Google platforms.
WHAT TO ASSUME ABOUT USERS
Android, overwhelmingly Modest devices, frequently Metered data, paid directly Intermittent connectivity
WHAT THAT MEANS FOR PLATFORM CHOICES
On-device processing where possible, since it costs no data and works offline Static maps rather than interactive ones, where interaction is unnecessary Few reads per screen, since each is billed and consumes data Smaller applications, since size determines installation
WHAT TO CHOOSE FOR HOSTING REGIONS
Whatever is nearest your users, measured rather than assumed.
WHY MEASURED
Latency differences between regions are substantial, and the nearest region is not always the obvious one.
WHAT TO TEST
Actual loading and response times from a local connection, at a busy time.
WHAT TO CONSIDER ABOUT COST
Every service billed in foreign currency moves with the exchange rate.
WHAT TO ESTABLISH
Which services have free allowances sufficient for your volume.
WHAT TO BUILD FOR
Working offline, and recovering when connectivity returns.
WHAT TO PROVIDE FOR SUPPORT
A messaging route, since that is where enquiries arrive.
