JP7142661B2 - Viewing related use interface objects - Google Patents

Description

The disclosed embodiments generally relate to user interfaces for electronic devices.

Advanced personal electronic devices may have small form factors. Exemplary personal electronic devices include, but are not limited to tablets and smartphones. The use of such personal electronic devices includes the display and manipulation of user interface objects on display screens designed to be small to complement personal electronic devices.

Exemplary user interface objects include digital images, videos, text, icons, control elements such as buttons, and other graphics. As used herein, the term "icon" refers to an image used to represent and launch an application, consistent with its ordinary meaning in the art. Further, a "widget," as used in the art to refer to a simplified view of an application, constitutes an icon for the purposes of this disclosure.

Existing user interfaces on reduced-size personal electronic devices may be inefficient because they may require multiple actions by the user before the appropriate information is presented.

Techniques are disclosed for presenting user interface objects on a personal electronic device.

1 illustrates an exemplary personal electronic device; FIG.

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

Fig. 3 shows an exemplary logical structure of a user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

1 illustrates an exemplary computing system; FIG.

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 13 illustrates an exemplary user interface;

FIG. 4 illustrates an exemplary process for displaying user interface objects;

In the following disclosure and description of examples, reference is made to the accompanying drawings, which are shown by way of illustration of specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be implemented and structural changes may be made without departing from the scope of the present disclosure.

FIG. 1 is a diagram illustrating an exemplary personal electronic device 100 (hereinafter, device 100). In the illustrated example, device 100 includes body 102 . Device 100 may have a touch-sensitive display screen (hereinafter touchscreen) 104 .

The touch screen 104 may be the back of a touch sensor panel implemented using any desired touch sensing technology such as mutual capacitive touch sensing, self-capacitive touch sensing, resistive touch sensing, projected scanning touch sensing, etc. or Display devices such as liquid crystal displays (LCD), light emitting diode (LED) displays, organic light emitting diode (OLED) displays, etc., which are partially or wholly disposed on the front side, may be mentioned. The touch screen 104 allows a user to hover near the touch-sensitive panel with one or more fingers or other objects and touch the touch-sensitive panel to perform various functions.

In some embodiments, device 100 can have one or more input mechanisms 106 and 108 . Input mechanisms 106 and 108, if included, may be touch-sensitive. Examples of touch-sensitive input mechanisms include touch-sensitive buttons and touch-sensitive surfaces. Input mechanisms 106 and 108, if included, may be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. Body 102, which may include a bezel, may have predetermined areas on the bezel that act as input mechanisms. In some embodiments, device 100 can have an attachment mechanism. When such attachment mechanisms are included, they allow device 100 to be attached to, for example, clothing, jewelry, and other wearable accessories. For example, attachment mechanisms can be attached to hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, pants, belts, shoes, purses, backpacks, and the like.

In some embodiments, device 100 can have one or more pressure sensors (not shown) to detect force or pressure applied to touch screen 104 . Force or pressure applied to touch screen 104 is used as an input to device 100 to perform any desired action, such as making selections, entering or exiting menus, displaying additional options/actions, etc. can be executed. Different actions can be performed based on the amount of force or pressure applied to the touch screen 104 . One or more pressure sensors can also be used to determine the location where force is being applied to the touch screen 104 .
1. View related user interface objects

FIG. 2 is a diagram illustrating an exemplary device 100 worn by a user 201 walking to his car 202 . When user 201 moves device 100 to the viewing position, device 100 automatically displays user interface screen 203 on touch screen 104 . In some embodiments, the display elements of touchscreen 104 are inactive until user 201 moves device 100 to the viewing position, which means the display elements of touchscreen 104 are off or off. It means to appear to be. In some embodiments, regardless of whether device 100 is held in an up, down, or sideways orientation by user 201, the information displayed is directed to device 100 so that it is in the proper viewing orientation. can rotate the display content of the touch screen 104 (eg, between landscape and portrait modes).

User interface screen 203 now contains the user interface objects that device 100 has determined are most relevant to the user. In particular, screen 203 includes an icon 204 for unlocking vehicle 202, useful to user 201 when the user approaches his vehicle. Screen 203 also includes a map icon 205 (which may be useful when user 201 begins driving) for accessing traffic information. Screen 203 may also include icons 206 useful for referencing upcoming calendar events and providing destination information. The size of displayed icons can be related to their relevance. On screen 203, icon 204 is larger than icons 205 and 206 because device 100 has determined that unlocking car 202, which is provided via icon 204, is more relevant.

