Abstract: The disclosed systems and methods provide a novel framework that provides on-device functionality to user devices for localized content ranking, modification and rendering. The disclosed systems and methods provide functionality for on-device personalization in a real-time, secure and network anonymous manner. Rather than exposing a user's data to the network for content tailoring, the disclosed framework performs the ranking and content manipulation locally on the user's device. The disclosed framework enables locally (on-device) built, updated and hosted user profiles to be used to tailor received content for display on a user device. This ensures the integrity of the personalization while maintaining security for the user's personalized data and activities.

Abstract: As provided herein, a translated string, received from a translator for an application (e.g., an instrumented application) may be identified. The translated string may be identified based upon the translated string being associated with a service call instruction for the application. A simulated instrumented application may be generated for testing the application. The simulated instrumented application may be generated to comprise the translated string integrated into the application. The simulated instrumented application may comprise an element corresponding to the translated string. A user interface may be generated. The user interface may comprise the simulated instrumented application, the translated string visually associated with the element, and an editing functionality to edit the translated string.

Abstract: The present teaching relates to creating and updating a user profile related to multiple devices, and synchronizing applications' sessions for the user on different devices. Upon execution of a first application on a first device, a first device ID associated with the first device and information about the first application are received. A user profile is created based on the first device ID and the information about the first application. Upon execution of a second application on a second device related to the first device, a second device ID associated with the second device and information about the second application are received. The user profile is updated based on the second device ID and the information about the second application. Further, the information about the first application is applied to the execution of the second application on the second device, or vice-versa.

Abstract: The present teaching relates to creating and updating a user profile related to multiple devices, and synchronizing applications' sessions for the user on different devices. Upon execution of a first application on a first device, a first device ID associated with the first device and information about the first application are received. A user profile is created based on the first device ID and the information about the first application. Upon execution of a second application on a second device related to the first device, a second device ID associated with the second device and information about the second application are received. The user profile is updated based on the second device ID and the information about the second application. Further, the information about the first application is applied to the execution of the second application on the second device, or vice-versa.

Abstract: Techniques are described for providing deep linking capability from any mobile app to any other mobile app in a way that is scalable. App configuration information (including deep link information) is programmatically accumulated and provided to mobile devices in a way that enables launching or linking to mobile apps to meet expressed information needs of users. In addition, online marketplaces are described that employ such techniques to enable a wide variety of transaction types.

Abstract: An output resource identifier, such as a universal resource locator (URL), may be programmatically generated using one or more recomposition rules and decomposed parts of a source, or input, URL. The decomposed parts may be programmatically generated using one or more decomposition rules. The input and output URLs may comprise one or more of web and/or native URLs.

Abstract: As provided herein, a translated string, received from a translator for an application (e.g., an instrumented application) may be identified. The translated string may be identified based upon the translated string being associated with a service call instruction for the application. A simulated instrumented application may be generated for testing the application. The simulated instrumented application may be generated to comprise the translated string integrated into the application. The simulated instrumented application may comprise an element corresponding to the translated string. A user interface may be generated. The user interface may comprise the simulated instrumented application, the translated string visually associated with the element, and an editing functionality to edit the translated string.

Abstract: In one embodiment, a current state of an application that is executing may be identified. A plurality of next possible states to which a user can navigate from the current state may be ascertained. A history of user behavior of one or more users may be determined. Data pertaining to at least one of the plurality of next possible states may be fetched based, at least in part, upon the history of user behavior of the one or more users.

Abstract: A method for identifying a user is provided, including the following method operations: identifying at least three contact regions on a touch sensitive surface, the contact regions defined by simultaneous contact of at least three fingers of the user with the touch sensitive surface; for each contact region, determining a center point; determining distances between each of the determined center points of the contact regions; comparing the determined distances against predefined distances associated with a known user; based on the comparing, determining the user to be the known user or not the known user.

Abstract: An output resource identifier, such as a universal resource locator (URL), may be programmatically generated using one or more recomposition rules and decomposed parts of a source, or input, URL. The decomposed parts may be programmatically generated using one or more decomposition rules. The input and output URLs may comprise one or more of web and/or native URLs.

Abstract: The present teaching relates to creating and updating a user profile related to multiple devices, and synchronizing applications' sessions for the user on different devices. Upon execution of a first application on a first device, a first device ID associated with the first device and information about the first application are received. A user profile is created based on the first device ID and the information about the first application. Upon execution of a second application on a second device related to the first device, a second device ID associated with the second device and information about the second application are received. The user profile is updated based on the second device ID and the information about the second application. Further, the information about the first application is applied to the execution of the second application on the second device, or vice-versa.

