))
The (accidental) developer in disputed territories
Manage episode 310369289 series 3053649
Innhold levert av re:publica. Alt podcastinnhold, inkludert episoder, grafikk og podcastbeskrivelser, lastes opp og leveres direkte av re:publica eller deres podcastplattformpartner. Hvis du tror at noen bruker det opphavsrettsbeskyttede verket ditt uten din tillatelse, kan du følge prosessen skissert her https://no.player.fm/legal.
How should software developers 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 cover examples and basic patterns on how to deal, and eventually limit, the impacts of the geolocation challenges.
…
continue reading
- Renato Losio
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 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?
35 participants
92 episoder
Del