This user interface display is notable in prioritizing and displaying a manageable subset of icons to the user 201 even though more user interface objects are available for display. . This user interface is also made available to user 201 without any user interface navigation input from the user other than an arm lift (e.g., without requiring user 201 to press a power on or equivalent button). In this manner, device 100 reduces the amount of user input required to initiate appropriate user interface operations. This advantage is not trivial. This is because, in particular, compared to smartphones and other electronic devices, the device 100 has a relatively small display screen size, which may hinder the user's navigation of larger user interface environments. be.

The number of related user interface objects in a given situation may exceed the number that can reasonably be displayed together on touch screen 104 (such as three as shown in FIG. 2). In this case, device 100 may prioritize the most relevant icons (as determined by a computer-based relevance algorithm on device 100) for initial display. In some embodiments, the user can cause the remaining associated icons to appear on the display using input mechanism 106 or 108 . In some embodiments, the user can cause the remaining associated icons to be displayed on the display using the touchscreen 104 (such as by swiping the touchscreen 104 with a touch object).

FIG. 3 is a diagram illustrating the display of related icons on multiple user interface screens. In the illustrated example, a user interface screen 301 is displayed on the device 100 in response to upward movement of the device. Screen 301 includes icons 302-304 (which may be icons 204-206 (FIG. 2) in some examples) representing associated applications. User interface screen 311 is displayed on device 100 in response to rotation of input mechanism 108 in direction 306 . Screen 311 may display several additional related icons 312 - 314 that are less relevant than those shown in screen 301 . In response to further rotation of input mechanism 108 in the same direction 306 , device 100 may display user interface screen 321 . Screen 321 includes another set of related icons 322 - 324 that are less relevant than those shown in screen 311 and, as a result, less relevant than those in screen 301 . Input mechanism 108 may be a rotatable crown. In this manner, a user can navigate between multiple sets of related user interface objects (eg, icons) on device 100 .

The user can activate the application corresponding to the displayed icon by touching the displayed icon (for example, by finger tapping). As used herein, launching an application means that the application runs in the foreground of device 100 and is displayed on the screen. FIG. 4 illustrates this aspect. In the illustrated example, a user interface screen 401 is displayed on the device 100 in response to movement of the device toward the viewing position. Screen 401 includes icon 402 representing a messaging application (eg, supporting short message service (SMS)), and icons 403 and 404 representing other applications, having five unread messages. In response to tapping icon 402 with a touch object (eg, finger 405 ), device 100 launches the corresponding messaging application and displays unread message 412 on user interface screen 411 .

Under some conditions of use, a user may wish to navigate from a messaging application to another related application. For example, the user may wish to navigate to the music and maps applications previously represented by icons 403 and 404 on screen 401 . Device 100 may allow navigation between these applications directly without returning to screen 401 first. Specifically, while screen 411 is displayed, rotating input mechanism 108 in direction 414 causes device 100 to display a music player represented by icon 403 on screen 421 . Screen 421 may include music playback controls 423 . Further rotation of input mechanism 108 in direction 414 while screen 421 is displayed causes device 100 to display the map application represented by icon 404 on screen 431 . Screen 431 may include traffic information 432 .

In some embodiments, screens 411, 421, and 431 each include a visual aid (paging dot 415, 425, and 435, etc.). Other visual aids (such as scroll bars and transitions between screens) are also used to help the user identify the currently displayed user interface screen relative to the larger set of available user interface screens. can do.

The example user interface screens shown in FIGS. 2-4 are primarily concerned with efficient display of associated user interface objects. However, it should be noted that the device 100 may contain more user interface objects that should be accessible to the user, even if their current relevance is not readily identifiable. For example, a user may have an impulse to want to play a game. Device 100 allows a user to navigate beyond related user interface objects to other user interface objects. FIG. 5 illustrates this aspect.

