Wanted to give you an update on this API issue.
I used Microsoft VirtualEarth API for timezone calculations. Works very very on desktop, and I can’t think of a reason why it wouldn’t be the same on a mobile browser, given the coverage of Microsoft and the usage of Virtual Earth. Nevertheless, either Wappler handling of the data or the API itself wasn’t displaying well on a mobile browser.
I made a test with Google Geo APIs, and the API and Wappler’s diplay of the data is working well.