I have an architecture front-end / back-end, specifically an Android app and a backend. I want that the app user can see different prices and currencies depending on their geo-localization.So my Android app has a mechanism to know in which country the user is (based on geo-localization), then it queries the backend using ISO 3 country (GBR) and the backend returns a price (say 5.00). Then I need to get the currency () based on the country. The above mechanism is not neat and elegant but it does the job.The problem here is that every client (Android, iOS, Web app, etc), needs to implement the mechanism, while it seems easier if it was the backend to implement it once.Possible solutions:FE queries the BE by ISO 3 country, BE returns a string containing price and currency ( 5.00, 7.50 ), handling also the different position of the currency symbolFE queries the BE by latitude/longitude, then same as above.What are the pros/cons here?
Handle country specific properties such as price and currency
internationalization;localization;geospatial