In FIG. 5, user interface screen 501 is displayed on device 100 in response to movement of the device to a viewing position. Screen 501 includes icons 502-504 (which may be icons 203-205 (FIG. 2) in some examples) representing associated applications. In the illustrated example, device 100 has determined that only three user interface objects (ie, icons 502-504) are currently relevant. Accordingly, in response to rotation of input mechanism 108 in direction 505 , device 100 displays user interface screen 511 , which displays other user interface objects available for user selection on device 100 . have. The icons displayed on screen 511 may be the user's favorite icons, which means that the icons on screen 511 are a predetermined subset of the user interface objects available on device 100. . Upon further rotation of input mechanism 108 in direction 505 , device 100 displays user interface screen 521 , which includes icons representing all applications available on device 100 . The size of the icons displayed on screen 521 may be too small for user navigation, so in response to further rotation of input mechanism 108 in direction 505 device 100 displays screen 531 . This has the effect of enlarging a subset of the icons on screen 521, which are displayed at a larger size for user interaction.

The navigation of the user interface described with reference to FIG. 5 can be logically organized according to the logical structure 600 shown in FIG. In the example shown in FIG. 6, x-axis 601 and y-axis 602 are coplanar with the surface of the touch screen screen (FIG. 1) of device 100, and z-axis 603 is the x/axis formed by axes 601 and 602. perpendicular to the y-plane. Plane 604 corresponds, in one example, to user interface screen 501 (FIG. 5), plane 605 to user interface screen 511 (FIG. 5), and plane 607 to user interface screens 521 and 531 (FIG. 5). handle. More specifically, screen 521 (FIG. 5) can correspond to a view of the entire content of plane 607, and screen 531 (FIG. 5) is an enlarged view of the content of plane 607 (i.e., an enlarged view of the contents of plane 607). subset). In another example, planes 604, 607, 608 may correspond to user interface screens 301, 311, and 321 of FIG. 3, respectively. Movement of the input mechanism can be used to select a particular plane of information (ie, a screen of icons) to display on device 100 . For example, by rotating the input mechanism 108, a screen with different icons can be displayed on the display device 100, for example, in the same manner as shown in FIG.
2. Determining relevant user interface objects

Consistent with its ordinary meaning, the phrase "related icon" is used here to refer to any user interface icon that is related to or appropriately applicable to the matter at hand. In the example of FIG. 2, the icon for unlocking the vehicle application is relevant because when the user approaches his car, he may desire to drive the car. Device 100 can determine relevance using computer instructions (eg, algorithms) that consider different inputs (including sensor inputs, application data, operating system data).

FIG. 7 illustrates an exemplary computing system 700 that forms device 100 in some embodiments. Computing system 700 includes components for determining and displaying relevant user interface objects. In the illustrated example, computing system 700 is operatively coupled (such as GPS sensor 720, acceleration sensor 722, orientation sensor 724, gyroscope 726, light sensor 728, and/or combinations thereof) to various sensors ( It has an I/O section 704 that can be connected). I/O section 704 also supports Wi-Fi, Bluetooth, Near Field Communication (“NFC”), cellular and other wireless communication technologies for receiving application and operating system data. can be connected to the communication unit 718 by. Additionally, computing system 700 may have a bus 702 coupling I/O section 704 together with one or more computer processors 706 and memory section 708 . Memory portion 708 can store computer-executable instructions (eg, representing algorithms) and/or data for determining and displaying associated user interface objects. One or more of these components may be part of an integrated chip or so-called system-on-chip. Additionally, the I/O section 704 can be connected to an input mechanism 714 . The I/O section 704 can be connected to one or more input buttons 716 . The I/O section 704 can be connected to a display 710 that can have a touch sensitive component 712 and, optionally, a touch pressure sensitive component 713 .

Sensors and communication units of computing system 700 can provide information to identify associated user interface objects. For example, GPS sensor 720 can determine the location and movement of a user, while communication unit 718 can receive information about the location and identity of nearby vehicles (eg, vehicle 202 in FIG. 2). . Acceleration sensor 722, orientation sensor 724, and gyroscope 726 can also detect movement of the device. Optionally, the outputs of GPS sensor 720 , accelerometer 722 , orientation sensor 724 and/or gyroscope 726 can be interpreted by motion processor 730 . Computer-executable instructions in processor 706 and memory unit 708 can use some or all of this information to determine that the user is approaching his vehicle. The instructions of processor 706 and memory 708 are based on application data and/or operating system data (including metadata) stored in memory 708 to determine that an application has been installed to interact with the user's vehicle. can also be determined. In this way, the association algorithm of the device 100 can determine that the car interaction application is relevant to the user at that time. Further, device 100 can conclude, based on the same data, that a map application will also be relevant to the user.

