Kirill Bondar 11/15/2018 5:06:18 PM
Mobile app performs quite aggressively when it detects the need for coordinates (the presence of DeviceLocation() function in action assignments) - it **requires** your device to provide location with 30m accuracy and blocks all the other operation while working with GPS module. Yet this behavior is acceptable since it affects the only path - if you want the mobile app task to have location stamp, add DeviceLocation() to mobile app action.
With desktops it's not the case. Many of them do not have GPS at all and rely either on IP-address-to-location database or on user filled settings in control panel. So, this would be likely optional feature. Next, getting current location takes significant - for computers -- amount of time, couple of seconds. This makes it hard to use BrowserLocation() in formulas. If you attempt to view the form with BrowserLocation() formula on screen, how should it behave? What if BrowserLocation() is in view's filter? What should it return when used in periodic trigger's action when there is no user in context?