Abstract: A request is received to access a user account. A geolocation of a mobile device registered with the user account is obtained directly from the mobile device. Authentication credentials for the user account are verified for correctness. A mobile device geolocation verification request is transmitted to a cellular data provider. The cellular data provider is equipped to independently determine a true geolocation region of the mobile device for comparison with the geolocation of the mobile device as obtained directly from the mobile device. A verification response to the mobile device geolocation verification request is received from the cellular data provider. The verification response indicates whether or not the geolocation of the mobile device as obtained directly from the mobile device corresponds to the true geolocation region of the mobile device. A response to the access request based on the verification response is transmitted.

Abstract: In one embodiment, a current state of an application that is executing may be identified. A plurality of next possible states to which a user can navigate from the current state may be ascertained. A history of user behavior of one or more users may be determined. Data pertaining to at least one of the plurality of next possible states may be fetched based, at least in part, upon the history of user behavior of the one or more users.

Abstract: A server-implemented method for managing packages on a client device is provided. The method initiates with receiving a content request from a client device, the content request defining a requested content item and current package data identifying one or more currently installed packages on the client device. Required packages for providing the requested content item are determined based on the content request, wherein determining the required packages includes analyzing dependencies amongst the required packages. A response to the content request is generated based on the determined required packages and the current package data, the response defining actions for providing the requested content item at the client device and actions for managing the one or more currently installed packages on the client device. The package management instructions are sent to the client device.

Abstract: In one embodiment, a request may be transmitted to a mobile device, where the request identifies one or more actions. An indication of a first time value may be received from the mobile device, where the first time value indicates a time that it has taken for the mobile device to perform the one or more actions. A device type of the mobile device may be determined. At least a second time value associated with the device type may be obtained, where the second time value indicates an approximate time that it takes for devices of the device type to perform the one or more actions. The first time value may be compared with the second time value. The mobile device may be authenticated according to a result of the comparing.

Abstract: Techniques are described for providing deep linking capability from any mobile app to any other mobile app in a way that is scalable. App configuration information (including deep link information) is programmatically accumulated and provided to mobile devices in a way that enables launching or linking to mobile apps to meet expressed information needs of users. In addition, online marketplaces are described that employ such techniques to enable a wide variety of transaction types.

Abstract: Techniques are described for providing deep linking capability from any mobile app to any other mobile app in a way that is scalable. App configuration information (including deep link information) is programmatically accumulated and provided to mobile devices in a way that enables launching or linking to mobile apps to meet expressed information needs of users. In addition, online marketplaces are described that employ such techniques to enable a wide variety of transaction types.

Abstract: A request is received to access a user account. A geolocation of a mobile device registered with the user account is obtained directly from the mobile device. Authentication credentials for the user account are verified for correctness. A mobile device geolocation verification request is transmitted to a cellular data provider. The cellular data provider is equipped to independently determine a true geolocation region of the mobile device for comparison with the geolocation of the mobile device as obtained directly from the mobile device. A verification response to the mobile device geolocation verification request is received from the cellular data provider. The verification response indicates whether or not the geolocation of the mobile device as obtained directly from the mobile device corresponds to the true geolocation region of the mobile device. A response to the access request based on the verification response is transmitted.

Abstract: A method for identifying a user is provided, including the following method operations: identifying at least three contact regions on a touch sensitive surface, the contact regions defined by simultaneous contact of at least three fingers of the user with the touch sensitive surface; for each contact region, determining a center point; determining distances between each of the determined center points of the contact regions; comparing the determined distances against predefined distances associated with a known user; based on the comparing, determining the user to be the known user or not the known user.

Abstract: A native application portion is configured for execution in a native environment. A native kernel is defined in the native environment, the native kernel including one or more native plugin services accessible by the native application portion. A non-native application portion is configured for execution in a web view context. A non-native kernel is defined in the web view context, the non-native kernel including one or more non-native plugin services accessible by the non-native application portion. A native kernel bridge service is interfaced with the native kernel, and a non-native kernel bridge service is interfaced with the non-native kernel. The native kernel bridge service and non-native kernel bridge service are interfaced with each other, enabling the non-native application portion to access the native plugin services of the native kernel, and enabling the native application portion to access the non-native plugin services of the non-native kernel.