Communications unit 718 may also receive other information that affects the relevance of user interface objects. For example, the communication unit can detect nearby devices that are identical or similar, such as other wearable devices of the same design. The communication unit can also detect non-identical units running the same operating system as the device 100 (such as smartphones and tablets of the same brand). The communication unit can also identify different devices that support communication according to a common protocol. These protocols can include wireless protocols such as Wi-Fi, Bluetooth, NFC, and others. These protocols are, for example, operating environment service protocols (Apple® AirPlay® and AirDrop®), home automation service protocols (e.g. Phillips® Lighting and Nest®), authentication service protocols (e.g. airport clearance and subway fares), point of sale service protocols (e.g. grocery store checkout), and software-based service protocols such as You can also do Algorithms used by device 100 to identify relevant user interface objects can take into account these inputs provided by communication unit 718 .

In addition, communication unit 718 can receive application and operating system data that informs the association. For example, a messaging application can receive incoming messages via SMS or Wi-Fi services, thereby becoming relevant. As another example, the relevance algorithm of device 100 can use calendar data and cellular system time to determine which event reminders are relevant. Additionally, the relevance algorithm of device 100 can consider the content of application and operating system data when determining relevance. For example, the algorithm may consider an incoming message that includes a reference to a particular time (e.g., "see you at 3pm") to become more relevant as that time (i.e., 3pm) approaches. can be done.

In some embodiments, user interface objects may be related in groups. That is, application data (including metadata) may specify that whenever user interface object A is relevant, user interface object B is also relevant. For example, drivers typically enjoy music, so a music application can be tied to the car's interactive application in this way. Since drivers typically want traffic and/or route information, map applications can also be linked to car interactive applications in this way.

In some embodiments, the relevance algorithm used by the device 100 can be adaptive, meaning that the results of the algorithm can change based on past user behavior. For example, an algorithm can recognize a user's commute based on the user's driving pattern during weekday mornings. In this way, device 100 can prioritize specific traffic information for display in the morning. As another example, if a user repeatedly activates one particular radio application during his commute than other available radio applications, device 100 may identify that radio application as being more relevant. , the icon can be displayed whenever the user unlocks his or her car.

In some embodiments, the computing system 700 may include biometric sensors such as photoplethysmograph (PPG) sensors, electrocardiogram (ECG) sensors, and/or health-related sensors such as galvanic skin response (GSR) sensors. can. Device 100 may receive input from one or more of these sensors that provide health-related information. For example, device 100 can use PPG sensor information to alert a user of abnormal breathing rate, blood pressure, and/or oxygen saturation. As another example, device 100 may use an electrocardiogram sensor to alert the user of an arrhythmia. As yet another example, the device 100 may use a GSR sensor to detect moisture on the user's skin indicating perspiration and prioritize a thermostat application for display on the device 100 . These sensors can also be used to facilitate biometric identification and authentication of users.

Sensors in computing system 700 can detect when the system (eg, device 100) is placed in a viewing position. For example, accelerometer 722 and/or motion sensor 730 can detect when computing system 700 is lifted, lowered, or shaken. These sensors can detect forward and backward rotation of the wrist. In some embodiments, lifting computing device 700 is interpreted as placing the device in a viewing position. In some embodiments, lifting and rotating computing device 700 is interpreted as placing the device into a viewing position. In some embodiments, the duration between lifting and lowering of computing device 700 is interpreted as placement of the device in the viewing position.

The algorithm used by device 100 to identify relevant user interface objects for display may employ one or more of the aforementioned aspects of the device (eg, computing system 700). That is, the algorithm can consider combinations of inputs in determining relevance, including: Position, movement (including posture, orientation, tilt, acceleration, and velocity), ambient conditions (including light, time, temperature, user health), application data (incoming phone calls, incoming messages), , including upcoming calendar events).

