do you know that…
- a simple choice in a drop down list could be a PR nightmare
- integrating a mapping service makes many users unhappy
- if you ignore geolocation challenges, your business can be severely affected
- some countries change name
- you might be reinforcing political views that you are not aligned with
How should software developers and testers manage location-based services when dealing with disputed territories or partially recognized states? How can they care about all their end users? From Hong Kong to war zones, from Crimea to Palestine, we will show examples and basic patterns on how to deal, and eventually limit, the impacts of the geolocation challenges.
the (accidental) developer in disputed territories
When a user uploads a picture, posts on Facebook or searches on-line for the nearest events, location-based services are part of the equation. They present unexpected challenges to the developer/tester who targets an international audience but wants to rely on location data to control new features.
When a controversial decoding is in a disputed territory or a partially recognized state, the corner cases might become a support and PR nightmare: what are the safest patterns and how do the four big platforms (Amazon, Google, Apple and Facebook) tackle issues related to geolocation?
presentations and workshops
Renato did present the topic at different national and international conferences in Berlin and abroad and performed a workshop at Factory Berlin in 2019. Some selected events are below.
- re:publica abstract slides
- Factory Berlin abstract
- Think About! meetup info
- Make Random Great Again info
- Codemotion info
- Linkedin article
what does saorico.com mean?
The project’s name saorico.com derives from São Rico, a fictional (and controversial) South American country in The Adventures of Tintin.