Newsletter
The beta version of Google Maps looks likely to see a number of improvements in due course in relation to road closures, the transit details it provides, and its Uber integration. This is based on information gathered from a teardown of the latest beta app (version 9.72) by XDA-Developers. Of the changes, the most interesting is likely to be the increased Uber integration. Google Maps already does provide Uber information (as it does with Lyft) including how far away the nearest Uber is, and the likely cost of an inputted journey. As well as the option to click through, launch the ride-sharing app and continue booking a ride. However, the new strings in the app suggest Google is readying Maps to make it easier for those who are not already using Uber. In short, it seems Google Maps (the beta, at least) will soon include the option to create an Uber account without having to be redirected to the Uber app first.
The next ‘getting better’ feature is to do with road closure information submitted by users. This is again something Maps already offers although the string information suggests in the future the app will allow users to provide richer road closure information, including precise details on why a road has been closed. Likewise, transit information is also seemingly going to become richer with its most interesting improvement being “transit occupancy.” While the details are still thin on this, the suggestion is Maps may be able to provide details on how busy transit options are inside, although whether this will be based on real-time info or just on previously collected data remains to be seen. Further adding to the general enriching notion, direction preferences, notifications, Q&As, and error messages, all also seem to be in line to gain fuller and more detailed access in the future.
As is usually the case with these teardowns, what is not known is when these features will go live at the user level as they are presently just noted as in a preparation stage within the app. Likewise, there is absolutely no guarantee that they will go live, or for that matter, migrate to the stable version of the app at any point. Lastly, these features are loosely based on interpretation of the code descriptions, and therefore are subject to being incomplete, or misinterpreted.