For example, the device 100 exceeds a threshold (e.g., 10 mph, 20 mph, 25 mph, 30 mph, 40 mph, 50 mph, 55 mph, 60 mph, 65 mph, etc.) If moving at speed, the device 100 may determine that the user of the device is commuting and icons corresponding to navigation applications are highly relevant. In such a situation, the device 100 may also determine that icons representing in-vehicle entertainment applications are relevant if available onboard equipment is in communication with the communication unit of the device 100 . As another example, device 100 may determine that icons representing health-related applications are more relevant when biometric sensors and motion sensors detect movement representing exercise. As another example, device 100 may determine that calendar events scheduled to occur after a certain amount of time (eg, 15 minutes, 30 minutes, 1 hour, 1 day, 1 week, etc.) are more relevant. be able to. Optionally, the device 100 may take into account other variables, such as the distance between the current location of the device and the location of the event, as well as the current weather, in determining event relevance. can. That is, for example, device 100 may determine that a nearby event scheduled in 15 minutes is less relevant than an event scheduled in 1 hour but 30 miles away.
3. Exemplary User Interaction

A user can interact with the user interface of device 100 . These interactions can include shortcuts for invoking application functions. This aspect will be described with reference to FIGS.

In the example of FIG. 8, device 100 has just received an incoming SMS message and provided tactile feedback to the user. In response to the haptic feedback, the user causes device 100 to display user interface screen 801 by lifting device 100 to the viewing position. Screen 801 includes icons 802-804 representing applications determined to be relevant to the user at the time. Icon 802 represents an unread SMS message. Icon 803 represents an upcoming calendar event. Icon 804 represents available traffic information. Since recently received SMS messages rank highest in relevance, icon 802 is displayed in a large fashion.

Message icon 802 has the highest relevance, so when the user rotates input mechanism 108 in direction 805 , device 100 launches the corresponding messaging application and displays unread SMS messages on user interface screen 811 . 812 is displayed. In response to further rotation of input mechanism 108 in direction 805 , device 100 displays calendar event 822 on user interface screen 821 in the calendar application represented by icon 803 . In response to further rotation of input mechanism 108 in direction 805 , device 100 displays traffic information provided by the map application (corresponding to icon 804 ) on user interface screen 831 .

From screen 811, the user may tap SMS message 812 to invoke user interface screen 901 shown in FIG. Referring to FIG. 9, screen 901 includes icon 902 for responding to SMS message 812 . Screen 901 also includes icon 903 for generating an alarm at 3:00 pm as suggested by SMS message 812 . Similarly, when screen 821 (FIG. 8) is displayed, the user can tap calendar event 822 to invoke user interface screen 911 shown in FIG. Screen 911 includes an icon 912 for messaging an event participant (eg, Larry). Screen 911 also includes icons 913 for obtaining navigation to the event location. Finally, when screen 831 (FIG. 8) is displayed, the user can tap map 832 to invoke user interface screen 921 shown in FIG. Screen 921 includes icons 922 for setting navigation waypoints and icons 923 for obtaining turn-by-turn navigation instructions.

In some embodiments, device 100 distinguishes between short and long taps on touchscreen 104 (FIG. 1), e.g., invokes screen 901 only after a long tap on screen 811 (FIG. 8). be able to. For purposes of this disclosure, a short tap refers to a short touch that touches the touchscreen 104 (FIG. 1) and then releases the touch. A long tap refers to touching the touchscreen 104 (FIG. 1) longer before releasing the touch. Device 100 may consider touches that exceed a predetermined duration to be long taps (and touches of shorter duration to be short taps). In some embodiments, device 100 can identify the degree of pressure on touch screen 104 . That is, device 100 can detect the strength of a touch object (eg, a user's finger) on touch screen 104 . Therefore, device 100 can invoke screen 901 only after the user taps screen 811 (FIG. 8) with sufficient pressure.

In some embodiments, the device 100 can distinguish between a short glance and a longer gaze at the touchscreen 104 (FIG. 1). A short glance can be characterized by a short duration between the lifting of the device to the viewing position and the subsequent lowering of the device. Longer gazes can be characterized by periods in which the equipment is relatively stationary in viewing position. Device 100 may respond differently to short glances and longer gazes. This aspect is illustrated in FIG. In the example of FIG. 10, a user interface screen 1001 is displayed in response to movement of the device 100 to the viewing position by the user. However, because message 1002 arrived just before device 100 was lifted into the viewing position, user interface screen 1001 emphasizes displaying unread SMS message 1002 from the contact instead of displaying multiple related user interface objects. do. If the user maintains the device 100 in the viewing position for more than a predetermined amount of time, the device 100 changes the screen 1001 to a user interface screen 1011 (showing a plurality of icons representing relevant user interface objects available on the device 100). ). From screen 1011 , the user can tap icon 1012 with finger 1013 to return to SMS message 1002 . In this manner, device 100 allows the user to easily glance at incoming messages.
4. An exemplary user interface.

