Determining relevant information based on third party information and user interaction
By using locally stored machine learning models and third-party data sources on mobile electronic devices, combined with user device data, we provide recommendations based on correlation scores and rankings, solving the problem of small screens and insufficient information in mobile devices, and improving users Experience and information accuracy and ensure data security.
Patent Information
- Application Number
- CN202410912105.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2018-11-09
- Filing Date
- 2019-03-19
- Publication Date
- 2024-11-12
AI Technical Summary
The small screen of a mobile electronic device limits the amount of information that can be provided to the user at any given time, resulting in further interactions for the user to find relevant information and applications, and the prior art is difficult to effectively utilize third-party information and user interaction to determine relevant information.
Using a locally stored machine learning model to determine relevant information on electronic devices, using correlation scores and rankings to provide recommendations by combining data from third-party data sources and user devices, such as recommending user interface elements and future actions, using Communication between wearable devices and mobile devices to achieve this.
Improve user experience, dynamically adjust the relevance score and ranking of recommendations, it can provide more accurate information and content that users are interested in, reduce the complexity of user interaction, and use privacy policies and practices to protect the security of user data.
Smart Images

Figure CN118939155A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application is a divisional application of the invention patent application with international application number PCT / US2019 / 023027, international application date March 19, 2019, date of entry into the Chinese national phase September 27, 2020, Chinese national application number 201980022691.6, and invention name “Determining relevant information based on third-party information and user interaction”.
[0003] This application claims the benefit of U.S. Provisional Patent Application Serial No. 62 / 679,887, filed on June 3, 2018, entitled “DETERMINING RELEVANT INFORMATION BASED ON THIRD PARTY INFORMATION AND USER INTERACTIONS,” which is hereby incorporated by reference in its entirety and made a part of this U.S. utility patent application for all purposes. Technical Field
[0004] This specification generally relates to determining relevant information based on user interactions, including such as determining relevant information based on user interactions at a user device. Background Art
[0005] Mobile electronic devices (e.g., watches or smartphones) are popular and are often carried by users when performing daily and / or repetitive tasks. For example, a user of a mobile electronic device may interact with the device throughout the day by using mobile applications installed locally on the device. However, the mobile electronic device may have a small screen that limits the amount of information that can be provided to the user at any given time. Therefore, if the information provided to the user at any given time is not relevant to the user, the user may need to further interact with the mobile electronic device to find relevant information and / or applications. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Certain features of the subject technology are set forth in the appended claims. However, for purposes of explanation, several embodiments of the subject technology are set forth in the following drawings.
[0007] Figure 1 An exemplary network environment for providing relevant information based on user interaction according to one or more implementations is shown.
[0008] Figure 2 An example diagram illustrating the architecture of a system for providing relevant information based on user interaction according to one or more implementations.
[0009] Figure 3A flow chart of an exemplary process for ranking user interface (UI) elements to provide recommendations in accordance with one or more implementations is shown.
[0010] Figure 4 An exemplary graphical user interface for displaying recommendations in the form of corresponding user interface elements according to one or more implementations is shown.
[0011] Figure 5 is an exemplary block diagram of a device (eg, a wearable device) with which one or more implementations of the subject technology may be implemented.
[0012] Figure 6 An electronic system is shown with which one or more implementations of the subject technology may be implemented. DETAILED DESCRIPTION
[0013] The specific embodiments shown below are intended to be descriptions of various configurations of the subject technology and are not intended to represent the only configuration that the subject technology can be practiced. The accompanying drawings are incorporated herein and constitute a part of the specific embodiments. The specific embodiments include specific details intended to provide a thorough understanding of the subject technology. However, the subject technology is not limited to the specific details set forth herein, but can be practiced using one or more other specific implementations. In one or more specific implementations, structures and components are shown in block diagram form to avoid blurring the concept of the subject technology.
[0014] The subject system provides an architecture that enables relevant information to be determined at an electronic device using a locally stored machine learning (ML) model that provides a relevance score and / or ranking of data provided by a local data source (e.g., from an application executing on the electronic device) and an external data source from a different electronic device (e.g., an application executing on a different electronic device). In one example, the relevance score is based at least on an input signal describing a user's current environment and / or historical user behavior information. In one or more specific implementations, the subject system may be implemented by a wearable electronic device (e.g., a smart watch) that works in conjunction with another electronic device (e.g., a mobile smartphone), but it should be understood that the subject technology may be implemented on other types of devices and utilize other types of output formats (e.g., graphical, auditory, etc.).
[0015] More specifically, the specific implementations described herein provide a system that enables the use of an ML model to provide recommendations (e.g., suggested content and / or suggested future actions) based on relevance scores and / or rankings of data provided by data sources including third-party data sources (e.g., third-party applications on one or more specific electronic devices), which donate information to the system using one or more application programming interfaces (APIs). A third-party application refers to an application developed by a different entity or developer. As referred to herein, "donated" information (or "donation" or "donation information") may refer to or be discussed in conjunction with a mechanism that enables an application to provide information at least related to user activities within such application to the system for at least determining recommendations to the user. In one example, the recommendation may be provided in the form of a user interface (UI) element displayed on a specific electronic device that indicates a suggested action for the user to perform and / or provides relevant content to the user.
[0016] Figure 1 An exemplary network environment 100 for providing relevant data to an electronic device according to one or more specific implementations is shown. However, not all of the components depicted may be used in all specific implementations, and one or more specific implementations may include additional or different components than those shown in the figures. Changes in the arrangement and type of these components may be made without departing from the spirit or scope of the claims listed herein. Additional components, different components, or fewer components may be provided.
[0017] The network environment 100 includes an electronic device 120, a wearable electronic device 110, and a server 130. The network 106 may be communicatively coupled (directly or indirectly), for example, to any two or more of the electronic device 120, the wearable electronic device 110, and / or the server 130. In one or more specific implementations, the network 106 may be an interconnected network that may include the Internet or a device communicatively coupled to the Internet. For purposes of explanation, the network environment 106 is described in detail in detail below. Figure 1 1 and 12. Network environment 100 is shown as including electronic device 120, wearable electronic device 110, and server 130; however, network environment 100 may include any number of electronic devices and any number of servers.
[0018] Server 130 may be part of a computer network or server group, such as in a cloud computing or data center implementation. Server 130 may store data that can be accessed on wearable electronic device 110 and / or electronic device 120, such as photos, music, text, web pages and / or content provided therein.
[0019] The electronic device 120 may be, for example, a portable computing device such as a laptop computer, a smartphone, a peripheral device (e.g., a digital camera, a headset), a tablet device, a smart speaker, etc., or any other suitable device including, for example, one or more wireless interfaces, such as a WLAN radio device, a cellular radio device, a Bluetooth radio device, a Zigbee radio device, a near field communication (NFC) radio device, and / or other radio devices. Figure 1 In the present invention, by way of example, the electronic device 120 is depicted as a mobile smart phone device. The electronic device 120 may be and / or may include the following with respect to Figure 6 All or part of the electronic system discussed. The electronic device 120 can communicate with the wearable electronic device 110.
[0020] The wearable electronic device 110 may be, for example, a wearable device configured to be worn on a user's arm and including, for example, one or more wireless interfaces, such as a WLAN radio device, a cellular radio device, a Bluetooth radio device, a Zigbee radio device, a near field communication (NFC) radio device, and / or other radio devices. The wearable electronic device 110 may be and / or may include the following with respect to Figure 5 All or part of the electronic device in question.
[0021] Although wearable electronic device 110 is shown as being able to communicate with another device or server using network 106, in one or more specific implementations described herein, wearable electronic device 110 performs operations locally on the device itself to provide relevant data to a user (e.g., without communicating through network 106 and / or server 130).
[0022] Figure 2 Exemplary architectures 200 and 202 are shown for determining relevant data on different electronic devices using information donated from third-party sources according to one or more implementations. For purposes of explanation, architecture 200 is described as being composed of Figure 1 The wearable electronic device 110 of the embodiment of the present invention is implemented by a processor and / or memory of the wearable electronic device 110, and the architecture 202 is described as being implemented by the electronic device 120, such as by a processor and / or memory of the electronic device 120; however, the architecture 200 and / or the architecture 202 may be implemented by any other electronic device. However, not all of the components depicted may be used in all specific implementations, and one or more specific implementations may include additional or different components than those shown in the figures. Changes in the arrangement and type of these components may be made without departing from the spirit or scope of the claims listed herein. Additional components, different components, or fewer components may be provided.
[0023] As shown, to provide recommendations using donation information from applications executing on wearable electronic device 110, architecture 200 can be implemented on wearable electronic device 110. Wearable electronic device 110 includes relevance engine and recommendation provider 210, one or more wearable device applications 230, database 240, and application data manager 220.
[0024] Wearable device application 230 may donate application data 235 to database 240 using one or more APIs. Wearable device application 230 may include an application, service, widget, or program stored locally and / or running on wearable electronic device 110. Database 240 may store application data 235 in index 242. Index 242 may be a searchable index accessible to other components of architecture 200. In one example, application data 235 includes donation information from wearable device application 230. It should also be understood that application data 235 may include additional information that may be stored in index 242 in addition to donation information. In one example, information corresponding to the user's current location and / or current time may be included in application data 235 and stored in index 242.
[0025] The donation information may include information related to recent user activity and / or historical user activity associated with a specific wearable device application, and / or information related to content (including user-generated content) within a specific wearable device application. Such user activity for a specific wearable device application may include previous actions performed by a user within a specific wearable device application and / or specific information that the developer of the wearable device application has indicated (e.g., marked) as included in the donation information. In another example, the donation information also includes future actions to be performed in conjunction with a specific wearable device application, which may be determined by the specific wearable device application based at least on previous user activities such as a history of similar user activities that occur periodically (e.g., buying a specific type of coffee every day, watching a specific TV show every week, making the same commute during workdays, going to the gym on specific days of the week, reading the news at home in the evening, etc.). For example, a future action may indicate a specific location or context (e.g., at home, at the gym, at work, during commuting, etc.) to show UI elements related to a specific wearable device application and / or when to launch a specific wearable device application. Additionally, application data 235 may include information corresponding to where the user will likely be based on previous user locations and / or scheduling information (e.g., calendar events, meetings, etc.), as well as wrist detection information for determining the start and end of the user's day.
[0026] In addition, user activity may indicate the type of interaction (e.g., usage information) with the wearable device application, including, for example, dwell time, tap-through, and / or scrolling performed by the user. As mentioned herein, dwell time corresponds to how long a user hovers over a particular UI element provided by the wearable device application. Scrolling activity may correspond to how far a user scrolls down a list of UI elements provided by one or more wearable device applications. In addition, tap-through or no-tap activity corresponds to whether a user taps a UI element, which indicates whether the user wants to obtain more information related to the content provided by the UI element.
[0027] The architecture 200 includes an application data manager 220 that receives donation information and / or other information stored in an index 242 based on application data 235. In one or more specific implementations, the application data manager 220 can be implemented as a background process (e.g., a daemon) executing on the wearable electronic device 110. The application data manager 220 can also actively track updates to the index 242 and detect updated user activity information and / or other donation information included in the application data 235. In another example, the application data manager 220 can receive information (e.g., the user's current location and / or current time) directly from the application data 235 (or from the wearable device application 230) without accessing the index 242. The application data manager 220 provides information about user activity and / or other donation information to the relevance engine and recommendation provider 210 to determine relevance scores and recommendations based on rankings of relevance scores. Such recommendations can be in the form of corresponding UI elements provided for display on the wearable electronic device 110. In one example, such UI elements are provided as wearable device surface tiles that a user can interact with through touch input, gestures, and / or scrolling, etc., on the wearable device surface tiles (e.g., Figure 4 ) are presented in an interactive manner (discussed further in ).
[0028] To determine the relevance score of a particular UI element that can be provided as a recommendation, the relevance engine and recommendation provider 210 can calculate a Gaussian curve for each particular feature, where the Gaussian curve indicates a closeness value (e.g., a mean value of the Gaussian curve) and a confidence value (e.g., a variance of the Gaussian curve) for the particular feature. Examples of features associated with different types of input are discussed further below. The relevance score of a particular UI element can be determined based at least in part on the sum of different Gaussian curves for multiple different features and / or other values as discussed further below.
[0029] The average value of the above-mentioned Gaussian curve corresponds to a value indicating the closeness (e.g., correlation) of the feature to the user. The variance indicates a confidence value of the closeness of the feature to the user. In one example, a positive closeness of a feature may correspond to a user behavior such as when a user taps or clicks a UI element associated with a wearable device application. In addition, a negative closeness of a feature may correspond to a user behavior such as when a user scrolls a UI element associated with a wearable device application without any additional interaction and / or does not tap or click the UI element. In addition, for example, a high variance of a particular feature indicates that the closeness value of the feature (e.g., the average value of the Gaussian curve) has a low confidence, and a low variance of a particular feature indicates that the closeness value of the feature has a high confidence.
[0030] In addition, the relevance engine and recommendation provider 210 determine a "deviation" value for a particular UI element that can be used as part of determining the relevance score. As used herein, a deviation value refers to the likelihood or indication that a user will click or tap a particular UI element when the user is viewing the display of the wearable electronic device 110, and in at least one specific implementation, is a specific feature that is always included in determining the relevance score for the particular UI element. In order to determine the final value of the relevance score, the relevance engine and recommendation provider 210 determine the sum of the aforementioned Gaussian curve and the deviation value. In one or more specific implementations, the relevance engine and recommendation provider 210 may utilize an ML model to determine the relevance score in the manner described above. For example, the ML model may be implemented using deep neural networks, convolutional networks, unsupervised learning techniques (e.g., clustering), Bayesian networks, hidden Markov models, collaborative filtering, and / or matrix decomposition, etc.
[0031] Some non-limiting examples of the aforementioned features (e.g., for which relevance scores may be calculated) may include information describing the user's current environment and / or describing historical or likely user behavior, such as the user's current location, the current time of day or a particular time period of day (e.g., morning, afternoon, evening), recent user activity (e.g., what the user did), personal digital assistant information, requested historical subject information or other information the user searched for (e.g., stocks, weather, sports, application categories, etc.), locally stored user profile information, dwell time, scrolling activity (e.g., how far the user scrolled down a list of UI elements), tap or no-tap activity (e.g., whether the user tapped a UI element), the likelihood that the user will launch an application (e.g., based on information such as previous user activity and probability calculations), and / or when the user puts on or takes off a wearable device or device (e.g., to determine a user's typical starts and ends). The content of a particular UI element may be considered a feature that may be included in a relevance score. Other examples of features may include an application identifier for a particular application and an identifier for a particular UI element provided by an application.
[0032] In at least one specific implementation, features may be included in different groups. For example, features may be included in a "general" group or a "memory" group, wherein the "general" group includes features that are not specific to one or more specific applications, and the "memory" group includes features that are specific to specific applications. In addition, specific feature groups may include features at different levels. Examples of features included in the general group include features indicating the current location, the current time, and the time period of the day. Examples of features included in the memory group include features related to dwell time, tapping through a specific application, scrolling through a specific application executed by a user, the likelihood that the user will launch an application, an application identifier for a specific application, and a specific time and / or location. Examples of feature levels for the general group may include a first level with features related to time and / or location, and a second level of application categories (e.g., business, games, etc.). Examples of feature levels for the memory group may include a first level and a second level, wherein the first level includes features related to a specific time and / or specific location, and the second level is for features related to a specific graphical element of a specific application.
[0033] In one example, when a new UI element (e.g., a wearable device surface tile) is introduced for a particular application, features included in the general group may be weighted more than other features included in the memory group. Initially, for the new UI element, the general features may have a lower variance (e.g., indicating a higher confidence) compared to the higher variance (e.g., indicating a lower confidence) for the memory features. Over time, as users increase interactions to provide additional information related to user activity with the new UI element, the features included in the memory group may be weighted more than the features included in the general group. In addition, in one example, after the user performs an initial action on the new UI element, for each subsequent action on the new UI element, a given feature with a very high variance may be weighted more than another feature with a lower variance. In this way, the system enables features with lower confidence to explore greater opportunities and enables another feature with higher confidence to exploit greater opportunities.
[0034] In one or more specific implementations, the ML model may be further used to adjust a relevance metric used to determine a relevance score based on the behavior of the user of the wearable electronic device 110 over time. For example, when new donation information and / or other information is received for one or more features, the relevance engine and recommendation provider 210 may provide the new donation information and / or other information to the ML model to adjust a set of constants (e.g., weights) assigned to the one or more features as described above. In another example, the ML model may also adjust the value of the relevance score itself (e.g., boost). The adjusted constants and / or one or more relevance metrics are then passed back to the relevance engine and recommendation provider 210 to adjust the relevance score where applicable.
[0035] The relevance engine and recommendation provider 210 may use the corresponding relevance scores to rank multiple UI elements (e.g., corresponding to corresponding recommendations) according to an order from the highest relevance score to the lowest relevance score (or some other suitable order), and may provide one or more UI elements corresponding to the recommendations for display by the wearable electronic device 110 based on the order of relevance provided by the relevance engine and recommendation provider 210. Figure 3 An exemplary process for ranking UI elements for providing recommendations is described in more detail in . Figure 4 An exemplary UI that displays recommendations in the form of different UI elements is described.
[0036] In one or more specific implementations, based on the ranking of the above UI elements, the relevance engine and recommendation provider 210 can remove one or more UI elements from the display on the wearable electronic device 110. In addition, the relevance engine and recommendation provider 210 can also redisplay the previously removed UI elements at a subsequent time.
[0037] As further shown, the electronic device 120 (e.g., a mobile smartphone) can implement an architecture 202 for donating information from a mobile application on the electronic device 120, which can be received by the wearable electronic device 110 for providing one or more recommendations. In one or more specific implementations, the electronic device 120 includes one or more mobile applications 270, a database 280, an application data manager 250, and a suggested action UI 260.
[0038] Mobile application 270 can donate application data 275 to database 240 using one or more APIs. Mobile application 270 can include an application, service, desktop widget, or program stored locally and / or running on electronic device 120. Database 280 can store application data 275 in index 282. Index 282 can be a searchable index accessible to other components of architecture 202. In one example, application data 275 includes donation information from mobile application 270.
[0039] The architecture 202 includes an application data manager 250 that receives donation information and / or other information stored in an index 282 based on the application data 275. In one or more implementations, the application data manager 250 can be implemented as a background process (e.g., a daemon) executing on the wearable electronic device 110. The application data manager 250 can also actively track updates to the index 282 and detect updated user activity information and / or other donation information included in the application data 275. The architecture 202 can work in conjunction with the architecture 200 implemented on the wearable electronic device 110. In at least one implementation, the application data manager 250 provides information about user activity and / or other donation information to the application data manager 220 on the wearable electronic device 110 to determine relevance scores and recommendations based on ranking of relevance scores for display by the wearable electronic device 110. In addition, in one implementation, such recommendations can be received by the application data manager 250 from the wearable electronic device 110 and then provided to the suggested action UI 260. In one specific implementation, the suggested actions UI 260 may provide corresponding recommendations on the display of the electronic device 120 when the device is in the lock mode.
[0040] It should be understood that in some cases, the architecture 202 of the electronic device 120 may include a specific application that is not available on the wearable electronic device 110. In this example, the application data manager 250 may provide the application data manager 220 with donation information (e.g., from the application data 275) related to a specific action performed by a user on a specific mobile application on the electronic device 120 (e.g., the user commanding a specific item on a mobile application that is not available on the wearable electronic device 110) to (potentially) provide a recommendation for the wearable electronic device 110. In addition, in some cases, when the electronic device 120 is not required to complete the action, the electronic device 120 does not have to be close to the wearable electronic device 110.
[0041] As described above, one aspect of the present technology is to collect and use data from various sources to improve the delivery of inspirational content or any other content that may be of interest to users. The present disclosure contemplates that in some instances, such collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter accounts, home addresses, data or records related to the user's health or health level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
[0042] The present disclosure recognizes that the use of such personal information data in the present invention technology can be used to benefit users. For example, the personal information data can be used to deliver targeted content that users are more interested in. Therefore, the use of such personal information data enables users to have planned control over the content delivered. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback for individuals who use technology to pursue health goals.
[0043] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.
[0044] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to an advertising delivery service, the technology of the present invention may be configured to allow a user to choose to "opt in" or "opt out" at any time during or after registration for the service to participate in the collection of personal information data. In another example, a user may choose not to provide emotion-related data for a target content delivery service. In another example, a user may choose to limit the length of time that emotion-related data is retained, or to completely prohibit the development of basic emotional conditions. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then the user may be reminded again just before the personal information data is accessed by the application.
[0045] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.
[0046] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, content may be selected and delivered to a user by inferring preferences based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with the user, other non-personal information available to a content delivery service, or publicly available information.
[0047] Figure 3 A flowchart of an exemplary process 300 for providing recommendations according to one or more specific implementations is shown. For the purpose of explanation, this document mainly refers to Figure 1 The process 300 is described with reference to the wearable electronic device 110. However, the process 300 is not limited to Figure 1The wearable electronic device 110 of the embodiment of the present invention may be a wearable electronic device 110, and one or more blocks (or operations) of the process 300 may be performed by one or more other components of the electronic device 120 and / or by other suitable devices. Further for the purpose of explanation, the blocks of the process 300 are described herein as occurring sequentially or linearly. However, multiple blocks of the process 300 may occur in parallel. In addition, the blocks of the process 300 do not have to be performed in the order shown, and / or one or more blocks of the process 300 do not have to be performed and / or may be replaced by other operations.
[0048] like Figure 3 As shown, the wearable electronic device 110 receives application data from one or more applications, and the application data includes features related to user activities from the one or more applications (302). In one example, the application data may include information associated with applications local and / or external to the wearable electronic device 110 (e.g., wearable device applications or mobile device applications), as well as a set of signals describing the user's current environment or historical user behavior information. The application data may include information from the application data as described above in Figure 2 Donation information for such applications as discussed in , includes information of different features used to determine a relevance score associated with a UI element from the application.
[0049] Some non-limiting examples of applications local to the wearable electronic device 110 may include wearable device applications, desktop applets or programs, and the like, such as the following: calendars, reminders, alarms, timers, stopwatches, weather, stocks, sports, TV shows, maps, turn-by-turn navigation, sunrise, sunset, activity, breathing, fitness, heartbeat information, activity fitness, commuting, news, Internet of Things (IoT), home automation, digital wallets, and / or other wearable device applications that provide donation information, and the like. Applications external to the wearable electronic device include mobile applications provided by another device (e.g., electronic device 120). As another example, the application data may include information related to predicted future actions (e.g., ordering different types of coffee based at least on time and / or location). Such future actions may be based on location, context, and / or routines, such as when the user is commuting, when the user is at work, when the user is at the gym, and / or when the user is at home, and the like.
[0050] Some non-limiting examples of signals may include the following information describing the user's current environment and / or describing historical or possible user behavior: the user's current location, the current time of day, recent user activity (e.g., what the user did), personal digital assistant information, biometric data (e.g., the user's heart rate), historical topic information requested or other information the user searches for (e.g., stocks, weather, sports, application categories, etc.), locally stored user profile information, dwell time (e.g., how long the user hovers over a data item in a watch implementation), scrolling activity (e.g., how far the user scrolls down a list of elements), tap-through or no-tap-through activity (e.g., whether the user taps an element), the likelihood that the user will launch an application (e.g., based on information such as previous user activity and probability calculations), and / or when the user puts on or takes off the watch or device (e.g., to determine the user's typical starts and ends).
[0051] Wearable electronic device 110 uses the ML model to provide a relevance score for one or more user interface (UI) elements based on each of the features (304). Figure 2 As described, a Gaussian curve for each specific feature can be determined, wherein the Gaussian curve indicates a closeness value (e.g., an average value of the Gaussian curve) and a confidence value (e.g., a variance of the Gaussian curve) of the specific feature. The relevance score of a specific UI element can be determined at least in part based on the sum of different Gaussian curves of multiple different features and / or other values. Examples of signals related to features that can affect the relevance score include the order in which the user launches one or more applications on the device, and the importance of UI elements based on other factors (e.g., important people in calendar invitations). In a specific implementation of the touch interface, the wearable electronic device 110 tracks previous activities, and if the user shows a history of not tapping the UI element or not interacting with the UI element, the UI element can score lower. In addition, the wearable electronic device 110 can also determine (e.g., using a sensor that detects motion) when the user is viewing the screen of the wearable electronic device 110 but not interacting with the UI element, and can reduce the score of the UI element. Similarly, when the wearable electronic device detects that the user is viewing the screen and does interact with the UI element, the score of the UI element can be improved. When a new signal is received, the score can be dynamically updated / recalculated. As mentioned above, these new signals can be fed into the ML model to adjust the final relevance score. Figure 2 As discussed, the respective weights of features may be adjusted over time, which may affect the relevance score.
[0052] Wearable electronic device 110 sorts / ranks the UI elements based on the relevance score of each UI element (306). For example, the sorting can be performed by score and time order (time). In another example, other sorting schemes can be used (e.g., from lowest relevance to highest relevance (reverse relevance order)). Wearable electronic device 110 provides one or more UI elements as output based at least in part on the ranking (308). In one example, the output is provided to wearable electronic device 110 for rendering a UI to a user (hereinafter referred to as the UI element). Figure 4 In one example, the output may be provided when the wearable electronic device 110 is in a locked mode. In another example, the output may be in an auditory format (e.g., a personal digital assistant). In yet another example, the output may be in a text format (e.g., an instant messaging application).
[0053] Figure 4 An exemplary graphical user interface for displaying ranked data items according to one or more specific implementations is shown. The relevance engine and recommendation provider 210 of the wearable electronic device 110 may provide a user interface 400 for presenting UI elements 410, 420, 430, and 440 for display, and the UI elements 410, 420, 430, and 440 may include corresponding content for display. In one or more specific implementations, the UI elements 410, 420, 430, and 440 may each be a corresponding wearable device surface block displayed by the wearable electronic device 110 based on at least donation information and / or other information from application data (e.g., application data 235, application data 275). Each UI element may have a different relevance score, and the relevance scores are ranked by the relevance engine and recommendation provider 210. In this example, the UI elements 410, 420, 430, and 440 are sorted from the highest relevance score to the lowest relevance score. However, it should be understood that the UI elements 410, 420, 430, and 440 may be related to Figure 4 The examples shown in the figure may be arranged in one or more different orders. Furthermore, even for the purpose of explanation, Figure 4 While four UI elements are shown in FIG. 2 , the relevance engine and recommendation provider 210 may also display any number of ranked data items (or subsets thereof) simultaneously.
[0054] Figure 5 is an exemplary block diagram of a wearable device 500 (e.g., a smart watch) according to one or more implementations of the subject technology. The wearable device 500 may be Figure 1Wearable electronic device 110 is shown and / or may be a part thereof. Wearable device 500 may include processing subsystem 502, storage subsystem 504, input / output 506, RF interface 508, connector interface 510, power subsystem 512, environmental sensor 514, and band sensor 516. Wearable device 500 may also include other components (not explicitly shown).
[0055] In many implementations, the wearable device 500 can keep time and display time, essentially acting as a watch or the like. The time can be displayed in analog or digital format, depending on the device, its settings, and (in some cases) the user's preferences. Typically, the time is displayed on a digital display stack that forms part of the exterior of the device.
[0056] The storage subsystem 504 may be implemented, for example, using magnetic storage media, flash memory, other semiconductor memory (e.g., DRAM, SRAM), or any other non-transitory storage media or combination of media, and may include volatile media and / or non-volatile media. In some implementations, the storage subsystem 504 may store media items such as audio files, video files, images, or artwork files; information about user contacts (names, addresses, phone numbers, etc.); information about appointments and events scheduled by the user; memos; and / or other types of information, examples of which are described below. In some implementations, the storage subsystem 504 may also store one or more application programs to be executed by the processing subsystem 502 (e.g., video game programs, personal information management programs, media playback programs, interface programs associated with specific host devices and / or host device functions, etc.).
[0057] Input / output 506 may include any combination of input devices and output devices. A user may operate an input device of input / output 506 to invoke a function of wearable device 500, and may view, listen to, and / or otherwise experience output from wearable device 500 via an output device of input / output 506.
[0058] Examples of output devices include a display 520, a speaker 522, and a tactile output generator 524. The display 520 may be implemented using compact display technologies such as LCD (liquid crystal display), LED (light emitting diode), OLED (organic light emitting diode), etc. In some implementations, the display 520 may be combined with a flexible display element or a curved glass display element, allowing the wearable device 500 to conform to a desired shape. One or more speakers 522 may be provided using small speaker technology, including any technology capable of converting electronic signals into audible sound waves. In some implementations, the speaker 522 may be used to produce tones (e.g., beeps or rings), and may, but need not be capable of reproducing sounds such as speech or music with any particular fidelity. The tactile output generator 524 may be, for example, a device that converts electronic signals into vibrations; in some implementations, the vibrations may be strong enough to be felt by a user wearing the wearable device 500, but not so strong as to produce a distinctive sound.
[0059] Examples of input devices include microphone 526, touch sensor 528, and camera 529. Microphone 526 may include any device that converts sound waves into electrical signals. In some implementations, microphone 526 may be sensitive enough to provide a representation of a specific word spoken by a user; in other implementations, microphone 526 may be used to provide an indication of the overall ambient sound level without necessarily providing a high-quality electronic representation of a specific sound.
[0060] The touch sensor 528 may include, for example, a capacitive sensor array having the ability to locate a contact at a specific point or area on the surface of the sensor, and in some cases, having the ability to distinguish multiple concurrent contacts. In some implementations, the touch sensor 528 may be overlaid on the display 520 to provide a touch screen interface, and the processing subsystem 504 may convert touch events (including taps and / or other gestures made using one or more contacts) into specific user inputs based on the content currently displayed on the display 520. In some implementations, the touch sensor 528 may also determine the location of the touch on the cover glass. The touch sensor may be incorporated into or on the display stack to determine the location of the touch. The touch sensor may be self-capacitive in some implementations, mutual-capacitive in other implementations, or a combination thereof.
[0061] The camera 529 may include, for example, a compact digital camera including an image sensor such as a CMOS sensor and an optical component (e.g., a lens) arranged to focus an image onto the image sensor, together with a control logic component operable to use the imaging component to capture and store still images and / or video images. The images may be stored, for example, in the storage subsystem 504, and / or transmitted by the wearable device 500 to other devices for storage. Depending on the specific implementation, the optical component may provide a fixed focus or a variable focus; in the latter case, auto focus may be provided. Zero, one, or more cameras may be provided depending on the specific implementation.
[0062] In some implementations, input / output 506 can provide output to an auxiliary device such as a headset, and / or receive input from an auxiliary device. For example, audio jack 530 can be connected to an auxiliary device via an audio cable (e.g., a standard 2.5mm or 3.5mm audio cable). Audio jack 530 can include an input path and / or an output path. Thus, audio jack 530 can provide audio to an auxiliary device, and / or receive audio from an auxiliary device. In some implementations, a wireless connection interface can be used to communicate with an auxiliary device.
[0063] The processing subsystem 502 may be implemented as any electronic device capable of processing, receiving or transmitting data or instructions. The processing subsystem 502 may include one or more integrated circuits. For example, the processing subsystem 502 may include one or more of the following: one or more single-core or multi-core microprocessors or microcontrollers, central processing units (CPUs), application-specific integrated circuits (ASICs), digital signal processors (DSPs), or additional combinations of such devices. In operation, the processing subsystem 502 may control the operation of the wearable device 500. In various specific implementations, the processing subsystem 502 may execute various programs in response to program code, and may maintain multiple programs or processes that are executed simultaneously. At any given time, some or all of the program code to be executed may reside in the processing subsystem 502 and / or in a storage medium such as the storage subsystem 504.
[0064] Through appropriate programming, the processing subsystem 502 can provide various functions for the wearable device 500. For example, in some specific implementations, the processing subsystem 502 can execute an operating system (OS) 532 and various applications for interfacing with a host device, such as a phone interface application 534, a text interface application 536, and / or a media interface application 538.
[0065] In some implementations, the processing subsystem 502 may also execute a host security process 560 that provides support for establishing and maintaining an authenticated communication session with a host device. User data 562 may include any information specific to a user, such as identification information, user-specified settings and preferences, customized information (e.g., contacts, predefined text messages), and any other data or content related to the user.
[0066] The RF (radio frequency) interface 508 can allow the wearable device 500 to communicate wirelessly with various host devices. The RF interface 508 may include RF transceiver components (such as an antenna and supporting circuits) to enable data communication via a wireless medium, for example, using WiFi (IEEE 502.5 series standards), (a series of standards published by Bluetooth SIG, Inc.) or other protocols for wireless data communications. The RF interface 508 may be implemented using a combination of hardware components (e.g., drive circuits, antennas, modulators / demodulators, encoders / decoders, and other analog signal processing circuits and / or digital signal processing circuits) and software components. In some implementations, the RF interface 508 may provide near field communication ("NFC") capabilities, such as implementing the ISO / IEC 18092 standard, etc.; NFC may support wireless data exchange between devices within a very short range (e.g., 20 cm or less). Multiple different wireless communication protocols and associated hardware may be incorporated into the RF interface 508.
[0067] The connector interface 510 may allow the wearable device 500 to communicate with various host devices via a wired communication path, such as using a universal serial bus (USB), a universal asynchronous receiver / transmitter (UART), or other protocols for wired data communication. In some implementations, the connector interface 510 may provide a power port, thereby allowing the wearable device 500 to receive power, such as to charge an internal battery. For example, the connector interface 510 may include a connector such as a micro USB connector or a custom connector and supporting circuitry.
[0068] Environmental sensors 514 may include various electronic, mechanical, electromechanical, optical, or other devices that provide information about external conditions surrounding wearable device 500. In some implementations, sensors 514 may provide digital signals to processing subsystem 502, such as in a streaming fashion as needed or in response to a poll by processing subsystem 502. Any type and combination of environmental sensors may be used; accelerometer 542, magnetometer 544, gyroscope sensor 546, and GPS receiver 548 are shown by way of example.
[0069] Sensors 516 may include various electronic, mechanical, electromechanical, optical or other devices that provide information to wearable device 500, such as a clasp sensor 550 that can detect when clasp members are engaged with each other or when they are disengaged from each other. For another example, one or more crown sensors 552 may be provided to detect input from the crown. Crown sensors 552 may also include motion sensors, accelerometers, pressure sensors (e.g., piezoelectric devices), etc.
[0070] The power subsystem 512 can provide power and power management capabilities for the wearable device 500. For example, the power subsystem 512 can include a battery 540 (e.g., a rechargeable battery) and associated circuitry to distribute power from the battery 540 to other components of the mobile device 500 that require power. In some implementations, the power subsystem 512 can also include circuitry for charging the battery 540, for example when the connector interface 510 is connected to a power source. In some implementations, the power subsystem 512 can include a "wireless" charger such as an inductive charger for charging the battery 540 without relying on the connector interface 510. An inductive charging base can transmit power to an inductive receiver within the device to charge the battery of the device.
[0071] It should be appreciated that wearable device 500 is exemplary and that variations and modifications are possible.
[0072] Figure 6 An electronic system 600 is shown that can be utilized to implement one or more implementations of the subject technology. The electronic system 600 can be Figure 1 The electronic device 130 and / or server 130 shown may be and / or may be a part thereof. The electronic system 600 may include various types of computer-readable media and interfaces for various other types of computer-readable media. The electronic system 600 includes a bus 608, one or more processing units 612, a system memory 604 (and / or cache), a ROM 610, a permanent storage device 602, an input device interface 614, an output device interface 606, and one or more network interfaces 616, or a subset and variant thereof.
[0073] The bus 608 generally represents all system buses, peripheral busses, and chipset buses that communicatively connect the many internal devices of the electronic system 600. In one or more implementations, the bus 608 communicatively connects the one or more processing units 612 with the ROM 610, the system memory 604, and the permanent storage device 602. The one or more processing units 612 retrieve instructions to be executed and data to be processed from these various memory units in order to perform the processes disclosed in the present subject matter. In different implementations, the one or more processing units 612 can be a single processor or a multi-core processor.
[0074] ROM 610 stores static data and instructions required by one or more processing units 612 and other modules of electronic system 600. On the other hand, permanent storage device 602 can be a read-write memory device. Permanent storage device 602 can be a non-volatile memory unit that stores instructions and data even when electronic system 600 is turned off. In one or more specific implementations, a mass storage device (such as a magnetic disk or optical disk and its corresponding disk drive) can be used as permanent storage device 602.
[0075] In one or more implementations, a removable storage device (such as a floppy disk, a flash drive, and its corresponding disk drive) can be used as the permanent storage device 602. Like the permanent storage device 602, the system memory 604 can be a read-write memory device. However, unlike the permanent storage device 602, the system memory 604 can be a volatile read-write memory, such as a random access memory. The system memory 604 can store any of the instructions and data that one or more processing units 612 may need at runtime. In one or more implementations, the processes disclosed in the subject matter are stored in the system memory 604, the permanent storage device 602, and / or the ROM 610. The one or more processing units 612 retrieve instructions to be executed and data to be processed from these various memory units in order to perform the processes of one or more implementations.
[0076] The bus 608 is also connected to an input device interface 614 and an output device interface 606. The input device interface 614 enables a user to transmit information and select commands to the electronic system 600. Input devices that can be used with the input device interface 614 may include, for example, an alphanumeric keyboard and a pointing device (also referred to as a "cursor control device"). The output device interface 606 may, for example, enable the display of images generated by the electronic system 600. Output devices that can be used with the output device interface 606 may include, for example, a printer and a display device, such as a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flexible display, a flat panel display, a solid-state display, a projector, or any other device for outputting information. One or more specific implementations may include a device that acts as both an input device and an output device, such as a touch screen. In these specific implementations, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, voice, or tactile input.
[0077] Finally, if Figure 6 As shown, bus 608 also couples electronic system 600 to one or more networks and / or to one or more network nodes, such as via one or more network interfaces 616. Figure 1 . In this manner, electronic system 600 may be part of a computer network, such as a LAN, a wide area network ("WAN"), or an intranet, or may be part of a network of networks, such as the Internet. Any or all components of electronic system 600 may be used with the subject disclosure.
[0078] Implementations within the scope of the present disclosure may be implemented in part or in whole using a tangible computer-readable storage medium (or multiple tangible computer-readable storage media of one or more types) programmed with one or more instructions. Tangible computer-readable storage media may also be non-transitory in nature.
[0079] Computer-readable storage media can be any storage media that can be read, written, or otherwise accessed by a general or special computing device, including any processing electronics and / or processing circuitry capable of executing instructions. For example, without limitation, computer-readable media can include any volatile semiconductor memory, such as RAM, DRAM, SRAM, T-RAM, Z-RAM, and TTRAM. Computer-readable media can also include any non-volatile semiconductor memory, such as ROM, PROM, EPROM, EEPROM, NVRAM, flash memory, nvSRAM, FeRAM, FeTRAM, MRAM, PRAM, CBRAM, SONOS, RRAM, NRAM, racetrack memory, FJG, and Millipede memory.
[0080] In addition, the computer-readable storage medium may include any non-semiconductor memory, such as optical disk storage, magnetic disk storage, magnetic tape, other magnetic storage devices, or any other medium capable of storing one or more instructions. In one or more specific implementations, the tangible computer-readable storage medium may be directly coupled to the computing device, while in other specific implementations, the tangible computer-readable storage medium may be indirectly coupled to the computing device, for example, via one or more wired connections, one or more wireless connections, or any combination thereof.
[0081] Instructions can be directly executable, or can be used to develop executable instructions. For example, instructions can be implemented as executable or non-executable machine code, or can be implemented as high-level language instructions that can be compiled to produce executable or non-executable machine code. In addition, instructions can also be implemented as data, or can include data. Computer executable instructions can also be organized in any format, including routines, subroutines, programs, data structures, objects, modules, applications, applets, functions, etc. As recognized by those skilled in the art, the details including but not limited to the number, structure, sequence and organization of instructions can be significantly different without changing the underlying logic, function, processing and output.
[0082] Although the above discussion mainly involves microprocessors or multi-core processors that execute software, one or more implementations are performed by one or more integrated circuits such as ASICs or FPGAs. In one or more implementations, such integrated circuits execute instructions stored on the circuits themselves.
[0083] Those skilled in the art will recognize that the various illustrative frames, modules, elements, parts, methods and algorithms described herein can be implemented as electronic hardware, computer software or a combination of the two. In order to illustrate this interchangeability of hardware and software, various illustrative frames, modules, elements, parts, methods and algorithms have been generally described above according to functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. The technician can implement the described functionality in different ways for each specific application. Various parts and frames can be arranged differently (e.g., arranged in different orders, or divided in different ways) without departing from the scope of the subject technology.
[0084] It should be understood that the specific order or the hierarchical structure of the frame in the process disclosed by the present invention are the illustration of exemplary methods. Based on the design preferred requirements, it should be understood that the specific order or the hierarchical structure of the frame in the process can be rearranged or all the frames shown are executed. Any frame in these frames can be executed simultaneously. In one or more specific implementations, multitasking and parallel processing may be advantageous. In addition, the division of each system component in the above-mentioned specific implementation should not be understood as requiring such division in all specific implementations, and it should be understood that program components and systems can be generally integrated together in a single software product or encapsulated in multiple software products.
[0085] As used in this specification and any claims of this patent application, the terms "base station", "receiver", "computer", "server", "processor" and "memory" all refer to electronic devices or other technical devices. These terms exclude people or groups of people. For the purpose of this specification, the term "display" or "displaying" means displaying on an electronic device.
[0086] As used herein, the phrase "at least one of" following a list of items, any of which is separated by the terms "and" or "or", modifies the list as a whole, rather than each member of the list (i.e., each item). The phrase "at least one of" does not require selection of at least one of each item listed; rather, the phrase allows for a meaning that includes at least one of any one item and / or at least one of any combination of items and / or at least one of each item. For example, the phrase "at least one of A, B, and C" or "at least one of A, B, or C" each refers to only A, only B, or only C; any combination of A, B, and C; and / or at least one of each of A, B, and C.
[0087] The predicate words "configured to," "operable to," and "programmed to" do not imply any particular tangible or intangible modification of a subject matter but are intended to be used interchangeably. In one or more specific implementations, a processor configured to monitor and control an operation or component may also mean that the processor is programmed to monitor and control the operation or that the processor is operable to monitor and control the operation. Likewise, a processor configured to execute code may be interpreted as a processor programmed to execute code or operable to execute code.
[0088] Phrases such as aspect, this aspect, on the other hand, some aspects, one or more aspects, a specific implementation, this specific implementation, another specific implementation, some specific implementations, one or more specific implementations, an embodiment, this embodiment, another embodiment, some embodiments, one or more embodiments, configuration, this configuration, other configurations, some configurations, one or more configurations, subject technology, disclosure, the present disclosure, other variations thereof, etc. are for convenience and do not mean that the disclosure involving such one or more phrases is essential to the subject technology, nor does it mean that such disclosure applies to all configurations of the subject technology. Disclosures involving such one or more phrases may apply to all configurations or one or more configurations. Disclosures involving such one or more phrases may provide one or more examples. Phrases such as aspect or some aspects may refer to one or more aspects and vice versa, and this applies similarly to the other aforementioned phrases.
[0089] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" or as an "example" is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, to the extent that the terms "including," "having," and the like are used in the specification or claims, such terms are intended to be inclusive, in a manner similar to the way the term "comprising" is interpreted when used as a transitional word in a claim.
[0090] All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be made available to the public regardless of whether the disclosure is explicitly stated in the claims. Pursuant to 35 U.S.C. §112, paragraph 6, no claim element shall be construed unless the element is expressly stated using the phrase “means for” or, in the case of a method claim, the element is stated using the phrase “step for”.
[0091] The previous description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications of these aspects are apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are intended to make the full scope consistent with the language claims, wherein reference to elements in singular values is not intended to mean "only one", but refers to "one or more", unless specifically noted. Unless otherwise specifically stated, the term "some" refers to one or more. Male pronouns (e.g., his) include female and neutral (e.g., her and its), and vice versa. Titles and subtitles (if any) are used only for convenience and do not limit the subject disclosure.
Claims
1. A device comprising: Memory; as well as at least one processor, the at least one processor being configured to: receiving application data from one or more applications, the application data comprising characteristics associated with user activity from the one or more applications; providing a relevance score for each of the one or more watch face user interface UI elements based on the features associated with the user activity using a machine learning (ML) model; as well as At least one watch face UI element of the one or more watch face UI elements is provided as output based at least in part on the relevance score. 2 . The apparatus of claim 1 , wherein the relevance score is based at least in part on a sum of corresponding Gaussian curves. 3 . The apparatus of claim 1 , wherein the relevance score is further based on a value indicating a likelihood that a user will click or tap a particular watch face UI element. The apparatus of claim 1 , wherein the feature comprises a location or time based signal.
5. The device of claim 1, wherein the application data is provided by the application using one or more application programming interfaces. The apparatus of claim 1 , wherein the features are included in different groups.
7. The apparatus of claim 6, wherein the different groups include a set of features shared across the applications and a second set of features specific to a particular application.
8. The device of claim 6, wherein the device comprises a wearable electronic device, and each watch face UI element is provided for display by the wearable electronic device according to a ranking.
9. A method comprising: receiving application data from one or more applications, the application data comprising characteristics associated with user activity from the one or more applications; providing a relevance score for each of the one or more table user interface (Ul) elements based on the features associated with the user activity using a machine learning (ML) model; as well as At least one table UI element of the one or more table UI elements is provided as output based at least in part on the relevance score.
10. A computer program product comprising code stored in a non-transitory computer readable storage medium, the code comprising: code for receiving application data from one or more applications, the application data comprising one or more characteristics related to user activity from the one or more applications; code for using a machine learning (ML) model to provide a corresponding relevance score for each of one or more user interface (UI) elements based on the one or more features; as well as Code for providing as output at least one UI element of the one or more UI elements based at least in part on the respective relevance scores of the one or each UI element.
11. The device according to claim 1 further includes a display, wherein the at least one processor is configured to provide the output by displaying a scrollable list of the one or more dial UI elements on the display, and the display order of the scrollable list is determined based on sorting the one or more UI elements according to the relevance score. The method of claim 9 , wherein the feature comprises a location or time based signal.
13. The method of claim 9, wherein the application data is provided by the application using one or more application programming interfaces. The method of claim 9 , wherein the features are included in different groups.
15. The method of claim 14, wherein the different groups include a set of features that are shared across the applications and a second set of features that are specific to a particular application.
16. The method according to claim 9, further comprising: A scrollable list of the one or more watch face UI elements is displayed on the display, wherein a display order of the scrollable list is determined based on sorting the one or more UI elements according to the relevance scores.
17. The computer program product of claim 10, wherein the characteristic comprises a location or time based signal.
18. The computer program product of claim 10, the application data provided by the application using one or more application programming interfaces.
19. The computer program product of claim 10, wherein the features are included in different groups.
20. The computer program product of claim 19, wherein the different sets include a set of features that are shared across the applications and a second set of features that are specific to a particular application.
