When a user uploads a picture or searches on-line for the nearest events, location-based services are part of the equation. They present unexpected challenges to the developer who targets an international audience and relies on location data.
Hong Kong people won’t use it. It is pretty offensive here.
When a controversial decoding is in a disputed territory or a partially recognized state, the corner cases might become a support and PR nightmare.
Chinese regulators have publicly reprimanded a string of foreign corporations, including Qantas, Zara and Marriott, for labelling Tibet and Taiwan as independent countries, in online drop-down menus.
What are the safest patterns? What are the goals of saorico.com?
Make sure that developers, product owners and testers are aware of the challenge. Think about the implications of what you are building.
From list of countries to EXIF data in pictures and datasets for AI. Avoid biased results, do not test your application only in your own backyard.
Be aware and learn the most common pattern to handle geolocation challenges. How do the big players manage the risks and flaws?
Who holds the responsibility? The developer? The third party API you integrate? Identify who is in charge of the problem.
Stay up to date. Once the ball starts rolling, the “witch hunt” follows.