11-16 illustrate exemplary user interfaces that device 100 can display over the course of a day based on relevance. In FIG. 11, the device 100 determines that the user has just woken up and displays an appropriate greeting 1102 saying "Good morning." The device 100 may be activated after a time of day, user interaction with an alarm clock application (e.g., the user has just turned off the alarm), and/or, for example, after a period of user inactivity. , movement of the device that indicates walking. Device 100 may rank greeting 1102 as the most relevant icon to display to the user when the user wakes up. Because of its high relevance, greeting 1102 is highlighted in user interface screen 1101, which means that greeting 1102 can be the largest icon displayed, or the only icon displayed. do. Note, however, that if the greeting 1102 is the only icon displayed, other non-iconic user interface elements (such as the current time) can still be displayed on-screen.

User interface screen 1111 shows another exemplary user interface that device 100 may display when the user wakes up. A screen 1111 includes an icon 1112 indicating the current time. The icon 1113 can have a circumferential outline 1113 that indicates the remaining snooze time. Optionally, icon 1112 has a background indicating the current weather, eg, blue for mild weather and gray for inclement weather. Screen 1111 may also include icons 1115 that indicate unread messages that the user should pay attention to.

FIG. 12 illustrates a user interface screen 1201 that can show additional related user interface objects after the user wakes up. Screen 1201 includes associated icons 1202-1204. Icon 1202 may correspond to a health application and show sleep information, such as the duration of sleep by the user. Icon 1203 can correspond to calendar information, such as the time remaining before the next calendar event. Icons 1204 may correspond to additional calendar information, such as all-day events.

User interface screen 1211 shows additional relevant user interface objects that device 100 may display after the user wakes up. Screen 1211 includes associated icons 1212 and 1213 . Icon 1212 may correspond to a weather application that indicates the weather at the device's current location. Optionally, icon 1212 may indicate the weather at locations the user has traveled to so far this morning, such as the weather at the user's place of work. Additionally, icon 1213 may indicate that the user should start their morning commute in 45 minutes. The device 100 makes this determination, for example, based on the first event on the calendar for today, where the user typically travels on weekday mornings, and the estimated travel time to that destination based on distance and traffic information. be able to.

User interface screen 1221 shows additional relevant user interface objects that device 100 can display later in the morning. Exemplary user interface screen 1221 includes associated icons 1222-1224. Weather conditions icon 1222 may display the same information previously displayed by icon 1212 . However, while in screen 1211 icon 1212 was the most relevant icon, in screen 1221 that relevance has been replaced by traffic icon 1223 . Traffic icon 1223 indicates a traffic alert and is displayed as the largest icon. The reason is that device 100 determined that information about accidents along the user's normal morning commute was highly relevant at that time. Screen 1221 also indicates that the user's commute should start in 10 minutes, given the traffic information received by device 100 (caused by an accident), rather than the 45 minutes indicated previously by icon 1213. contains an icon 1224 indicating that the

Referring to FIG. 13, screen 1301 shows an icon 1302 for unlocking the user's car when the user approaches his car. Based on the decreasing distance between the device 100 and a car near the user, the device 100 can display an icon 1302. FIG. Optionally, screen 1301 can include additional associated icons, such as those described in connection with FIG. Device 100 may display user interface screen 1311 when lifted into a viewing position while the user is in his/her car. Screen 1311 displays the estimated time of arrival at work (“ETA”) (ie, icon 1312), the time until the next meeting on the user's calendar (ie, icon 1313), and a music player (ie, icon 1314). ), as represented by These are relevant to the user on his way to work. The device 100 can determine that the user is driving based on GPS movement and/or communication with an in-vehicle telematics system (eg, via Bluetooth or cable connection). . Device 100 may determine that the user is driving to work based on historical information about the user's commute patterns. As the user gets closer to work, the estimated time of arrival will become less relevant and the information will be displayed with less importance. For example, on user interface screen 1321 , music icon 1322 is displayed in a larger format than ETA icon 1324 . The time until the next meeting on the calendar information remains relevant, so icon 1323 can continue to display this time. If the meeting is off-site (ie, physically far from the user's work place), the device 100 can mark the reminder as relevant based on GPS sensor and calendar information.

