Abstract: Aspects of the disclosed technology include checking a route which has been previously generated or stored on a user device to check whether the route can be currently navigated. Aspects include sending, from a user device to a server, route data which may include route segments and/or anchor points. Each route segment may be checked to see if it can be currently navigated. The server may return an alternative route, with replacement route segments, for parts of the route which may not be navigated.

Abstract: In some embodiments, an electronic device present navigation routes from various perspectives. In some embodiments, an electronic device modifies display of representations of (e.g., physical) objects in the vicinity of a navigation route while presenting navigation directions. In some embodiments, an electronic device modifies display of portions of a navigation route that are occluded by representations of (e.g., physical) objects in a map. In some embodiments, an electronic device presents representations of (e.g., physical) objects in maps. In some embodiments, an electronic device presents representations of (e.g., physical) objects in maps in response to requests to search for (e.g., physical) objects.

Abstract: In some embodiments, an electronic device present navigation routes from various perspectives. In some embodiments, an electronic device modifies display of representations of (e.g., physical) objects in the vicinity of a navigation route while presenting navigation directions. In some embodiments, an electronic device modifies display of portions of a navigation route that are occluded by representations of (e.g., physical) objects in a map. In some embodiments, an electronic device presents representations of (e.g., physical) objects in maps. In some embodiments, an electronic device presents representations of (e.g., physical) objects in maps in response to requests to search for (e.g., physical) objects.

Abstract: Technologies described herein reduce the size of a software application. In some embodiments, the size of one or more resource files of an application are reduced. Resource files include key/value pairs that define elements of the application. In some embodiments, the application's source code is analyzed to determine if an entry in a resource file may be removed. For instance, initialization functions in the application's source code may be analyzed to determine if a value loaded from a resource file is replaced before being used. For example, a button with a color property may be defined as grey by a resource, but later set to orange in an initialization function. In this case, the resource entry defining the button as grey is superfluous and may be safely removed. This technique allows for entries to be removed from a resource file even though the source code references the entries.

Abstract: In some embodiments, an electronic device present navigation routes from various perspectives. In some embodiments, an electronic device modifies display of representations of (e.g., physical) objects in the vicinity of a navigation route while presenting navigation directions. In some embodiments, an electronic device modifies display of portions of a navigation route that are occluded by representations of (e.g., physical) objects in a map. In some embodiments, an electronic device presents representations of (e.g., physical) objects in maps. In some embodiments, an electronic device presents representations of (e.g., physical) objects in maps in response to requests to search for (e.g., physical) objects.

Abstract: Technologies described herein reduce the size of a software application. In some embodiments, the size of one or more resource files of an application are reduced. Resource files include key/value pairs that define elements of the application. In some embodiments, the application's source code is analyzed to determine if an entry in a resource file may be removed. For instance, initialization functions in the application's source code may be analyzed to determine if a value loaded from a resource file is replaced before being used. For example, a button with a color property may be defined as grey by a resource, but later set to orange in an initialization function. In this case, the resource entry defining the button as grey is superfluous and may be safely removed. This technique allows for entries to be removed from a resource file even though the source code references the entries.

Abstract: Technologies described herein reduce the size of a software application. In some embodiments, the size of one or more resource files of an application are reduced. Resource files include key/value pairs that define elements of the application. In some embodiments, the application's source code is analyzed to determine if an entry in a resource file may be removed. For instance, initialization functions in the application's source code may be analyzed to determine if a value loaded from a resource file is replaced before being used. For example, a button with a color property may be defined as grey by a resource, but later set to orange in an initialization function. In this case, the resource entry defining the button as grey is superfluous and may be safely removed. This technique allows for entries to be removed from a resource file even though the source code references the entries.

Abstract: Technologies described herein reduce the size of a software application. In some embodiments, the size of one or more resource files of an application are reduced. Resource files include key/value pairs that define elements of the application. In some embodiments, the application's source code is analyzed to determine if an entry in a resource file may be removed. For instance, initialization functions in the application's source code may be analyzed to determine if a value loaded from a resource file is replaced before being used. For example, a button with a color property may be defined as grey by a resource, but later set to orange in an initialization function. In this case, the resource entry defining the button as grey is superfluous and may be safely removed. This technique allows for entries to be removed from a resource file even though the source code references the entries.