Referring to FIG. 14, later in the day, the user of device 100 may visit a store such as a coffee shop. At screen 1401, the device 100 can display an electronic payment icon 1402 that allows the user to authorize a purchase at the coffee shop. The device 100 can determine proximity to coffee shops based on GPS information and application data provided by third party applications such as map applications or Starbucks® applications. Device 100 may also determine proximity to a coffee shop based on wireless communication with the store's point of sale system, such as via near field communication with a payment reader. Additionally, on screen 1401, device 100 can display icons 1403 that indicate proximity of contacts (eg, friends) at the coffee shop. On screen 1411, the device 100 displays an icon 1412 indicating a new incoming message, an icon 1413 counting down to an upcoming meeting, and an icon 1414 suggesting that the user should take the stairs to the meeting location for additional exercise. , can be displayed. If the user is late for a meeting, the device 100 can remind the user of it. For example, on screen 1421, the device 100 displays an icon 1422 alerting the user that the user is eight minutes late for a meeting on the calendar, and a new incoming message to the user (some of which may be the user's Icons 1422 and 1424 may be displayed to indicate that the meeting may be triggered by the absence of a meeting.

Referring to FIG. 15, the device 100 can display relevant information as the workday nears its end. In user interface screen 1501, device 100 may display an ETA to the user's home (ie, icon 1502) and an ETA to the user's spouse's home (ie, icon 1503). On user interface screen 1511, device 100 continues to display the user's ETA to home (ie, icon 1512), a music application that changes the music in the user's car (ie, icon 1513), and a stress level indicator. (ie icon 1514) can be displayed. The device 100 can calculate the user's stress level based on sensor inputs including, for example, PPG, ECG and GSR sensor readings. When the user arrives home and looks at the device 100, the device 100 can display an icon 1522 for unlocking the wirelessly enabled front door. Device 100 can also display icons 1524 for controlling electronics in the home, such as lighting and fireplace settings with Wi-Fi enabled lighting and HVAC controllers. The device 100 can also display an icon 1523 that indicates a dinner event.

Referring to FIG. 16, the device 100 can display relevant information as the day ends. In user interface screen 1601, device 100 may display icon 1602 suggesting that the user needs to go to bed soon, for example, based on the user's usual sleep time and calendared activities for the next morning. can be done. Device 100 may also display icons 1604 for controlling the television based on the user's habit of watching television at night. Device 100 can also display icons 1603 for lighting control based on the user's normal end-of-day routine. As the user's usual bedtime continues to approach, the device 100 displays a summary of the user's physical activity for the day (i.e., icon 1612 indicating that the user has met 75% of their goals for the day), and an alarm for the next morning. An alarm clock icon 1613 for setting the can be displayed. Device 100 may also reduce the amount of user interface objects displayed at the end of the day. For example, as shown in screen 1621, device 100 may display a single icon 1622 suggesting sleep. Further, icons 1622 can be displayed using wavelengths of light that are less likely to interfere with the user's sleep patterns. In this manner, device 100 may avoid keeping the user awake and/or waking a sleeping user.

Optionally, device 100 can be configured to permanently display a watch face. This aspect is described with respect to FIG. In the illustrated example, device 100 displays user interface screen 1701 in response to lifting the device to the viewing position. In screen 1701 a clock 1702 is displayed with an associated icon 1703 . As device 100 identifies additional relevant user interface objects, they can be displayed on top of touch screen 104 (FIG. 1) around clock 1702 (additional relevant user interface objects on screens 1711 and 1721). (as indicated by icons 1712 and 1703). In this way, the user can configure the device 100 to emphasize the time keeping function.

FIG. 18 shows an exemplary process 1800 that may be performed by device 100 to display associated user interface objects. At block 1810, the device 100 obtains input from a motion sensor indicating movement of the device toward the viewing position. In some embodiments, the motion can be an upward motion. At block 1820, device 100 acquires additional sensor data. Such sensor data may include GPS location information, light information, motion information, and/or accelerometer information. At block 1830, the device 100 obtains application or operating system data. Such data can be obtained by communication links such as Wi-Fi, Bluetooth, or NFC. At block 1840, the device 100 identifies relevant user interface objects for display to the user based on the sensor data and application/OS data. Device 100 can also rank related user interface objects. At block 1850, the most relevant user interface objects are displayed to the user. At block 1860, the device 100 receives input representing movement of the input mechanism. In response, at block 1870, device 100 displays icons representing the user's favorite applications available on the device. At block 1880, device 100 receives additional input representing movement of the input mechanism. In response, at block 1890, device 100 displays icons representing all applications available on the device.

7, the memory portion 708 of the computing system 700, when executed by one or more computer processors 706, performs the user interface techniques described above, including process 1800 (FIG. 18), on the computer processors, for example. It can be a non-transitory computer-readable storage medium storing computer-executable instructions that can be executed. For use by an instruction execution system, device, or device, such as a computer-based system, a system that includes a processor, or any other system capable of fetching instructions from and executing instructions from the instruction execution system, device, or device. Or in connection therewith, the computer-executable instructions may be stored and/or transferred in any non-transitory computer-readable storage medium. For the purposes of this document, "non-transitory computer-readable storage medium" means any medium capable of storing or storing computer-executable instructions for use by or in connection with an instruction execution system, device, or apparatus. It can be used as a medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic, optical, and/or semiconductor storage. Examples of such storage include magnetic discs, CDs, DVDs or optical discs based on Blu-ray technology, as well as RAM, ROM, EPROM, flash memory and solid state memory. Computing system 700 is not limited to the components and configuration of FIG. 7, but may include other or additional components in multiple configurations.

Although the present disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are intended to be included within the scope of the disclosure and examples defined by the appended claims.

Claims (22)

In an electronic device containing a display,
detecting the user's approach to a vehicle associated with the user while the user is using the electronic device;
displaying on the display a first icon for unlocking the vehicle in response to detecting that the user is approaching the vehicle;
In response to unlocking the vehicle via the first icon, on the display of the electronic device, the user has repeatedly taken in the vehicle while previously using the vehicle. displaying a second icon corresponding to the action;
A method, including detecting an input while displaying the first icon;
2. The method of claim 1, further comprising initiating a process to unlock the vehicle in response to detecting the input. 3. The method of claim 2, wherein said input is directed to said first icon. 4. The method of claim 2 or 3, wherein initiating the process of unlocking the vehicle comprises unlocking the vehicle. 5. The method of any one of claims 2-4, wherein initiating the process of unlocking the vehicle comprises launching an application for performing the process of unlocking the vehicle. Displaying a plurality of icons on the display of the electronic device prior to displaying the first icon, wherein the plurality of icons does not include the first icon. ,
6. The method of any one of claims 1-5, wherein displaying the first icon comprises updating the plurality of displayed icons to include the first icon. 7. The method of claim 6, wherein the plurality of icons are selected from among a plurality of icons available for more display in response to each of the plurality of icons being determined to be relevant. . 8. The method of claim 7, wherein the plurality of icons available for more display includes the first icon. 9. The method of claims 6 to 8, wherein the plurality of displayed icons are updated to include the first icon in response to determining that an application for unlocking the vehicle has increased relevance. A method according to any one of paragraphs. 10. The method of claims 6 to 9, wherein updating the displayed plurality of icons to include the first icon includes replacing a separate one display of the plurality of icons with the first icon. A method according to any one of paragraphs. 11. The method of any one of claims 1-10, further comprising determining relevance of the first icon using the location of the electronic device and the location of the vehicle. 12. The method of claim 11, wherein the relevance of the first icon increases as the distance between the location of the electronic device and the location of the vehicle decreases. 13. A method according to claim 11 or 12, wherein said relevance of said first icon is determined using identification information of said vehicle. 14. A method according to any one of claims 11 to 13, wherein said relevance of said first icon is determined using a relevance algorithm. 15. The method of any preceding claim, further comprising determining increased relevance of the first icon in response to detecting that the user is approaching the vehicle. . 16. The method of claim 15, further comprising increasing a display size of the first icon in response to determining that the relevance of the first icon has increased. From claim 1, wherein the first icon is associated with a first application for unlocking the vehicle and the second icon is associated with a second application different from the first application. 17. The method of any one of 16. 18. The method of any one of claims 1-17, wherein the electronic device is a wearable device. 19. The method of any one of claims 1-18, wherein the first icon is displayed in response to detecting input from a movement-based motion sensor of the electronic device. A computer program for causing a computer to carry out the method according to any one of claims 1 to 19. a memory storing a computer program according to claim 20;
and one or more processors capable of executing said computer programs stored in said memory. An electronic device comprising means for carrying out the method according to any one of claims 1 to 19.

Images