Device, method and graphical user interface for presenting representations of media containers

文档序号：1631672 发布日期：2020-01-14 浏览：17次中文

阅读说明：本技术 用于呈现媒体容器的表示的设备、方法和图形用户界面 (Device, method and graphical user interface for presenting representations of media containers ) 是由 O·莫拉格于 2018-03-21 设计创作，主要内容包括：一种设备接收用于登记音乐共享的请求。在接收到所述请求之后,所述设备显示登记用户界面,所述登记用户界面包括同时显示由第一用户创建的多个播放列表的表示和针对所述多个播放列表的隐私设置。所述隐私设置具有默认值。所述登记用户界面包括对应于所述多个播放列表中的第一播放列表的第一示能表示和对应于所述多个播放列表中的第二播放列表的第二示能表示。所述设备接收将所述隐私设置从对应的默认隐私设置改变为用户指定的隐私设置的一个或多个用户输入。在完成登记之后,所述设备基于针对所述多个播放列表的所述隐私设置向与所述第一用户具有预先确定关系的其他用户提供对所述第一用户的所述多个播放列表的访问。在显示媒体浏览用户界面时,设备接收用于显示所述媒体浏览用户界面的不同视图的请求。响应于所述请求,所述设备同时显示第一媒体容器的表示和第二媒体容器的表示。根据确定所述第一媒体容器满足所述第一用户与其具有预先确定关系的其他用户已与所述相应媒体容器接合的接合标准,所述设备显示针对所述第一媒体容器的所述表示的接合标记以指示其他用户已与所述第一媒体容器接合。根据确定所述第一媒体容器不满足针对所述第一用户的所述接合标准,所述设备显示所述第一媒体容器的所述表示而不显示针对所述第一媒体容器的所述表示的接合标记。一种电子设备在显示单元上显示针对媒体应用程序的媒体浏览用户界面。在显示所述媒体浏览用户界面时,所述电子设备经由一个或多个输入设备接收用于显示最近播放的媒体容器的请求。响应于接收到用于显示所述最近播放的媒体容器的所述请求,所述电子设备显示被标记为最近已由用户播放的媒体容器的多个表示,其中媒体容器的所述多个表示包括基于请求与言语指令的一部分匹配的媒体的回放的所述言语指令来生成的第一媒体容器。设备显示媒体接合用户界面,所述媒体接合用户界面包括针对第一用户已满足针对其的接合标准的第一媒体容器和第二媒体容器的表示。所述第一用户与所述第一媒体容器和所述第二媒体容器的所述接合对于与所述第一用户具有预先确定关系的其他用户是可见的。所述设备检测用于隐藏所述第一用户与相应媒体容器的所述接合的请求。根据确定所述请求对应于所述第一媒体容器,所述设备改变所述第一媒体容器的所述表示的外观而不改变所述第二媒体容器的所述表示的所述外观。对所述第一媒体容器的所述表示的所述改变指示所述第一用户与所述第一媒体容器的所述接合被隐藏而不能被与所述第一用户具有所述预先确定关系的其他用户查看。(A device receives a request to register for music sharing. After receiving the request, the device displays a check-in user interface that includes displaying a representation of a plurality of playlists created by the first user and privacy settings for the plurality of playlists simultaneously. The privacy settings have default values. The enrollment user interface includes a first affordance corresponding to a first playlist in the plurality of playlists and a second affordance corresponding to a second playlist in the plurality of playlists. The device receives one or more user inputs that change the privacy settings from the corresponding default privacy settings to user-specified privacy settings. After completing enrollment, the device provides access to the plurality of playlists of the first user to other users having a predetermined relationship with the first user based on the privacy settings for the plurality of playlists. While displaying a media browsing user interface, a device receives a request to display different views of the media browsing user interface. In response to the request, the device simultaneously displays a representation of the first media container and a representation of the second media container. In accordance with a determination that the first media container satisfies engagement criteria that the first user has a predetermined relationship with other users having a predetermined relationship with the first media container engaged with the respective media container, the device displays an engagement indicium for the representation of the first media container to indicate that other users have engaged with the first media container. In accordance with a determination that the first media container does not satisfy the engagement criteria for the first user, the apparatus displays the representation of the first media container without displaying an engagement label for the representation of the first media container. An electronic device displays a media browsing user interface for a media application on a display unit. While displaying the media browsing user interface, the electronic device receives, via one or more input devices, a request to display a recently played media container. In response to receiving the request to display the recently played media container, the electronic device displays a plurality of representations of media containers marked as recently played by a user, wherein the plurality of representations of media containers includes a first media container generated based on verbal instructions requesting playback of media matching a portion of the verbal instructions. The device displays a media engagement user interface that includes representations of a first media container and a second media container for which the first user has satisfied engagement criteria. The engagement of the first user with the first media container and the second media container is visible to other users having a predetermined relationship with the first user. The device detects a request to hide the engagement of the first user with a respective media container. In accordance with a determination that the request corresponds to the first media container, the apparatus changes an appearance of the representation of the first media container without changing the appearance of the representation of the second media container. The change to the representation of the first media container indicates that the engagement of the first user with the first media container is hidden from view by other users having the predetermined relationship with the first user.)

1. A method, the method comprising:

at a device comprising a display and one or more input devices:

receiving, via the one or more input devices, a request to register for music sharing, wherein registering for music sharing allows a first user to share music with other users;

after receiving the request, displaying a check-in user interface on the display, the check-in user interface including displaying a representation of a plurality of playlists created by the first user and privacy settings for the plurality of playlists concurrently, wherein the privacy settings for the plurality of playlists have default values, and the check-in user interface includes:

a first affordance corresponding to a first playlist of the plurality of playlists created by the first user; and

a second affordance corresponding to a second playlist of the plurality of playlists created by the first user;

while displaying the privacy settings for the plurality of playlists, receiving, via the one or more input devices, one or more user inputs that change the privacy settings for one or more of the plurality of playlists from corresponding default privacy settings to user-specified privacy settings; and

after completion of enrollment, providing other users having a predetermined relationship with the first user access to the plurality of playlists of the first user based on the privacy settings for the plurality of playlists, comprising:

in accordance with a determination that the one or more user inputs detected while displaying the registered user interface change the default privacy settings for the first playlist, providing other users connected with the first user access to the first playlist of the first user based on the user-specified privacy settings; and is

In accordance with a determination that the one or more user inputs detected while displaying the registered user interface change the default privacy settings for the second playlist, providing access to the second playlist of the first user to other users connected with the first user based on the user-specified privacy settings.

2. The method of claim 1, wherein the enrollment user interface includes a third affordance that, when activated, changes the default values of the privacy settings for the plurality of playlists.

3. The method of any of claims 1-2, wherein the representations of the plurality of playlists are scrollable.

4. The method of any of claims 1-3, wherein the default values of the privacy settings for the plurality of playlists indicate that the plurality of playlists are private.

5. The method of claim 4, wherein the one or more user inputs change the privacy settings for the first playlist from private to public, and wherein access to the first playlist is provided to other users in response to the privacy settings for the first playlist changing from private to public.

6. The method of any of claims 1-5, wherein the first affordance includes a first toggle switch displayed adjacent to the representation of the first playlist, and wherein the first toggle switch is in one of the following states:

a first state indicating that the first playlist is private; and

a second state indicating that the first playlist is public.

7. The method of any of claims 1-6, further comprising, during the registering:

receiving a request to create a profile;

in accordance with a determination that the request is for creating a public profile, creating a public profile for the first user; and

in accordance with a determination that the request is for creating a private profile, a private profile is created for the first user.

8. The method of claim 7, wherein receiving the request to create the profile comprises receiving one or more of a name, a username, and a photograph.

9. The method of any of claims 7 to 8, further comprising:

after registration is completed:

receiving a follow-up request from a second user when the profile for the user is a private profile; and

displaying a notification on the display indicating the follow-up request, wherein the notification includes:

a first affordance that, when activated, accepts the follow request;

a second affordance that, when activated, denies the follow request; and

a third affordance that, when activated, displays a user profile for the second user.

10. The method of claim 9, further comprising:

receiving a user selection of one of the first affordance and the second affordance;

after receiving the user selection:

in accordance with a determination that the user selection includes a selection of the first affordance, providing the second user access to the first playlist of the first user based on the user-specified privacy setting; and

in accordance with a determination that the user selection includes a selection of the second affordance, denying the second user access to the plurality of playlists of the first user.

11. The method of any of claims 1-10, further comprising, during the registering:

displaying on the display a plurality of representations of other users that do not have a predetermined relationship with the first user;

displaying relationship affordances corresponding to the other users on the display, wherein each respective relationship affordance, when activated, triggers establishment of a predetermined relationship with a user corresponding to the affordance.

12. The method of any of claims 1-11, displaying on the display a plurality of representations of other users that do not have a predetermined relationship with the first user, wherein:

selecting the representations of the other users for inclusion in the plurality of representations of other users based on a comparison of the music preferences of the first user to music preferences of a plurality of candidate users other than the first user,

causing less than all of a first subset of the candidate users to be included in the plurality of representations of users based on similarity of their music preferences to the music preferences of the first user; and

excluding from the plurality of representations of users a second subset of less than all of the candidate users based on the similarity of their music preferences to the music preferences of the first user; and is

The music preferences of the users in the first subset of the candidate users are closer to the music preferences of the first user than the users in the second set of the candidate users.

13. The method of any of claims 1-12, comprising displaying on the display a plurality of representations of other users that do not have a predetermined relationship with the first user, wherein displaying the representations of the other users comprises simultaneously displaying:

a graphical indication of music preferences of a first user of the other users along with information identifying the first user; and

a graphical indication of music preferences of a second user of the other users along with information identifying the second user.

14. The method of any of claims 12 to 13, comprising displaying on the display a plurality of representations of other users that do not have a predetermined relationship with the first user, wherein displaying the representations of the other users comprises:

arranging the representations of the other users based on a degree of similarity between the music preferences of the first user and the music preferences of the other users who do not have a predetermined relationship with the first user.

15. The method of any of claims 11 to 14, comprising displaying on the display a plurality of representations of other users that do not have a predetermined relationship with the first user, wherein displaying the representations of the other users comprises:

selecting the other user based on one or more of:

a geographic location of the first user; and

a social network associated with the device.

16. The method of any of claims 1-15, further comprising, during the enrolment, providing the first user with an affordance controlling settings for requiring approval from the first user before allowing the user to establish the predetermined relationship with the first user; and

after registration, in response to receiving a request from a respective other user to establish the predetermined relationship with the first user:

in accordance with a determination that the setting is in a first state in which approval by the first user is required to establish the predetermined relationship, displaying a notification that the respective other user has requested establishment of the predetermined relationship with the first user; and

in accordance with a determination that the setting is in a second state in which approval by the first user is not required to establish the predetermined relationship, establishing the predetermined relationship with the first user.

17. The method of any of claims 1 to 16, further comprising:

receiving, via the one or more input devices, a request to establish a verified account for the first user; and

transmitting the request to a verification entity that determines whether the request satisfies a verification criterion.

18. The method of any of claims 1 to 17, further comprising:

displaying on the display a link to music created by the first user.

19. The method of any of claims 1 to 18, further comprising:

in response to receiving the request to register for music sharing and prior to displaying the registration user interface:

determining whether the first user is subscribed to a subscription-based music streaming service;

in accordance with a determination that the first user is subscribed to the subscription-based music streaming service, displaying the registered user interface; and

in accordance with a determination that the first user is not subscribed to the subscription-based music streaming service, forgoing display of the enrollment user interface.

20. The method of any of claims 1-19, further comprising, prior to completing enrollment music sharing:

in accordance with a determination that the first user has not completed registration, displaying a notification of registration of music sharing.

21. An electronic device, the electronic device comprising:

a display;

an input device;

one or more processors;

a non-transitory memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing or causing the performance of any of the methods of claims 1-20.

22. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with a display and an input device, cause the electronic device to perform or cause performance of any of the methods of claims 1-20.

23. An electronic device, the electronic device comprising:

a display;

an input device; and

apparatus for performing or causing the performance of any one of the methods of claims 1-20.

24. A graphical user interface on an electronic device with a display, an input device, a non-transitory memory, and one or more processors to execute one or more programs stored in the non-transitory memory, the graphical user interface comprising user interfaces displayed in accordance with any of the methods of claims 1-20.

25. An information processing apparatus for use in an electronic device having a display and an input device, comprising:

apparatus for performing or causing the performance of any one of the methods of claims 1-20.

26. A method, the method comprising:

at a device comprising a display and one or more input devices:

displaying a media browsing user interface for a first user on the display;

while displaying the media browsing user interface, receiving, via the one or more input devices, input corresponding to a request to display a different view of the media browsing user interface; and

concurrently displaying, in response to the input, a plurality of representations of containers of media items within the media browsing user interface: a representation of a first media container and a representation of a second media container, wherein:

in accordance with a determination that the first media container satisfies engagement criteria for the first user, wherein the engagement criteria for a respective media container includes criteria that the first user has engaged media in the respective media container with other users having a predetermined relationship therewith, displaying engagement indicia for the representation of the first media container to indicate that the first user has engaged one or more media items in the first media container with users having the predetermined relationship therewith;

in accordance with a determination that the first media container does not satisfy the engagement criteria for the first user, displaying the representation of the first media container without displaying an engagement label for the representation of the first media container;

in accordance with a determination that the second media container satisfies the engagement criteria for the first user, displaying an engagement indicium for the representation of the second media container to indicate that the user with whom the first user has the predetermined relationship has engaged one or more media items in the second media container; and

in accordance with a determination that the second media container does not satisfy the engagement criteria for the first user, displaying the representation of the second media container without displaying an engagement label for the representation of the second media container.

27. The method of claim 26, wherein simultaneously displaying the plurality of representations comprises:

displaying a first set of the plurality of representations with respective splice marks; and

displaying a second set of the plurality of representations without corresponding splice marks.

28. The method of any of claims 26-27, wherein simultaneously displaying the plurality of representations comprises:

determining whether the other user has engaged with one or more of the first media container and the second media container.

29. The method of claim 28, wherein the engagement criteria for determining that the respective other user has engaged the respective media container include one or more of the following criteria:

when the device receives a criterion that is met when a second device has played the respective media container more than a threshold amount, indicating that the respective other user has listened to the respective media container more than the threshold amount;

a criterion that is satisfied when the device receives that the second device associated with the respective other user has received input indicating a preference for the respective media container;

criteria that are met when the device receives an indication that the second device associated with the respective other user has received input corresponding to a request to add the respective media container or a media item from the respective media container to a media library;

criteria that are met when the device receives an indication that the second device associated with the respective other user has downloaded the respective media container or a media item from the respective media container.

30. The method of any of claims 26-29, wherein the engagement criteria for determining that respective other users have engaged with respective media containers include a criterion that is met when a number of interactions by the other users with the respective media containers meets a threshold amount of interactions.

31. The method of claim 30, further comprising:

in accordance with a determination that the engagement criteria include explicit criteria, determining whether the number of interactions is greater than a first threshold; and

in accordance with a determination that the engagement criteria include implicit criteria, determining whether the number of interactions is greater than a second threshold, wherein the second threshold is greater than the first threshold.

32. The method of any of claims 26-31, wherein determining whether the first media container satisfies the engagement criteria comprises:

determining whether the other user is engaged with the first media container within a predetermined period of time;

in accordance with a determination that the other user is engaged with the first media container within the predetermined time period, determining that the first media container satisfies the engagement criteria for the first user; and

in accordance with a determination that the other user is not engaged with the first media container within the predetermined time period, determining that the first media container does not satisfy the engagement criteria for the first user.

33. The method of any of claims 26-32, wherein displaying the engagement indicia for the representation of the first media container comprises:

displaying a first badge indicating a first user of the other users engaged with the one or more media items in the first media container.

34. The method of claim 33, wherein the first badge comprises a picture of the first one of the other users engaged with the one or more media items in the first media container.

35. The method of any of claims 33-34, wherein displaying the splice mark for the representation of the first media container further comprises:

displaying at least a portion of a second badge that indicates a second user of the other users engaged with the one or more media items in the first media container, wherein the second badge comprises a picture of the second user of the other users.

36. The method of claim 35, wherein displaying the splice mark for the representation of the first media container further comprises:

displaying at least a portion of a third badge that indicates a third user of the other users engaged with the one or more media items in the first media container, wherein the third badge comprises a picture of the third user of the other users.

37. The method of claim 36, wherein the number of badges displayed is less than a threshold number of badges.

38. The method of any of claims 36 to 37, further comprising:

detecting a user input on one of the first badge, the second badge and the third badge; and

displaying a list of the other users engaged with the first media container after detecting the user input.

39. The method of any of claims 26-38, wherein displaying the engagement indicia for the representation of the first media container comprises:

displaying a badge indicating that other users engaged the one or more media items in the first media container;

detecting, via the one or more input devices, a user input on the badge; and

in response to detecting the user input on the badge, displaying selectable affordances corresponding to the other users engaged with the one or more media items in the first media container, each selectable affordance corresponding to a respective one of the other users.

40. The method of claim 39, further comprising:

detecting, via the one or more input devices, a user input that activates one of the selectable affordances; and

in response to detecting the user input that activates the one of the selectable affordances, displaying a user profile for a respective one of the other users engaged with one or more media items in the first media container.

41. The method of any of claims 26-40, wherein the engagement indicia for the representation of the first media container indicates a type of engagement with the first media container that at least one of the other users has.

42. The method of claim 41, wherein:

in accordance with a determination that the type of engagement is a first type of engagement, the engagement indicia includes a first symbol indicating the first score; and

in accordance with a determination that the type of splice is a second type of splice, wherein the second type of splice is different from the first type of splice, the splice mark includes a second symbol that is different from the first symbol.

43. The method of claim 42, wherein in accordance with a determination that the type of the engagement includes the at least one of the other users assigning a third score to the first media container, the engagement marking does not include a third symbol indicating the third score, the third score being less than the first score.

44. The method of any of claims 26 to 43, wherein the first user has a private profile, the method further comprising:

receiving a follow-up request from a second user not in the predetermined relationship with the first user; and

displaying a notification on the display indicating the follow-up request;

while displaying the notification, detecting, via the one or more input devices, one or more user inputs corresponding to a request to display an expanded version of the notification; and

in response to receiving the one or more user inputs corresponding to the request to display the expanded version of the notification, displaying an expanded version of the notification, the expanded version of the notification comprising:

a first affordance that, when activated, accepts the follow request;

a second affordance that, when activated, denies the follow request; and

a third affordance that, when activated, displays a user profile for the second user.

45. The method of any of claims 26 to 44, further comprising:

displaying, within the media browsing user interface, a recommendation page that includes a recommendation for the first user, the recommendation including a plurality of sets of recommended content, wherein the plurality of sets of recommended content include:

a first set of recommended content selected based on engagement of users having the predefined relationship with the first user, and the first set of recommended content includes only containers of media items from among containers of the plurality of media items that satisfy the engagement criteria; and

a second set of recommended content selected based on criteria other than engagement by a user having the predefined relationship with the first user, including at least one media container that does not meet the engagement criteria.

46. The method of claim 45, wherein the containers of the media items in the first set of content are ordered based on one or more of a degree of engagement and a recency of engagement.

47. The method of any of claims 26 to 46, further comprising:

displaying a recommendation page within the media browsing user interface that includes a recommendation for the first user; and

displaying, within the recommendation page, a set of content including a container of media items that have been explicitly shared with the first user.

48. The method of any one of claims 26 to 47, further comprising:

displaying a notification on the display indicating that at least one of the other users has engaged with one or more media items in one or more of the containers of the plurality of media items.

49. An electronic device, the electronic device comprising:

a display;

an input device;

one or more processors;

a non-transitory memory; and

50. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with a display and an input device, cause the electronic device to perform or cause performance of any of the methods of claims 26-48.

51. An electronic device, the electronic device comprising:

a display;

an input device; and

apparatus for performing or causing performance of any one of the methods of claims 26-48.

52. A graphical user interface on an electronic device with a display, an input device, a non-transitory memory, and one or more processors to execute one or more programs stored in the non-transitory memory, the graphical user interface comprising user interfaces displayed in accordance with any of the methods of claims 26-48.

53. An information processing apparatus for use in an electronic device having a display and an input device, comprising:

apparatus for performing or causing performance of any one of the methods of claims 26-48.

54. A method, the method comprising:

at a device comprising a display and one or more input devices:

displaying a media browsing user interface for a media application on the display;

while displaying the media browsing user interface, receiving, via the one or more input devices, a request to display a recently played media container; and

in response to receiving the request to display the recently played media container, displaying a plurality of representations of media containers marked as having been recently played by a user, wherein the plurality of representations of media containers includes a first media container generated based on verbal instructions requesting playback of media matching a portion of the verbal instructions.

55. The method of claim 54, wherein the first media container includes a representation of the verbal instructions for generating the first media container.

56. The method of any of claims 54-55, wherein displaying the plurality of representations of media containers comprises:

displaying one or more representations of the custom media container; and

one or more representations of pre-existing media containers are displayed.

57. The method of claim 56, wherein:

the one or more representations of the custom media container comprise one or more icons for the custom media container;

the one or more representations of the pre-existing media container comprise one or more icons for the pre-existing media container; and

the one or more icons for the custom media container have a different appearance than the one or more icons for the pre-existing media container.

58. The method of any of claims 54-57, wherein the first media container is generated based on verbal instructions received at the device.

59. The method of any of claims 54-57, wherein the first media container is generated based on verbal instructions received at a different device associated with the user.

60. The method of any one of claims 54-59, further comprising:

receiving, at the device, verbal instructions for playing a media item; and

in response to receiving the verbal instructions for playing a media item:

in accordance with a determination that the verbal instruction matches one of a plurality of pre-existing media containers, selecting the one of the plurality of pre-existing media containers as the first container; and

in accordance with a determination that the verbal instruction does not match one of the plurality of pre-existing media containers, synthesizing a customized media container as the first container.

61. The method of claim 60, wherein the verbal instructions refer to an artist, and wherein synthesizing the customized media container comprises:

concatenating two or more of the media containers associated with the artist to edit the identity curated media containers.

62. The method of any of claims 54-61, further comprising:

receiving, at the device, verbal instructions for playing a media item; and

in response to receiving the verbal instructions for playing a media item:

in accordance with a determination that the verbal instructions include the predefined keyword, the first media container includes media items that match the portion of the verbal instructions and related media items that do not match the portion of the verbal instructions; and

in accordance with a determination that the verbal instructions do not include the predefined keyword, the first media container includes only the media items that match the portion of the verbal instructions.

63. The method of any of claims 54-62, wherein the first media container includes media items selected according to a media taste profile of the user.

64. The method of any of claims 54-63, wherein the first media container includes media items that other users are engaging, wherein the other users have a predetermined relationship with the user.

65. The method of claim 64, further comprising:

receiving, via the one or more input devices, user input on the representation of the first media container;

in response to receiving the user input on the representation of the first media container, displaying affordances for other users that affect the first media container by engaging with media items;

receiving, via the one or more input devices, user input on one of the affordances corresponding to one of the other users; and

in response to receiving the user input on the one of the affordances, removing a media item engaged with the one of the other users from the first media container.

66. The method of any of claims 54-65, wherein the first media container is updated periodically.

67. The method of claim 66, wherein updating the first media container comprises:

determining whether media items not currently in the first media container satisfy engagement criteria, wherein the engagement criteria for a respective media container include criteria that the first user has engaged with media in the respective media container with other users having a predetermined relationship therewith; and

in accordance with a determination that the media item satisfies the engagement criteria, including the media item in the first media container.

68. The method of any of claims 66-67, wherein updating the first media container comprises:

determining whether media items currently in the first media container satisfy engagement criteria, wherein the engagement criteria for a respective media container include criteria that the first user has engaged with media in the respective media container with a predetermined relationship to other users; and

in accordance with a determination that the media item does not satisfy the engagement criteria, removing the media item from the first media container.

69. An electronic device, the electronic device comprising:

a display;

an input device;

one or more processors;

a non-transitory memory; and

70. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with a display and an input device, cause the electronic device to perform or cause performance of any of the methods of claims 54-68.

71. An electronic device, the electronic device comprising:

a display;

an input device; and

apparatus for performing or causing performance of any one of the methods of claims 54-68.

72. A graphical user interface on an electronic device with a display, an input device, a non-transitory memory, and one or more processors to execute one or more programs stored in the non-transitory memory, the graphical user interface comprising user interfaces displayed in accordance with any of the methods of claims 54-68.

73. An information processing apparatus for use in an electronic device having a display and an input device, comprising:

apparatus for performing or causing performance of any one of the methods of claims 54-68.

74. A method, the method comprising:

at a device comprising a display and one or more input devices:

displaying, on the display, a media engagement user interface comprising a plurality of representations of containers of media items for which a first user has satisfied engagement criteria, wherein engagement of the first user with the containers of the plurality of media items is visible to other users having a predetermined relationship with the first user, wherein displaying the media engagement user interface comprises simultaneously displaying, on the display:

a representation of a first media container; and

a representation of a second media container;

detecting, via the one or more input devices, a sequence of one or more inputs corresponding to a request to hide the engagement of the first user with a respective media container; and

in response to detecting, via the one or more input devices, the sequence of one or more inputs corresponding to the request to hide the engagement of the first user with the respective media container:

in accordance with a determination that the sequence of one or more inputs corresponds to a request to hide the engagement of the first user with the first media container, changing an appearance of the representation of the first media container without changing an appearance of the representation of the second media container, wherein the change to the representation of the first media container indicates that the engagement of the first user with the first media container is hidden from view by other users having the predetermined relationship with the first user; and

in accordance with a determination that the sequence of one or more inputs corresponds to a request to hide the engagement of the first user with the second media container, changing an appearance of the representation of the second media container without changing an appearance of the representation of the first media container, wherein the change in the appearance of the representation of the second media container indicates that the engagement of the first user with the second media container is hidden from view by the other users having the predetermined relationship with the first user.

75. The method of claim 74, wherein the plurality of representations of containers of media items are displayed in a user profile portion of the media engagement user interface.

76. The method of any of claims 74-75, wherein the plurality of representations of containers of media items are displayed in a recommendation module of the media engagement user interface.

77. The method of any of claims 74-76, wherein the plurality of representations of containers of media items are ordered based on one or more of a joint frequency and a joint recency.

78. The method of any one of claims 74-77, further comprising:

after the engagement of the first user with the first media container is hidden from view by the other users having the predetermined relationship with the first user:

detecting subsequent engagement of the first user with one or more of the containers of media items; and

in response to detecting the subsequent engagement of the first user with the container of the one or more media items, updating the rankings of the plurality of representations of containers of media items based on one or more of a frequency of engagement and a recency of engagement.

79. The method of any one of claims 74-78, further comprising:

after the engagement of the first user with the first media container is hidden from view by the other users having the predetermined relationship with the first user:

detecting engagement of the first user with the first media container; and

after detecting the engagement of the first user with the first media container, causing the change to the representation of the first media container to be maintained as indicating that the engagement of the first user with the media container remains hidden from view by the other users having the predetermined relationship with the first user.

80. The method of any of claims 74-79, wherein the one or more media items in the first container include one or more of a playlist, an album, a radio station, and individual music items.

81. The method of any of claims 74-80, wherein the plurality of representations of containers of media items are displayed in a module of a profile page for the first user, wherein the module indicates media items that the first user is listening to.

82. The method of claim 81, further comprising:

presenting at least one of the containers of the plurality of media items as a media recommendation to at least one of the other users with which the first user has the predetermined relationship.

83. The method of claim 82, further comprising:

after the engagement of the first user with the first media container is hidden from view by the other users having the predetermined relationship with the first user:

forgoing presentation of the first media container to the at least one of the other users with which the first user has the predetermined relationship as the media recommendation.

84. The method of any of claims 74-83, wherein the one or more media items in the first media container include a plurality of media items, and wherein the engagement of the first user with each of the plurality of media items is hidden from view by the other users having the predetermined relationship with the first user.

85. The method of any one of claims 74-84, further comprising:

receiving, via the one or more input devices, user input on the representation of the first media container; and

displaying on the display a menu comprising affordances that, when activated, trigger respective user interface operations.

86. The method of claim 85, wherein the menu is an overlay interface, and wherein the user interface operations triggered by the affordance include one or more of: hiding the representation of the first container, adding the first container to a library, adding the first container to a playlist, sharing the first container, and playing media items from the first container.

87. The method of any one of claims 74-86, further comprising:

displaying a privacy settings affordance on the display; and

wherein the sequence of one or more inputs is detected at a location corresponding to the privacy settings affordance.

88. The method of any of claims 74-87, wherein detecting the sequence of one or more inputs comprises:

detecting a user input at a location corresponding to the representation of the respective media container.

89. The method of any one of claims 74-88, further comprising:

after the engagement of the first user with the first media container is hidden from view by the other users having the predetermined relationship with the first user:

forgoing display of the representation of the first media container on a public version of a profile page for the first user, wherein the public version of the profile page is visible to the other users having the predetermined relationship with the first user; and

maintaining a display of the changed representation of the first media container on a private version of the profile page for the first user, wherein the private version of the profile page is visible only to the first user.

90. The method of any one of claims 74-89, further comprising:

after the engagement of the first user with the first media container is hidden from view by the other users having the predetermined relationship with the first user:

receiving, via the one or more input devices, a request to unhide the engagement of the first user with the first media container; and

in response to receiving the request to unhide the engagement, restoring the change in the appearance of the representation of the first media container, wherein the change in the appearance of the representation of the first media container indicates that the engagement of the first user with the first media container is no longer hidden from view by the other users having the predetermined relationship with the first user.

91. An electronic device, the electronic device comprising:

a display;

an input device;

one or more processors;

a non-transitory memory; and

92. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with a display and an input device, cause the electronic device to perform or cause performance of any of the methods of claims 74-89.

93. An electronic device, the electronic device comprising:

a display;

an input device; and

means for performing or causing performance of any one of the methods of claims 74-89.

94. A graphical user interface on an electronic device with a display, an input device, a non-transitory memory, and one or more processors to execute one or more programs stored in the non-transitory memory, the graphical user interface comprising user interfaces displayed in accordance with any of the methods of claims 74-89.

95. An information processing apparatus for use in an electronic device having a display and an input device, comprising:

means for performing or causing performance of any one of the methods of claims 74-89.

Technical Field

The present disclosure relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that implement representations for presenting media containers.

Background

The use of touch sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch sensitive surfaces include trackpads and touch screen displays. Such surfaces are widely used for manipulating user interface objects on a display.

Exemplary manipulations include adjusting the position and/or size of one or more user interface objects, or activating a button or opening a file/application represented by a user interface object, as well as associating metadata with one or more user interface objects or otherwise manipulating a user interface. Exemplary user interface objects include digital images, videos, text, icons, control elements (such as buttons), and other graphics. In some cases, the user will need to perform such manipulations on user interface objects in: a file management program (e.g., Finder from Apple Inc. (Cupertino, California)); image management applications (e.g., Aperture, iPhoto, Photos from Apple Inc. (Cupertino, California)); digital content (e.g., video and music) management applications (e.g., iTunes from Apple Inc. (Cupertino, California)); a drawing application program; a presentation application (e.g., Keynote from Apple Inc. (Cupertino, California)); word processing applications (e.g., Pages from Apple Inc. (Cupertino, California)); a website creation application (e.g., ibe from Apple Inc. (Cupertino, California)); disc editing applications (e.g., iDVD from Apple Inc. (Cupertino, California)); or spreadsheet applications (e.g., Numbers from Apple Inc. (Cupertino, California)).

However, the methods for performing these manipulations are cumbersome and inefficient. For example, using a sequence of mouse-based inputs to select one or more user interface objects and perform one or more actions on the selected user interface objects is tedious and creates a significant cognitive burden on the user. Furthermore, these methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-powered devices.

Disclosure of Invention

Accordingly, there is a need for electronic devices that display and interact with representations of media containers using faster and more efficient methods and interfaces. Such methods and interfaces optionally complement or replace conventional methods for displaying and interacting with representations of media containers. Such methods and interfaces reduce the cognitive burden placed on the user and result in a more efficient human-machine interface. For battery-driven devices, such methods and interfaces may conserve power and increase the time between battery charges.

The above-described deficiencies and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces may be reduced or eliminated with the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, tablet, or handheld device). In some embodiments, the device has a touch pad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touch screen" or "touch screen display"). In some embodiments, the device has a Graphical User Interface (GUI), one or more processors, memory, and one or more modules, programs or sets of instructions stored in the memory for performing a plurality of functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, rendering, word processing, web page creation, disc editing, spreadsheet making, game playing, telephone answering, video conferencing, e-mailing, instant messaging, fitness support, digital photography, digital video recording, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

According to some embodiments, a method is performed at a device having a display, one or more input devices, a non-transitory memory, and one or more processors coupled with the display, the one or more input devices, and the non-transitory memory. The method includes receiving, via the one or more input devices, a request to register for music sharing, wherein registering for music sharing allows a first user to share music with other users. After receiving the request, the method includes displaying a check-in user interface on the display, the check-in user interface including simultaneously displaying a representation of a plurality of playlists created by the first user and privacy settings for the plurality of playlists, wherein the privacy settings for the plurality of playlists have default values. The registration user interface includes a first affordance corresponding to a first playlist of the plurality of playlists created by the first user and a second affordance corresponding to a second playlist of the plurality of playlists created by the first user. The method comprises the following steps: while displaying the privacy settings for the plurality of playlists, receiving, via the one or more input devices, one or more user inputs that change the privacy settings for one or more of the plurality of playlists from the corresponding default privacy settings to user-specified privacy settings. The method comprises the following steps: after completion of the registration, providing access to the plurality of playlists of the first user to other users having a predetermined relationship with the first user based on the privacy settings for the plurality of playlists. In accordance with a determination that the one or more user inputs detected while displaying the enrollment user interface change a default privacy setting for the first playlist, the method includes providing access to the first playlist of the first user to other users connected with the first user based on the user-specified privacy setting. In accordance with a determination that the one or more user inputs detected while displaying the enrollment user interface change a default privacy setting for the second playlist, the method includes providing access to the second playlist of the first user to other users connected to the first user based on the user-specified privacy setting.

According to some embodiments, an electronic device includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled with the display unit and the one or more input units. The processing unit is configured to receive, via the one or more input devices, a request to register for music sharing, wherein registering for music sharing allows the first user to share music with other users. Upon receiving the request, the processing unit displays on the display a registration user interface that includes displaying, simultaneously, representations of a plurality of playlists created by the first user and privacy settings for the plurality of playlists, wherein the privacy settings for the plurality of playlists have default values. The registration user interface includes a first affordance corresponding to a first playlist of the plurality of playlists created by the first user and a second affordance corresponding to a second playlist of the plurality of playlists created by the first user. The processing unit is configured to: while displaying the privacy settings for the plurality of playlists, receiving, via the one or more input devices, one or more user inputs that change the privacy settings for one or more of the plurality of playlists from the corresponding default privacy settings to user-specified privacy settings. The processing unit is configured to: after completion of the registration, providing access to the plurality of playlists of the first user to other users having a predetermined relationship with the first user based on the privacy settings for the plurality of playlists. In accordance with a determination that the one or more user inputs detected while displaying the enrollment user interface change a default privacy setting for the first playlist, the processing unit provides other users connected with the first user access to the first playlist of the first user based on the user-specified privacy setting. In accordance with a determination that the one or more user inputs detected while displaying the enrollment user interface change a default privacy setting for the second playlist, the processing unit provides access to the second playlist of the first user to other users connected with the first user based on the user-specified privacy setting.

According to some embodiments, a method is performed at a device having a display, one or more input devices, a non-transitory memory, and one or more processors coupled with the display, the one or more input devices, and the non-transitory memory. The method includes displaying a media browsing user interface for a first user on a display. The method comprises the following steps: while displaying the media browsing user interface, receiving, via the one or more input devices, input corresponding to a request to display a different view of the media browsing user interface. The method comprises the following steps: in response to the input, simultaneously displaying, within the media browsing user interface, a plurality of representations of containers of media items: a representation of the first media container and a representation of the second media container. In accordance with a determination that the first media container satisfies engagement criteria for the first user, wherein the engagement criteria for the respective media container include criteria that the first user has engaged media in the respective media container with other users having a predetermined relationship therewith, the method includes displaying an engagement indicia for the representation of the first media container to indicate that the first user having a predetermined relationship therewith has engaged one or more media items in the first media container. In accordance with a determination that the first media container does not satisfy the engagement criteria for the first user, the method includes displaying a representation of the first media container without displaying an engagement flag for the representation of the first media container. In accordance with a determination that the second media container satisfies engagement criteria for the first user, the method includes displaying engagement indicia for the representation of the second media container to indicate that a user with whom the first user has a predetermined relationship has engaged one or more media items in the second media container. In accordance with a determination that the second media container does not satisfy the engagement criteria for the first user, the method includes displaying a representation of the second media container without displaying an engagement flag for the representation of the second media container.

According to some embodiments, an electronic device includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled with the display unit and the one or more input units. The processing unit is configured to display a media browsing user interface for the first user on the display unit. The processing unit is configured to: while displaying the media browsing user interface, receiving, via the one or more input units, an input corresponding to a request to display a different view of the media browsing user interface. In response to the input, the processing unit simultaneously displays, within the media browsing user interface, a plurality of representations of containers of media items, including a representation of a first media container and a representation of a second media container. In accordance with a determination that the first media container satisfies engagement criteria for the first user, wherein the engagement criteria for the respective media container include criteria that the first user has engaged media in the respective media container with other users having a predetermined relationship therewith, the processing unit displays engagement indicia for the representation of the first media container to indicate that the first user having a predetermined relationship therewith has engaged one or more media items in the first media container. In accordance with a determination that the first media container does not satisfy the engagement criteria for the first user, the processing unit displays a representation of the first media container without displaying an engagement flag for the representation of the first media container. In accordance with a determination that the second media container satisfies engagement criteria for the first user, the processing unit displays engagement indicia for the representation of the second media container to indicate that the user with whom the first user has a predetermined relationship has engaged one or more media items in the second media container. In accordance with a determination that the second media container does not satisfy the engagement criteria for the first user, the processing unit displays a representation of the second media container without displaying an engagement flag for the representation of the second media container.

According to some embodiments, a method is performed at a device having a display, one or more input devices, a non-transitory memory, and one or more processors coupled with the display, the one or more input devices, and the non-transitory memory. The method includes displaying, on a display, a media engagement user interface that includes a plurality of representations of containers of media items for which a first user has satisfied engagement criteria. The engagement of the first user with the container of the plurality of media items is visible to other users having a predetermined relationship with the first user. Displaying the media engagement user interface includes simultaneously displaying a representation of the first media container and a representation of the second media container on the display. The method includes detecting, via the one or more input devices, a sequence of one or more inputs corresponding to a request to hide the engagement of the first user with the respective media container. In response to detecting, via the one or more input devices, a sequence of one or more inputs corresponding to a request to hide the engagement of the first user with the respective media container, the method includes: in accordance with a determination that the sequence of one or more inputs corresponds to a request to hide the engagement of the first user with the first media container, changing an appearance of the representation of the first media container without changing an appearance of the representation of the second media container. The change to the representation of the first media container indicates that the first user's engagement with the first media container is hidden from view by other users having a predetermined relationship with the first user. In accordance with a determination that the sequence of one or more inputs corresponds to a request to hide the engagement of the first user with the second media container, the method includes changing an appearance of the representation of the second media container without changing an appearance of the representation of the first media container, wherein the change in appearance of the representation of the second media container indicates that the engagement of the first user with the second media container is hidden from view by other users having a predetermined relationship with the first user.

According to some embodiments, an electronic device includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled with the display unit and the one or more input units. The processing unit is configured to display a media engagement user interface on the display unit, the media engagement user interface including a plurality of representations of containers of media items for which the first user has satisfied engagement criteria. The engagement of the first user with the container of the plurality of media items is visible to other users having a predetermined relationship with the first user. Displaying the media engagement user interface includes simultaneously displaying a representation of the first media container and a representation of the second media container on the display. The processing unit detects, via the one or more input devices, a sequence of one or more inputs corresponding to a request to hide the engagement of the first user with the respective media container. In response to detecting, via the one or more input devices, a sequence of one or more inputs corresponding to a request to hide the engagement of the first user with the respective media container, the processing unit: in accordance with a determination that the sequence of one or more inputs corresponds to a request to hide the engagement of the first user with the first media container, changing an appearance of the representation of the first media container without changing an appearance of the representation of the second media container. The change to the representation of the first media container indicates that the first user's engagement with the first media container is hidden from view by other users having a predetermined relationship with the first user. In accordance with a determination that the sequence of one or more inputs corresponds to a request to hide the engagement of the first user with the second media container, the processing unit changes an appearance of the representation of the second media container without changing an appearance of the representation of the first media container, wherein the change in appearance of the representation of the second media container indicates that the engagement of the first user with the second media container is hidden from view by other users having a predetermined relationship with the first user.

Accordingly, an electronic device having a display and an input device is provided with a faster and more efficient method and interface for displaying affordances in an accessibility mode. Such electronic devices improve visibility of the affordance, thereby improving operability of the electronic device. Such methods and interfaces may supplement or replace conventional methods for displaying affordances in an accessibility mode.

Drawings

For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

Fig. 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments.

FIG. 2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

Fig. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

FIG. 4A illustrates an exemplary user interface of an application menu on a portable multifunction device according to some embodiments.

FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from a display, in accordance with some embodiments.

Fig. 5A-5V illustrate exemplary user interfaces for sharing music with other users, according to some embodiments.

Fig. 6A-6N illustrate exemplary user interfaces for indicating engagement by other users, according to some embodiments.

Fig. 7A-7T illustrate exemplary user interfaces displaying representations of media containers marked as recently played by a user, according to some embodiments.

Fig. 8A-8X illustrate an exemplary user interface that allows a first user to hide the first user's engagement with one or more media containers, according to some embodiments.

Fig. 9A-9F are flow diagrams illustrating methods of sharing music with other users, according to some embodiments.

Fig. 10A-10E are flow diagrams illustrating methods of indicating engagement of other users, according to some embodiments.

11A-11D are flow diagrams illustrating methods of displaying representations of media containers marked as recently played by a user, according to some embodiments.

Fig. 12A-12E are flow diagrams illustrating methods of allowing a first user to hide the engagement of the first user with one or more media containers, according to some embodiments.

Detailed Description

In general, obtaining information stored as data encoded in an optical machine-readable format is a non-intuitive, non-user-friendly experience. Thus, in the embodiments described below, the device displays a notification when the device detects that the media capture preview generated by the media capture user interface of the camera application includes data encoded in an optical machine-readable format. Displaying notifications in a media capture user interface provides an intuitive and user-friendly experience. Further, detecting data encoded in an optical machine-readable format while displaying the media capture user interface reduces the need to launch a user interface dedicated to detecting data encoded in a machine-readable format.

Some devices do not provide an intuitive and user-friendly option for processing images that include data encoded in an optical machine-readable format. Thus, in the embodiments described below, in response to an image including data encoded in an optical machine-readable format, the device displays information corresponding to the data encoded in the optical machine-readable format. The device displays information corresponding to the data encoded in the optical machine-readable format in response to receiving a request for additional information about the image. If the image does not include data encoded in an optical machine-readable format, the device displays additional information about the image. Displaying information corresponding to data encoded in an optical machine-readable format provides a user with the option to take action on the information, thereby improving the operability of the device and providing a better user experience.

Some devices do not provide intuitive and user-friendly options for taking action on various types of encoding functions. Thus, in the embodiments described below, a device detects the proximity of the device to a coded feature and displays a notification that includes an indication indicating the type of coded feature. The notification provides the user with the option to take action on the information stored in the encoded feature. Detecting and indicating various types of coding features when the device is in proximity to the coding features improves the operability of the device by providing the user with the option to take action on the coding features.

1A-1B, FIG. 2, and FIG. 3 provide a description of exemplary devices. Fig. 4A to 4B and 5A to 5W illustrate exemplary user interfaces for sharing music with other users. Fig. 6A-6N illustrate exemplary user interfaces for indicating engagement of other users with a media container of a first user. Fig. 7A-7T illustrate exemplary user interfaces displaying representations of media containers marked as recently played by a user. Fig. 8A-8X illustrate exemplary user interfaces that allow a first user to hide the first user's engagement with one or more media containers. Fig. 9A to 9F show flowcharts of a method of sharing music with other users. The user interfaces in fig. 5A to 5V are used to illustrate the processes in fig. 9A to 9F. Fig. 10A-10E show flow charts indicating engagement of other users with one or more media containers of a first user. The user interfaces in fig. 6A to 6N are used to illustrate the processes in fig. 10A to 10E. 11A-11D illustrate a flow diagram of a method of displaying representations of media containers marked as recently played by a user. The user interfaces in fig. 7A to 7T are used to illustrate the processes in fig. 11A to 11D. Fig. 12A-12E illustrate a flow diagram for hiding engagement of a first user with one or more media containers. The user interfaces in fig. 8A to 8X are used to illustrate the processes in fig. 12A to 12E.

Exemplary device

Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of various described embodiments. It will be apparent, however, to one skilled in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail as not to unnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements in some cases, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact can be termed a second contact, and, similarly, a second contact can be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact unless the context clearly indicates otherwise.

The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, the term "if" is optionally interpreted to mean "when … …" after "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrase "if determined … …" or "if [ stated condition or event ] is detected" is optionally to be construed to mean "upon determination … …" or "in response to determination … …" or "upon detection of [ stated condition or event ] or" in response to detection of [ stated condition or event ] ", depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and related processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also contains other functions, such as PDA and/or music player functions. Portable multifunctionalExemplary embodiments of energy devices include, but are not limited to, those from apple inc

iPod

Andan apparatus. Other portable electronic devices are optionally used, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).

In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick.

The device typically supports various applications, such as one or more of the following: a mapping application, a rendering application, a word processing application, a website creation application, a disc editing application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

Various applications executing on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or varied for different applications and/or within respective applications. In this way, a common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

Attention is now directed to embodiments of portable devices having touch sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display system 112 is sometimes referred to as a "touch screen" for convenience and is sometimes referred to simply as a touch-sensitive display. Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 163 for generating tactile outputs on device 100 (e.g., on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in this specification and claims, the term "haptic output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to a center of mass of the device that is to be detected by a user with the user's sense of touch. For example, where a device or component of a device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other portion of a user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a haptic sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of the touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down click" or "up click" of a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click," even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement is not moving. As another example, even when there is no change in the smoothness of the touch sensitive surface, the movement of the touch sensitive surface is optionally interpreted or sensed by the user as "roughness" of the touch sensitive surface. While such interpretation of touch by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touch are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "click down," "click up," "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component thereof that would generate the sensory perception of a typical (or ordinary) user.

It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of these components. The various components shown in fig. 1A are implemented in hardware, software, firmware, or any combination thereof, including one or more signal processing circuits and/or application specific integrated circuits.

The memory 102 optionally includes high-speed random access memory, and also optionally includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as one or more CPUs 120 and peripheral interface 118, is optionally controlled by a memory controller 122.

Peripheral interface 118 may be used to couple the input and output peripherals of the device to memory 102 and one or more CPUs 120. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in the memory 102 to perform various functions of the device 100 and to process data.

In some embodiments, peripherals interface 118, one or more CPUs 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

RF (radio frequency) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks such as the internet, also known as the World Wide Web (WWW), intranets, and/or wireless networks such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), and other devices via wireless communication. The wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including, but not limited to, global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), evolution data only (EV-DO), HSPA +, dual cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), wideband code division multiple access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), bluetooth, wireless fidelity (Wi-Fi) (e.g., IEEE802.11a, IEEE802.11 ac, IEEE802.11 ax, IEEE802.11 b, IEEE802.11 g, and/or IEEE802.11n), voice over internet protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP), and/or Post Office Protocol (POP)) Instant messaging (e.g., extensible messaging and presence protocol (XMPP), session initiation protocol for instant messaging and presence with extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and/or Short Message Service (SMS)), or any other suitable communication protocol including communication protocols not yet developed at the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. The audio circuitry 110 receives audio data from the peripheral interface 118, converts the audio data to electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to a human. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals to audio data and transmits the audio data to the peripheral interface 118 for processing. Audio data is optionally retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripheral interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in fig. 2). The headset jack provides an interface between the audio circuitry 110 and a removable audio input/output peripheral such as an output-only headset or a headset having both an output (e.g., a monaural headset or a binaural headset) and an input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripheral devices on the device 100, such as a touch-sensitive display system 112 and other input or control devices 116, to a peripheral interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive electrical signals from or transmit electrical signals to other input or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, one or more input controllers 160 are optionally coupled to (or not coupled to) any of: a keyboard, an infrared port, a USB port, a stylus, and/or a pointing device such as a mouse. The one or more buttons (e.g., 208 in fig. 2) optionally include an up/down button for volume control of the speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in fig. 2).

Touch-sensitive display system 112 provides an input interface and an output interface between the device and the user. Display controller 156 receives electrical signals from touch-sensitive display system 112 and/or transmits electrical signals to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to a user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to a user interface object.

Touch-sensitive display system 112 has a touch-sensitive surface, sensor, or group of sensors that accept input from a user based on haptic/tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and convert the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch-sensitive display system 112. In an exemplary embodiment, the point of contact between touch-sensitive display system 112 and the user corresponds to a user's finger or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In an exemplary embodiment, the administration is usedReflective mutual capacitance sensing technology, such as that from Apple Inc (Cupertino, California)

iPod

And

the technique found in (1).

Touch sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400dpi (e.g., 500dpi, 800dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the action desired by the user.

In some embodiments, in addition to a touch screen, device 100 optionally includes a touch pad (not shown) for activating or deactivating particular functions. In some embodiments, the trackpad is a touch-sensitive area of the device that, unlike a touchscreen, does not display visual output. The trackpad is optionally a touch-sensitive surface separate from touch-sensitive display system 112, or an extension of the touch-sensitive surface formed by the touch screen.

The device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a Light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

The device 100 optionally further includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The one or more optical sensors 164 optionally include Charge Coupled Devices (CCDs) or Complementary Metal Oxide Semiconductor (CMOS) phototransistors. The one or more optical sensors 164 receive light projected through the one or more lenses from the environment and convert the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), one or more optical sensors 164 optionally capture still images and/or video. In some embodiments, an optical sensor is located on the back of device 100 opposite touch-sensitive display system 112 on the front of the device, enabling the touch screen to be used as a viewfinder for still and/or video image capture. In some embodiments, another optical sensor is located on the front of the device to capture images of the user (e.g., for self-timer shooting, for video conferencing while the user is viewing other video conference participants on a touch screen, etc.).

Device 100 optionally further comprises one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I/O subsystem 106. The one or more contact intensity sensors 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). One or more contact intensity sensors 165 receive contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some implementations, at least one contact intensity sensor is collocated with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100 opposite touch-sensitive display system 112, which is located on the front of device 100.

The device 100 optionally further includes one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 is coupled with the input controller 160 in the I/O subsystem 106. In some embodiments, the proximity sensor turns off and disables touch-sensitive display system 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

The device 100 optionally further includes one or more tactile output generators 163. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 in I/O subsystem 106. The tactile output generator 163 optionally includes one or more electro-acoustic devices such as speakers or other audio components, and/or electromechanical devices that convert energy into linear motion such as motors, solenoids, electroactive aggregators, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). The tactile output generator 163 receives tactile feedback generation instructions from the tactile feedback module 133 and generates tactile outputs on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., into/out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100 opposite touch-sensitive display system 112 located on the front of device 100.

The device 100 optionally also includes one or more accelerometers 167, gyroscopes 168, and/or magnetometers 169 (e.g., as part of an Inertial Measurement Unit (IMU)) for obtaining information regarding the device's position (e.g., pose). FIG. 1A shows sensors 167, 168, and 169 coupled to peripheral interface 118. Alternatively, sensors 167, 168, and 169 are optionally coupled to input controller 160 in I/O subsystem 106. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from the one or more accelerometers. The device 100 may optionally include a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the location of the device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a haptic feedback module (or set of instructions) 133, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application program (or set of instructions) 136. Further, in some embodiments, memory 102 stores device/global internal state 157, as shown in fig. 1A and 3. Device/global internal state 157 includes one or more of: an active application state indicating which applications (if any) are currently active; display state, which indicates what applications, views, or other information occupy various areas of touch-sensitive display system 112; sensor status, including information obtained from various sensors of the device and other input or control devices 116; and position and/or orientation information regarding the position and/or attitude of the device.

The operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communications module 128 facilitates communications with other devices through one or more external ports 124, and also includes various software components for processing data received by RF circuitry 108 and/or external ports 124. External port 124 (e.g., Universal Serial Bus (USB), firewire, etc.) is adapted to couple directly to other devices or indirectly through a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is some of Apple Inc

iPod

A multi-pin (e.g., 30-pin) connector that is the same as or similar and/or compatible with the 30-pin connector used in iPod devices. In some embodiments, the external port is some of Apple Inc

iPodA Lightning connector that is the same as or similar and/or compatible with the Lightning connector used in the iPod device.

Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a trackpad or physical click wheel). Contact/motion module 130 includes software components for performing various operations related to detection of contact (e.g., a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger-down event), determining the intensity of contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining whether contact has ceased (e.g., detecting a finger-up event or a contact-breaking). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact optionally includes determining velocity (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the point of contact, the movement of the point of contact being represented by a series of contact data. These operations are optionally applied to single point contacts (e.g., single finger contacts or stylus contacts) or multiple simultaneous contacts (e.g., "multi-touch"/multi-finger contacts and/or stylus contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detect contact on a touch pad.

The contact/motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, the gesture is optionally detected by detecting a particular contact pattern. For example, detecting a single-finger tap gesture includes detecting a finger-down event, and then detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at an icon location). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event, then detecting one or more finger-dragging events, and then subsequently detecting a finger-up (lift-off) event. Similarly, taps, swipes, drags, and other gestures of the stylus are optionally detected by detecting a particular contact pattern of the stylus.

Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other displays, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual properties) of displayed graphics. As used herein, the term "graphic" includes any object that may be displayed to a user, including without limitation text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphic module 132 receives one or more codes for specifying a graphic to be displayed from an application program or the like, and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to output to the display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by haptic output generator 163 to produce haptic outputs at one or more locations on device 100 in response to user interaction with device 100.

Text input module 134, which is optionally a component of graphics module 132, provides a soft keyboard for entering text in various applications such as contacts 137, email 140, IM 141, browser 147, and any other application that requires text input.

The GPS module 135 determines the location of the device and provides such information for use in various applications (e.g., to the phone 138 for location-based dialing; to the camera 143 as picture/video metadata; and to applications that provide location-based services such as weather desktop widgets, local yellow pages desktop widgets, and map/navigation desktop widgets).

Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof:

a contacts module 137 (sometimes referred to as an address book or contact list);

a phone module 138;

a video conferencing module 139;

an email client module 140;

an Instant Messaging (IM) module 141;

fitness support module 142;

a camera module 143 for still and/or video images;

an image management module 144;

a browser module 147;

a calendar module 148;

desktop applet module 149, optionally including one or more of: a weather desktop applet 149-1, a stock market desktop applet 149-2, a calculator desktop applet 149-3, an alarm desktop applet 149-4, a dictionary desktop applet 149-5, and other desktop applets obtained by the user, and a user created desktop applet 149-6;

a desktop applet creator module 150 for forming a user-created desktop applet 149-6;

a search module 151;

a video and music player module 152, optionally consisting of a video player module and a music player module;

a notepad module 153;

a map module 154; and/or

Online video module 155.

Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions for managing contact lists or contact lists (e.g., stored in memory 102 or in an application internal state 192 of contacts module 137 in memory 370), including: adding a name to the address book; delete names from the address book; associating a telephone number, email address, physical address, or other information with a name; associating the image with a name; classifying and classifying names; providing a telephone number and/or email address to initiate and/or facilitate communication via telephone 138, video conference 139, email 140, or instant message 141; and so on.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, phone module 138 includes executable instructions for: entering a sequence of characters corresponding to a telephone number, accessing one or more telephone numbers in the address book 137, modifying the entered telephone number, dialing a corresponding telephone number, conducting a conversation, and disconnecting or hanging up when the conversation is completed. As noted above, the wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephony module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants according to user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send an email with a still image or a video image captured by the camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: entering a sequence of characters corresponding to an instant message, modifying previously entered characters, sending a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for telephone-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for internet-based instant messages), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant messages optionally include graphics, photos, audio files, video files, and/or MMS and/or other attachments supported in an Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, fitness support module 142 includes executable instructions for creating a workout (e.g., having time, distance, and/or calorie burning goals); communicating with fitness sensors (in sports equipment and smart watches); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

In conjunction with touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to: capturing still images or video (including video streams) and storing them in the memory 102, modifying features of the still images or video, and/or deleting the still images or video from the memory 102.

In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide or album), and storing still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the internet (including searching, linking to, receiving, and displaying web pages or portions thereof, and attachments and other files linked to web pages) according to user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do items, etc.) according to user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet module 149 is a mini-application (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) that is optionally downloaded and used by the user, or a mini-application created by the user (e.g., user-created desktop applet 149-6). In some embodiments, the desktop applet includes an HTML (hypertext markup language) file, a CSS (cascading style sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (extensible markup language) file and a JavaScript file (e.g., Yahoo! desktop applet).

In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, desktop applet creator module 150 includes executable instructions for creating a desktop applet (e.g., turning a user-specified portion of a web page into a desktop applet).

In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions for searching memory 102 for text, music, sound, images, videos, and/or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speakers 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and playback recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, rendering, or otherwise playing back video (e.g., on touch-sensitive display system 112 or on an external display wirelessly connected via external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple inc.).

In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notepad module 153 includes executable instructions for creating and managing notepads, backlogs, and the like according to user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions for receiving, displaying, modifying, and storing maps and data associated with maps (e.g., driving directions; data for stores and other points of interest at or near a particular location; and other location-based data) according to user instructions.

In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes executable instructions that allow a user to access, browse, receive (e.g., by streaming and/or downloading), play back (e.g., on touch screen 112 or on an external display that is wirelessly connected or connected via external port 124), send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as h.264. In some embodiments, the link to the particular online video is sent using instant messaging module 141 instead of email client module 140.

Each of the modules and applications identified above corresponds to a set of executable instructions for performing one or more of the functions described above as well as the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures described above. Further, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device on which the operation of a predefined set of functions is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or trackpad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.

The predefined set of functions performed exclusively through the touchscreen and/or trackpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main, home, or root menu. In such embodiments, a touchpad is used to implement a "menu button". In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

Fig. 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 102 (in FIG. 1A) or memory 370 (FIG. 3) includes event classifier 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., any of the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives the event information and determines application 136-1 and application view 191 of application 136-1 to which the event information is to be delivered. The event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that indicates one or more current application views that are displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, the device/global internal state 157 is used by the event classifier 170 to determine which application(s) are currently active, and the application internal state 192 is used by the event classifier 170 to determine the application view 191 to which to deliver event information.

In some embodiments, the application internal state 192 includes additional information, such as one or more of: resume information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready for display by the application 136-1, a state queue for enabling a user to return to a previous state or view of the application 136-1, and a repeat/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripheral interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 167, one or more gyroscopes 168, one or more magnetometers 169, and/or microphone 113 (through audio circuitry 110). Information received by peripheral interface 118 from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to peripheral interface 118 at predetermined intervals. In response, peripheral interface 118 transmits the event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving input above a predetermined noise threshold and/or receiving input for more than a predetermined duration).

In some embodiments, event classifier 170 further includes hit view determination module 172 and/or active event recognizer determination module 173.

When touch-sensitive display system 112 displays more than one view, hit view determination module 172 provides a software process for determining where within one or more views a sub-event has occurred. The view consists of controls and other elements that the user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within a programmatic or view hierarchy of applications. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events identified as correct inputs is optionally determined based at least in part on the hit view of the initial touch that initiated the touch-based gesture.

Hit view determination module 172 receives information related to sub-events of the touch-based gesture. When the application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which the initiating sub-event (i.e., the first sub-event in the sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

The active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some implementations, the active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and thus determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, the higher views in the hierarchy will remain actively participating views.

The event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers event information to event recognizers determined by active event recognizer determination module 173. In some embodiments, the event dispatcher module 174 stores event information in an event queue, which is retrieved by the respective event receiver module 182.

In some embodiments, the operating system 126 includes an event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another embodiment, the event classifier 170 is a stand-alone module or is part of another module stored in the memory 102 (such as the contact/motion module 130).

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module that is a higher-level object such as a user interface toolkit (not shown) or application 136-1 that inherits methods and other properties from it. In some embodiments, the respective event handlers 190 comprise one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and recognizes events from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).

The event receiver 182 receives event information from the event sorter 170. The event information includes information about a sub-event such as a touch or touch movement. According to the sub-event, the event information further includes additional information, such as the location of the sub-event. When the sub-event relates to motion of a touch, the event information optionally also includes the velocity and direction of the sub-event. In some embodiments, the event comprises rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information comprises corresponding information about the current orientation of the device (also referred to as the device pose).

Event comparator 184 compares the event information to predefined event or sub-event definitions and determines an event or sub-event or determines or updates the state of an event or sub-event based on the comparison. In some embodiments, event comparator 184 includes event definitions 186. Event definition 186 contains definitions of events (e.g., predefined sub-event sequences), such as event 1(187-1), event 2(187-2), and others. In some embodiments, sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1(187-1) is a double click on the displayed object. The double tap includes, for example, a first touch on the displayed object for a predetermined phase (touch start), a first lift-off for a predetermined phase (touch end), a second touch on the displayed object for a predetermined phase (touch start), and a second lift-off for a predetermined phase (touch end). In another example, the definition of event 2(187-2) is a drag on the displayed object. Dragging includes, for example, a predetermined length of time of touch (or contact) on a displayed object, movement of the touch across touch-sensitive display system 112, and liftoff of the touch (touch complete). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes definitions of events for respective user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view that displays three user interface objects on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, the definition of the respective event 187 further includes a delay action that delays the delivery of the event information until it has been determined whether the sequence of sub-events does or does not correspond to the event type of the event identifier.

When the respective event recognizer 180 determines that the sequence of sub-events does not match any event in the event definition 186, the respective event recognizer 180 enters an event not possible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, the respective event recognizer 180 includes metadata 183 with configurable attributes, tags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how or how event recognizers interact with each other. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate whether a sub-event is delivered to a different level in the view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the respective event identifier 180 activates the event handler 190 associated with the event. In some embodiments, the respective event identifier 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a marker associated with the recognized event, and the event handler 190 associated with the marker retrieves the marker and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about sub-events without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the sequence of sub-events or to actively participating views. Event handlers associated with the sequence of sub-events or with actively participating views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates a phone number used in contacts module 137 or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 176 creates a new user interface object or updates the location of a user interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It should be understood that the above discussion of event processing with respect to user touches on a touch sensitive display also applies to other forms of user input utilizing an input device to operate multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds; contact movements on the touchpad, such as taps, drags, scrolls, and the like; inputting by a stylus; movement of the device; verbal instructions; detected eye movement; inputting biological characteristics; and/or any combination thereof, is optionally used as input corresponding to sub-events defining the event to be identified.

FIG. 2 illustrates a portable multifunction device 100 with a touch screen (e.g., touch-sensitive display system 112 of FIG. 1A) in accordance with some embodiments. The touch screen optionally displays one or more graphics within the User Interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more of these graphics by making gestures on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics will occur when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up, and/or down), and/or a rolling of a finger (right to left, left to right, up, and/or down) that has made contact with device 100. In some implementations, or in some cases, inadvertent contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over the application icon optionally does not select the corresponding application.

Device 100 optionally also includes one or more physical buttons, such as a "home" button, or menu button 204. As previously described, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen display.

In some embodiments, device 100 includes a touch screen display, menu buttons 204, push buttons 206 for powering the device on/off and for locking the device, one or more volume adjustment buttons 208, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, and docking/charging external port 124. Pressing the button 206 optionally serves to turn the device on/off by pressing the button and holding the button in a pressed state for a predefined time interval; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlocking the device or initiating an unlocking process. In some embodiments, device 100 also accepts voice input through microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on touch-sensitive display system 112, and/or one or more tactile output generators 163 for generating tactile outputs for a user of device 100.

Fig. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop, desktop, tablet, multimedia player device, navigation device, educational device (such as a child learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to one or more tactile output generators 163 described above with reference to fig. 1A) for generating tactile outputs on device 300, a sensor 359 (e.g., a touch-sensitive sensor, an optical sensor, a contact intensity sensor, a proximity sensor, an acceleration sensor, a gesture, and/or a magnetic sensor similar to sensors 112, 164, 165, 166, 167, 168, and 169 described above with reference to fig. 1A). Memory 370 includes high speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to those stored in memory 102 of portable multifunction device 100 (fig. 1A), or a subset thereof. Further, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk editing module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above identified elements in fig. 3 is optionally stored in one or more of the previously mentioned memory devices. Each of the identified modules corresponds to a set of instructions for performing the functions described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. Further, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed to embodiments of a user interface ("UI") optionally implemented on portable multifunction device 100.

Fig. 4A illustrates an exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

one or more signal strength indicators 402 for one or more wireless communications (e.g., cellular signals and Wi-Fi signals);

time 404;

a bluetooth indicator 405;

a battery status indicator 406;

tray 408 with common application icons such as:

an icon 416 of the telephony module 138 labeled "telephony", the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;

an icon 418 of the email client module 140 labeled "mail", the icon 418 optionally including an indicator 410 of the number of unread emails;

icon 420 of browser module 147, labeled "browser"; and

an icon 422 labeled "iPod" of video and music player module 152 (also referred to as iPod (trademark of Apple inc.) module 152); and

icons for other applications, such as:

icon 424 of IM module 141 labeled "text";

icon 426 of calendar module 148 labeled "calendar";

icon 428 of image management module 144 labeled "photo";

icon 430 of camera module 143 labeled "camera";

icon 432 of online video module 155 labeled "online video";

an icon 434 of the stock market desktop applet 149-2 labeled "stock market";

icon 436 of map module 154 labeled "map";

icon 438 labeled "weather" for weather desktop applet 149-1;

icon 440 of alarm clock desktop applet 169-6 labeled "clock";

icon 442 labeled "fitness support" for fitness support module 142;

icon 444 of notepad module 153 labeled "notepad"; and

an icon 446 that sets applications or modules, the icon 446 providing access to settings of the device 100 and its various applications 136;

it should be noted that the icon labels shown in fig. 4A are merely exemplary. For example, in some embodiments, icon 422 of video and music player module 152 is labeled "music" or "music player". Other tabs are optionally used for the various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

Fig. 4B illustrates an exemplary user interface on a device (e.g., device 300 in fig. 3) having a touch-sensitive surface 451 (e.g., tablet or trackpad 355 in fig. 3) separate from the display 450. Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) to detect the intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 359 to generate tactile outputs for a user of device 300.

Fig. 4B illustrates an exemplary user interface on a device (e.g., device 300 in fig. 3) having a touch-sensitive surface 451 (e.g., tablet or trackpad 355 in fig. 3) separate from the display 450. Although many of the examples that follow will be given with reference to input on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in fig. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in fig. 4B) has a major axis (e.g., 452 in fig. 4B) that corresponds to a major axis (e.g., 453 in fig. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at locations that correspond to corresponding locations on the display (e.g., in fig. 4B, 460 corresponds to 468 and 462 corresponds to 470). Thus, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device while the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contact, single-finger tap gesture, finger swipe gesture, etc.), it should be understood that in some embodiments, one or more of these finger inputs are replaced by inputs from another input device (e.g., mouse-based inputs or stylus inputs). For example, the swipe gesture is optionally replaced by a mouse click (e.g., rather than a contact), followed by movement of the cursor along the path of the swipe (e.g., rather than movement of the contact). As another example, a flick gesture is optionally replaced by a mouse click (e.g., instead of detecting a contact, followed by ceasing to detect a contact) while the cursor is over the location of the flick gesture. Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mouse and finger contacts are optionally used simultaneously.

As used herein, the term "focus selector" refers to an input element that is used to indicate the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in fig. 1A or the touch screen in fig. 4A) that enables direct interaction with user interface elements on the touch screen display, a contact detected on the touch screen serves as a "focus selector" such that when an input (e.g., a press input by the contact) is detected at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by moving the focus from one button to another using tab or arrow keys); in these implementations, the focus selector moves according to movement of the focus between different regions of the user interface. Regardless of the particular form taken by the focus selector, the focus selector is typically a user interface element (or contact on a touch screen display) that is controlled by a user to communicate a user-desired interaction with the user interface (e.g., by indicating to the device an element with which the user of the user interface desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or touchscreen), the location of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (as opposed to other user interface elements shown on the device display).

As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a substitute for (surrogate for) the force or pressure of a contact on the touch-sensitive surface. The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average or sum) to determine an estimated contact force. Similarly, the pressure sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereof, the capacitance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof and/or the resistance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some implementations, the substitute measurement of contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). The intensity of the contact is used as an attribute of the user input, allowing the user to access additional device functionality that the user would otherwise not have readily accessible on a smaller sized device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical/mechanical controls such as knobs or buttons).

In some embodiments, contact/motion module 130 and/or contact/motion module 430 use a set of one or more intensity thresholds to determine whether an operation has been performed by the user (e.g., determine whether the user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined as a function of software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and may be adjusted without changing the physical hardware of device 100). For example, the mouse "click" threshold of the trackpad or touch screen display may be set to any one of a wide range of predefined thresholds without changing the trackpad or touch screen display hardware. Additionally, in some embodiments, a user of the device is provided with software settings for adjusting one or more intensity thresholds in the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting multiple intensity thresholds at once with a system-level click on the "intensity" parameter).

As used in the specification and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples acquired during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detecting contact, before detecting contact liftoff, before or after detecting contact start movement, before or after detecting contact end, before or after detecting an increase in intensity of contact, and/or before or after detecting a decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: maximum value of contact strength, mean value of contact strength, average value of contact strength, value at the first 10% of contact strength, half maximum value of contact strength, 90% maximum value of contact strength, and the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact whose characteristic intensity does not exceed the first threshold results in a first operation, a contact whose characteristic intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose characteristic intensity exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether to perform one or more operations (e.g., whether to perform a respective option or forgo performing a respective operation) rather than to determine whether to perform a first operation or a second operation.

In some implementations, a portion of the gesture is recognized for determining the feature intensity. For example, the touch-sensitive surface may receive a continuous swipe contact that transitions from a starting location and reaches an ending location (e.g., a drag gesture) where the intensity of the contact increases. In this example, the characteristic strength of the contact at the end position may be based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only a portion of the swipe contact at the end position). In some implementations, a smoothing algorithm may be applied to the intensity of the swipe gesture before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: a non-weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for the purpose of determining the feature intensity.

The user interface diagrams described below optionally include various intensity diagrams that illustrate contacts on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold, IT)₀Light press pressure intensity threshold IT_LDeep compression strength threshold IT_DAnd/or one or more other intensity thresholds). This intensity map is typically not part of the displayed user interface, but is provided to assist in interpreting the map. In some embodiments, the light press intensity threshold corresponds to an intensity that: at which intensity the device will performOperations typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity that: at which intensity the device will perform a different operation than that typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when the characteristic intensity is detected to be below the light press intensity threshold (e.g., and above the nominal contact detection intensity threshold IT)₀A contact lower than the nominal contact detection intensity threshold is no longer detected), the device will move the focus selector in accordance with movement of the contact across the touch-sensitive surface without performing the operations associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface drawings.

In some embodiments, the response of the device to an input detected by the device depends on criteria based on the intensity of the contact during the input. For example, for some "tap" inputs, the intensity of the contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to an input detected by the device depends on criteria including both the intensity of contact during the input and time-based criteria. For example, for some "deep press" inputs, the intensity of a contact that exceeds a second intensity threshold, greater than the first intensity threshold of a light press, triggers a second response during the input as long as a delay time elapses between the first intensity threshold being met and the second intensity threshold being met. The delay time is typically less than 200ms in duration (e.g., 40ms, 100ms, or 120ms, depending on the magnitude of the second intensity threshold, wherein the delay time increases as the second intensity threshold increases). This delay time helps avoid accidental deep press inputs. As another example, for some "deep press" inputs, a period of reduced sensitivity will occur after the first intensity threshold is reached. During this period of reduced sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detecting a deep press input does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholds and/or corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application execution, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., environmental noise), focus selector position, and so forth. Exemplary factors are described in U.S. patent applications 14/399,606 and 14/624,296, which are incorporated by reference herein in their entirety.

Contact characteristic intensity from below light press intensity threshold IT_LTo be between the light press intensity threshold IT_LAnd deep press intensity threshold IT_DThe intensity in between is sometimes referred to as a "light press" input. Characteristic intensity of contact from below deep press intensity threshold IT_DIs increased to above the deep press strength threshold IT_DIs sometimes referred to as a "deep press" input. Contact characteristic intensity from below contact detection intensity threshold IT₀To be intermediate the contact detection intensity threshold IT₀And light press intensity threshold IT_LIs sometimes referred to as detecting contact on the touch surface. Characteristic intensity of contact from above contact detection intensity threshold IT₀Is reduced to below the contact detection intensity threshold IT₀Is sometimes referred to as detecting lift-off of the contact from the touch surface. In some embodiments, IT₀Is zero. In some embodiments, IT₀Greater than zero in some illustrations, a shaded circle or ellipse is used to represent the intensity of the contact on the touch-sensitive surface. In some illustrations, circles or ellipses without shading are used to represent respective contacts on the touch-sensitive surface without specifying the intensity of the respective contacts.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting a respective press input performed with a respective contact (or contacts), wherein the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the respective operation is performed in response to detecting that the intensity of the respective contact increases above the press input intensity threshold (e.g., performing the respective operation on a "down stroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press input threshold (e.g., the respective operation is performed on an "up stroke" of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental input sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold having a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., the respective operation is performed on an "up stroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., depending on the circumstances, the increase in contact intensity or the decrease in contact intensity).

For ease of explanation, the description of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input is optionally triggered in response to detecting: the intensity of the contact increases above the press input intensity threshold, the intensity of the contact increases from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, the intensity of the contact decreases below the press input intensity threshold, or the intensity of the contact decreases below the hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples in which operations are described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operations are optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on the time-based criteria being met (e.g., a delay time between reaching the first intensity threshold and reaching the second intensity threshold has elapsed).

User interface and associated process

Attention is now directed to implementations of a user interface ("UI") and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contacts with the touch-sensitive surface.

Fig. 5A-5V illustrate exemplary user interfaces for sharing music with other users, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in fig. 9A-9F. Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in fig. 4B.

Fig. 5A-5F show examples of a check-in user interface that provides the user with the option to check-in music sharing and selectively mark playlists as public or private. In some embodiments, playlists that are marked as public are accessible to other users having a predetermined relationship with the user of device 100. In some embodiments, playlists that are marked as public are presented to other users as music recommendations. In some embodiments, playlists marked as private are not accessible to other users having a predetermined relationship with the user of device 100. In some embodiments, playlists that are marked as private are not presented to other users as music recommendations. In some embodiments, the predetermined relationship refers to the user of device 100 connecting to other users via a music recommendation engine. In some embodiments, the predetermined relationship refers to other users having corresponding contact entries in the address book of the user of the device 100.

Fig. 5A shows a setup screen 502 that provides the user with the option to register for music sharing. In the example of FIG. 5A, the setup screen 502 includes affordances 504a and 504 b. The affordance 504a, when activated, triggers registration for music sharing. The affordance 504b, when activated, does not trigger registration for music sharing. In the example of FIG. 5A, device 100 receives user input 506 at a location corresponding to affordance 504 a. The user input 506 corresponds to a request for registering music sharing.

FIG. 5B illustrates a profile creation screen 508 that allows a user to create a profile for the user. In some embodiments, device 100 presents profile creation screen 508 in response to receiving a request to register for music sharing. For example, in some embodiments, device 100 presents profile creation screen 508 in response to receiving user input 506 shown in fig. 5A. The profile creation screen 508 includes various data fields 510 that allow the user to enter information about the user. In some examples, data field 510 allows the user to provide the user's name, the user's username, password, music preferences, and the like.

Fig. 5C shows a share option screen 516 that provides the user with the option to share music with each person or with a particular person selected by the user. In the example of FIG. 5C, sharing options screen 516 includes affordances 518a and 518 b. Affordance 518a, when activated, allows a user to share music with everyone. In some embodiments, each person refers to all people who have a corresponding contact entry in the user's address book and have registered for music sharing. In some embodiments, everyone refers to all people who have registered for music sharing (e.g., even people who do not have a corresponding contact entry in the user's address book). The affordance 518b, when activated, allows the user to share music with a particular person selected by the user. In the example of FIG. 5C, affordance 518a is activated. Thus, the user has selected to share music with everyone. In some embodiments, device 100 presents sharing options screen 516 after presenting profile creation screen 508 shown in FIG. 5B. In some embodiments, the user may select one of the affordances 518a and 518b, but may not select both of the affordances 518a and 518 b.

Fig. 5D illustrates a playlist share screen 524 that provides the user with the option to change the privacy settings for the user's playlist. In the example of fig. 5D, playlist share screen 524 includes representations 524a, 524b, and 524c of the user's playlists (hereinafter referred to as " playlist representations 524a, 524b, and 524 c" for brevity). As shown in FIG. 5D, playlist representations 524a, 524b, and 524c are associated with respective privacy affordances 526a, 526b, and 526 c. Privacy affordances 526a, 526b, and 526c indicate corresponding privacy settings for the playlist. In the example of FIG. 5D, privacy affordances 526a, 526b, and 526c include toggle switches with two mutually exclusive positions: an ON position corresponding to a public setting in which the playlist is being shared with other users, and an OFF position corresponding to a private setting in which the playlist is not being shared with other users. In the example of FIG. 5D, privacy affordances 526a, 526b, and 526c are set to the OFF position. Thus, in the example of fig. 5D, the playlists "Date Nite", "Work", and "Gym" are private and not shared with other users.

Fig. 5E-5F illustrate a sequence in which the device 100 receives a user input 528 for changing the privacy settings of a playlist for a user. In the example of fig. 5E, device 100 receives user input 528 (e.g., a tap input) at a location corresponding to privacy affordance 526b, which indicates privacy settings for a "Work" playlist. In FIG. 5E, the privacy affordance 526b is in the OFF position, indicating that the "Work" playlist is private and not shared with other users. The user input 528 corresponds to a request to switch the privacy affordance 526b from the OFF position to the ON position. In other words, the user input 528 corresponds to a request to change the privacy setting for the "Work" playlist from private to public. In other words, the user input 528 corresponds to a request to share a "Work" playlist with other users. Displaying the privacy affordances 526a, 526b, and 526c allows a user to selectively mark playlists as private or public, thereby providing an intuitive and user-friendly experience for sharing music with other users. Displaying the privacy affordance enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to explicitly share playlists with various users), and in addition, it enables users to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

As shown in FIG. 5F, in response to receiving the user input 528 shown in FIG. 5E, the device 100 switches the privacy affordance 526b from the OFF position to the ON position. The ON position of the privacy affordance 526b indicates that the "Work" playlist is public. Since the user has marked the "Work" playlist as public, the "Work" playlist is being shared with other users having a predetermined relationship with the user of device 100. For example, a "Work" playlist is presented as a music recommendation to other users connected to the user of device 100 via the music recommendation engine and/or social network. The OFF positions of the privacy affordances 526a and 526c indicate that the playlists "Date Nite" and "Gym" are private. Since the playlists "Date Nite" and "Gym" are private, the playlists "Date Nite" and "Gym" are not shared with other users having a predetermined relationship with the user of the device 100. For example, playlists "Date Nite" and "Gym" are not presented as music recommendations to other users connected to the user of device 100 via the music recommendation engine and/or social network. Playlist share screen 524 provides the user with the option of making some playlists public while keeping others private.

Fig. 5G-5H show a sequence in which the device 100 receives a user input 530 for changing the privacy settings for all playlists of the user. In the example of fig. 5G-5H, playlist share screen 524 includes playlist representation 524d, which represents the user's various playlists (e.g., all of the user's playlists, such as playlists "DateNite," "Work," and "Gym"). Playlist share screen 524 includes privacy affordance 526d associated with playlist representation 524 d. Privacy affordance 526d allows the user to control privacy settings for all playlists. In the example of fig. 5G, device 100 receives user input 530 corresponding to a request to change the privacy settings of all playlists from private to public. As shown in fig. 5H, in response to receiving user input 530, device 100 changes the privacy settings for all playlists from public to private. In the example of FIG. 5H, privacy affordances 526a, 526b, 526c, and 526d are in the ON position, indicating that all playlists are being shared with other users having a predetermined relationship with the user of device 100. Displaying the privacy affordance 526d allows a user to control privacy settings for multiple playlists (e.g., all playlists) by providing a single user input, thereby improving the efficiency of the device and providing a better user experience. Controlling privacy settings for multiple playlists (e.g., all playlists) with a single user input enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to controlling respective privacy settings for playlists), and in addition, it enables a user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 5I-5J illustrate sequences in which the device 100 provides a user with options to establish a predetermined relationship with other users. In the example of fig. 5I-5J, device 100 displays a follow-up screen 534 that includes representations 536a, 536b, and 536c of other users and corresponding follow-up affordances 538a, 538b, and 538c for following the other users. In some embodiments, a user may access music shared by another user by following the other user. In some examples, a user receives a music recommendation (e.g., playlist, individual music items) that includes music that other users have shared. In the example of fig. 5I, device 100 receives user input 540 selecting the follow affordance 538 a. User input 540 corresponds to a request to follow the user represented by representation 536a (e.g., user input 540 corresponds to a request to follow "Kelly"). As shown in fig. 5J, in response to receiving user input 540, device 100 triggers establishment of a follow-up relationship between the user and "Kelly". Device 100 displays the following badge 542a to indicate that the user is following "Kelly". Presenting the follow screen 534 and displaying the follow affordances 538a, 538b, and 538c allows the user to receive music recommendations that include music shared by other users, thereby reducing the need for a sequence of user inputs corresponding to manually requesting music of other users. Presenting the follow-up screen with follow-up affordances for other users enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requesting music from various other users), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to FIG. 5K, device 100 receives user input 544 at a location corresponding to affordance 504 b. The user input 544 corresponds to a request for not registering music sharing. In response to receiving user input 544, device 100 forgoes presentation of profile creation screen 508 shown in FIG. 5B. Fig. 5L shows a notification 546 reminding the user to register for music sharing. In the example of fig. 5L, the notification 546 includes a banner displayed toward the top of the touch-sensitive display. In some embodiments, activating the notification 546 triggers presentation of the profile creation screen 508 shown in fig. 5B. More generally, in some embodiments, in response to receiving a user input that activates the notification 546, the device 100 initiates a process for the user to register for music sharing. A presentation notification 546 alerts the user to register for the music share, providing the user with an option to register for the music share even if the user initially decides not to log in to the music share. Alerting the user to register for music sharing enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to a request to register for music sharing), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 5M, in some embodiments, the profile creation screen 508 provides the user with the option of creating a private profile. Creating a private profile allows a user to restrict access to the user's shared music. In the example of fig. 5M, profile creation screen 508 includes private profile affordance 548. As shown in fig. 5M, the private profile affordance 548 includes a toggle switch with two mutually exclusive positions: an ON position corresponding to a request to create a private profile and an OFF position corresponding to a request to create a public profile. In the example of fig. 5M, private profile affordance 548 is in the ON position, indicating that the user has selected to create a private profile. Providing the option of creating a private profile allows the user to restrict access to the user's shared music.

Fig. 5N illustrates device 100a associated with a second user (e.g., a user other than the user selected to create the private profile in fig. 5M). The device 100a displays a user profile 550 for a first user (e.g., the user in fig. 5M who selects to create a private profile). The user profile 550 includes a private profile indication 552 (e.g., a lock badge). The privacy profile indication 552 indicates that the user profile 550 is private. In some examples, the user profile 550 obscures at least a portion of the music shared by the first user. In the example of fig. 5N, the user profile 550 includes a follow request affordance 554 that allows the second user to submit a request for following the first user. Masking music shared by a first user allows the first user to restrict access to the shared music by requiring other users to submit follow-up requests, thereby providing the first user with more privacy.

Referring to fig. 5O, in some embodiments, the device 100 associated with the first user displays a follow-up request notification 556 indicating that the second user has submitted a follow-up request. In some embodiments, follow request notification 556 indicates that the second user has requested access to the music shared by the first user. In some embodiments, device 100 displays follow-up request notification 556 in response to the second user submitting a follow-up request (e.g., in response to the second user selecting follow-up request affordance 554 shown in fig. 5N). The device 100 receives a user input 558 selecting to follow the request notification 556. In some embodiments, user input 558 corresponds to a request for expansion of follow-up request notification 556. Displaying follow-up request notification 556 provides the user with the option to view follow-up requests from other users. Displaying the follow-up request notification 556 enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requests to view follow-up requests from other users), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to FIG. 5P, in response to receiving user input 558 shown in FIG. 5O, device 100 displays an expanded version 560 following request notification 556. Expanded version 560 provides the user with the option to accept the follow-up request, reject the follow-up request, and/or view the user profile of the second user. In the example of fig. 5P, expanded version 560 includes a decline affordance 560a for declining follow-up requests, a view profile affordance 560b for viewing a user profile of a requestor (e.g., Jessie Macintosh), and an accept affordance 560c for accepting follow-up requests. Displaying an expanded view 560 with options for rejecting/accepting user profiles following requests and viewing requesters provides more control and improved privacy for the user.

Referring to fig. 5Q, in some embodiments, the profile creation screen 508 provides the user with the option of requesting an authenticated account. In some embodiments, the verified account indicates that the user is a verified artist who has created music. In the example of fig. 5Q, the profile creation screen 508 includes a verification request affordance 562. In some embodiments, the verification request affordance 562 includes a checkbox with two mutually exclusive states: a selected status indicating that a verified account is requested and an unselected status indicating that a verified account is not requested. In the example of FIG. 5Q, the authentication request affordance 562 is in a selected state, indicating that the user has requested an authenticated account. In some implementations, requesting a verified account triggers a verification process to determine whether the user meets the verification criteria (e.g., whether the user is an artist).

Fig. 5R illustrates device 100a associated with a second user (e.g., a user other than the user selected to request the authenticated account in fig. 5Q). The device 100a displays a user profile 564 for a first user (e.g., the user associated with the device 100 shown in fig. 5Q). The user profile 564 includes a verified account indication 566 (e.g., a check mark). The verified account indication 566 indicates that the user profile 564 is verified (e.g., the user profile 564 meets verification criteria, e.g., the user profile 564 is for an artist). In some examples, the user profile 564 displays a representation 568 of a media container (e.g., music such as a music album, podcast, audio book, etc.) created by the artist. In some embodiments, the user profile 566 displays a user's playlist 570. Providing the user with the option of requesting a verified account allows the user to have a discernible user profile indicating that the user is an artist, thereby providing an improved user experience. Providing the option of requesting an authenticated account enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to submitting a request to establish an authenticated account), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 5S-5V, in fig. 5S, the share option screen 516 indicates that the affordance 518b is activated. The affordance 518b being activated corresponds to a request to share music with a particular person selected by the user (e.g., rather than sharing music with everyone). In response to the affordance 518b being activated, in some embodiments, the device 100 displays a people screen 572 shown in fig. 5T. The people screen 572 includes affordances 574a, 574b, and 574c that, when activated, display the corresponding category of people (e.g., all people, nearby people, or people with similar tastes). In the example of FIG. 5T, affordance 574a is activated. Thus, in FIG. 5T, the device 100 displays a representation 576a of all people in the user's address book that have corresponding contact entries. Representation 576a is optional. Thus, the user may select which people the user wants to share music with. In FIG. 5U, affordance 574b is activated. Thus, in fig. 5U, the device 100 displays a representation 576b of contacts that are nearby (e.g., within a threshold distance of the device 100, such as in the same city or country/region). Representation 576b represents a subset of representation 576a shown in figure 5T. In FIG. 5V, an affordance 574c is activated. Thus, in fig. 5V, the device 100 displays a representation 576c of contacts having similar music tastes 578 (e.g., listening to contacts having a degree of similarity to music listened to by the user). Representation 576c represents a subset of representation 576a shown in figure 5T. Displaying representations 576a, 576b, and/or 576c provides the user with the option of selecting the person with whom the user wants to share music, thereby providing the user with more control over music sharing and improving the user experience. Indicating similar musical tastes 578 enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests for viewing user profiles of other users to discern their musical tastes 578), and in addition, it enables users to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 6A-6N illustrate examples of a media browsing user interface according to some embodiments. The media browsing user interfaces in these figures are used to illustrate the processes described below, including the processes in fig. 10A-10E. Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in fig. 4B.

Fig. 6A illustrates an exemplary media browsing user interface 602. The media browse user interface 602 allows a user to browse through various media containers. In some embodiments, a media container refers to a playlist that includes a sequence of media items, an album that includes a collection of media items, and/or a single media item. In some embodiments, a media item refers to a music item such as a song. In the example of FIG. 6A, the media browsing user interface 602 displays categories of media containers (e.g., downloaded music, playlists, albums, and songs). The device 100 receives a user input 604 at a location corresponding to the playlist. The user input 604 corresponds to a request to display a view of the media browsing user interface 602 that includes a user's playlist.

Fig. 6B shows a view of a media browsing user interface 602 that includes representations of various playlists for a user. In the example of FIG. 6B, media browsing user interface 602 includes word Playlist representation 606a representing "Work Playlist", studio Playlist representation 606B representing "studio Playlist", and word kout Playlist representation 606c representing "Work kout Playlist". In some embodiments, other users having a predetermined relationship with the user can access the user's playlist. For example, other users connected to the user via a music recommendation engine can access the user's playlist. In some embodiments, other users who follow the user via the music recommendation engine can access the user's playlist. Thus, in some embodiments, other users interface with the user's playlist. For example, other users listen to the user's playlist.

In some implementations, the media browsing user interface 602 displays a splice mark for the representation of the playlist in response to the playlist satisfying the splice criteria. In some implementations, the engagement criteria for the playlist includes a requirement that at least one of the other users with whom the user has a predetermined relationship is engaging the playlist. In some implementations, interfacing with a playlist refers to listening to the playlist, downloading the playlist, sharing the playlist with another user, indicating a preference for the playlist (e.g., a like/favorite playlist), and/or adding the playlist to a media library. In the example of FIG. 6B, device 100 displays splice mark 608a for work playlist representation 606 a. Engagement marker 608a for Work Playlist representation 606a indicates that another user of device 100 with whom the user has a predetermined relationship is engaging "WorkPlaylist" (e.g., the other user is listening to "WorkPlaylist"). In some embodiments, the join indicia includes a badge that represents the other user that is joining the playlist. For example, the badge includes a profile picture of the other user that is being joined with the playlist. As shown in FIG. 6B, engagement indicia 608a includes a first badge 610a representing a first other user that is engaging work playlist. Engagement indicia for representations of media containers provides an intuitive and user-friendly experience to obtain information about other users' engagement with the media containers. Displaying engagement indicia for the media container enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display representations of other users engaging the media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending battery life of the device.

Fig. 6C shows: in some implementations, the engagement indicia for the representation of the media container changes as the engagement with the media container changes. For example, if the number of users engaged with the media container increases from one user to two users, the engagement tag includes badges that represent both users. In the example of FIG. 6C, the join mark 608a for the Work Playlist representation 606a includes a first badge 610a representing a first other user and a second badge 610b representing a second other user that is joining "Work Playlist". Increasing the number of badges included in the engagement tag provides an intuitive and user-friendly way for a user to obtain information about the number of users that are engaging the media container. Including badges of different users in the engagement tag for the media container enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display representations of other users being engaged with the media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending battery life of the device.

Fig. 6D shows: in some implementations, the device 100 arranges (e.g., sorts) representations of media containers based on respective engagement levels associated with the media containers. For example, in some embodiments, the device 100 arranges the representations of the media containers based on the respective number of other users that are engaging the media containers (e.g., based on the respective number of badges). In the example of FIG. 6D, the "Workout Playlist" representation 606c includes a splice mark 608 c. The splice mark 608c indicates that another user of the device 100 with whom the user has a predetermined relationship is splicing with "Workout Playlist". The engagement tag 608c includes a second badge 610b representing a second other user. In the example of FIG. 6D, the second other user is splicing with "Work Playlist" and "Workout Playlist". In fig. 6C and 6D, the ordering of playlist representations 606a, 606b, and 606C is different. In the example of fig. 6C-6D, the playlist representations 606a, 606b, and 606C are ordered based on the number of users that are engaging the playlist. Ranking the representations of the media containers based on their respective engagement levels indicates which media containers are being engaged the most, thereby providing a better user experience. Sorting the representations of the media containers based on their respective engagement levels enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input corresponding to scrolling through the representations to find the media container with the highest/lowest engagement level), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In the example of FIG. 6E, the splice mark 608a for the "Work Playlist" representation 606a includes a third badge 610c representing a third other user that is splicing with the "Work Playlist". In fig. 6E, device 100 receives user input 612 selecting workplayist representation 606 a. In some embodiments, the user input 612 corresponds to a request to display information about "Work Playlist". In the example of fig. 6E, device 100 receives user input 612 at a location corresponding to work playlist representation 612. Referring to FIG. 6F, in response to receiving user input 612, device 100 displays a Playlist screen 614 that includes information about "Work Playlist". The playlist screen 614 includes splice information 616 for "WorkPlaylist". The splice information 616 indicates which other users in a predetermined relationship with the user of the device 100 are splicing with "Work Playlist". In the example of FIG. 6F, the splice information 616 includes magnified badges 618a, 618b, 618c, and 618d representing other users that are splicing with "WorkPlaylist". Some of the enlarged badges displayed within the join information 616 are enlarged versions of the badges displayed on the playlist representation. For example, the magnified badges 618a, 618b, and 618c are magnified versions of badges 610a, 610b, and 610c, respectively, displayed on the work playlist representation 606 a. Displaying the magnified badges 618a, 618b, 618c, and 618d provides the user with an intuitive and user-friendly way to know which other users are engaging "Work Playlist". Displaying engagement information 616 for the media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to display a list of other users that are engaging the media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In the example of fig. 6F, the device 100 displays four magnified badges (e.g., magnified badges 618a, 618b, 618c, and 618d) within the splice information 616 of "Work Playlist". Thus, in the example of FIG. 6F, four other users are engaging "Work Playlist". However, in FIG. 6E, device 100 displays only three badges (e.g., badges 610a, 610b, and 610 c). In some embodiments, the device 100 limits the number of badges that are displayed as part of the engagement indicia. In the example of FIG. 6E, the device 100 limits the number of badges to three. In some examples, the device 100 displays badges representing the other users that are engaging the most with the media container. For example, in FIG. 6E, the device 100 displays badges 610a, 610b, and 610c representing Dale, Eric, and Breda, respectively, because Dale, Eric, and Breda engage more of the work plastics than other users. Limiting the number of badges avoids cluttering the media browsing user interface 602, thereby providing a user-friendly experience.

Fig. 6G to 6H show examples of the engagement type indicator. As described herein, in some embodiments, one of the other users interfaces with the media container by indicating a preference for the media container. In some examples, the other user interfaces with the media container by indicating that the other user likes the media container. In some examples, the other user engages with the media container by indicating to the other user to love the media container. More generally, in various embodiments, the other user indicates a preference for the container by assigning a preference score to the media container. In some embodiments, the first preference score corresponds to the other user favorites the media container and the second preference score corresponds to the other user favorites the media container. In the example of FIG. 6G, the device 100 displays a junction type indicator 620c associated with the enlarged badge 618c representing "Breda". For example, the engagement type indicator 620c is at least partially overlaid on the enlarged badge 618c representing "breda". The splice type indicator 620c includes a "like" symbol to indicate that "Breda" likes "word Playlist". In some embodiments, a "like" symbol indicates that "Breda" has assigned a first preference score to work playlist. Displaying the engagement type indicator provides an intuitive and user-friendly way for a user to obtain information about the engagement type associated with the media container. Providing information about the type of engagement by displaying the engagement type indicator enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to view the type of engagement), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

As described herein, in various embodiments, the engagement information for a media container (e.g., engagement information 616 for "WorkPlaylist") includes representations of other users that are engaging the media container (e.g., engagement information 616 includes magnified badges 618a.. 618 d). In some embodiments, the representations of the other users are arranged (e.g., ranked) based on the respective types of engagement associated with the other users. In the example of fig. 6H, device 100 displays a splice type indicator 620b associated with a magnified badge 618b representing "Eric". The splice type indicator 620b includes a "heart" symbol to indicate "Eric" love "Work Playlist". In some embodiments, the "heart" symbol indicates that "Eric" has assigned a second preference score to "Work Playlist". In some embodiments, the second preference score assigned by "Eric" to "Work Playlist" is higher than the first preference score assigned by "breda" to "Work Playlist". In some embodiments, the device 100 ranks the representations of the users based on respective preference scores assigned to the media containers by the users. Thus, in the example of FIG. 6H, device 100 orders the magnified badges such that magnified badge 618b representing "Eric" appears before magnified badge 618c representing "Breda". Ordering the representations of other users (e.g., badges representing the other users, such as the enlarged badges 618a.. 618d) based on the respective types of splices (e.g., splice type indicators 620b and 620c) provides the user with an intuitive and user-friendly way to obtain information about the type of splice associated with a media container (e.g., work playlist). Sorting the representations of other users based on the respective types of engagement enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input corresponding to scrolling through the representations to view representations of users associated with a particular type of engagement), and in addition, it enables users to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In the example of fig. 6I, the join mark 608a for the Work Playlist representation 606a includes a generic badge 610x that represents a group of other users that are joining "Work Playlist" (e.g., rather than displaying a badge 610a representing a single user that is joining "Work Playlist" (as shown in fig. 6B)). In some embodiments, the device 100 displays the generic badge 610x when the number of users being engaged with the media container is greater than a threshold number (e.g., 3, 5, 10, etc.). Device 100 receives user input 624 selecting work playlist representation 606 a. In response to receiving user input 624, device 100 displays Playlist screen 614, which includes information about "Work Playlist". As shown in fig. 6I, there are four other users who are joining "Work Playlist". Displaying a generic badge 610x (e.g., rather than displaying four badges representing four users who are engaging "Work Playlist") provides a clear indication that many users are engaging Work Playlist.

Referring to fig. 6J, device 100 receives user input 626 corresponding to a request to view more information about work playlist. In some implementations, the user input 626 includes a swipe-up gesture (e.g., the device 100 detects movement of the contact in an upward direction on the touch-sensitive display). As shown in FIG. 6K, in response to receiving the user input 626, the device 100 displays a representation 628 of a media item (hereinafter referred to as "media item representation 628" for brevity). In the example of FIG. 6K, the media items comprise songs and the media item representations 628 comprise representations of songs. In some implementations, the device 100 displays engagement indicia 630 for at least some of the media item representations 628. Splice mark 630 indicates the splicing of the other user with the corresponding media item. In some implementations, the device 100 arranges (e.g., sorts) the media item representations 628 based on respective engagement levels associated with the corresponding media items. For example, media item representations 628 for media items with which more users are engaging are displayed above media item representations 628 for media items with which fewer or no users are engaging. Displaying the engagement indicia for the media item representations 628 provides an intuitive and user-friendly interface for the user to obtain information regarding the engagement of other users with the various media items in the media container. Displaying splice marks for media items enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display representations of other users that are splicing to a particular media item), and in addition, it enables a user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In the example of fig. 6L, device 100 receives user input 632 at a location corresponding to engagement tag 608a for work playlist representation 606 a. For example, in some embodiments, device 100 receives user input 632 at a location corresponding to one or more of badges 610a, 610b, and 610c included in engagement badge 608 a. As described herein, in some embodiments, the number of badges in a splice mark is limited to a threshold number (e.g., three). Thus, in some embodiments, user input 632 corresponds to a request to view a list of users that are engaging work playlist. In response to receiving user input 632, device 100 displays overlay interface 634, which includes list 636 of users that are engaging "WorkPlaylist". The display list 636 provides the user with the splice information 616 of other users with "Work Playlist".

FIG. 6M illustrates an exemplary media recommendation screen 640 that provides media recommendations to a user. In the example of FIG. 6M, the media recommendation screen 640 includes a social recommendation portion 642 that recommends a media container that meets engagement criteria for the user of the device 100. In some embodiments, the media container satisfies the engagement criteria if other users with whom the user of device 100 has a predetermined relationship have engaged the media container. In the example of FIG. 6M, the social recommendation portion 642 includes representations 644a, 644b, and 644c for albums that meet the engagement criteria (hereinafter referred to as " album representations 644a, 644b, and 644 c" for brevity). Album representations 644a, 644b, and 644c include joint marks 646a, 646b, and 646c that indicate that other users are joining the album. As shown in FIG. 6M, in some embodiments, the social recommendation portion 642 recommends a media container only if other users with whom the user of the device 100 has a predetermined relationship are engaging the media container. Displaying the social recommendation portion 642 provides an intuitive and user-friendly interface for the user to view recommended media containers that the user of the device 100 is engaging with other users with whom the user has a predetermined relationship. Displaying the social recommendation portion 642 enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to transmitting requests to other users for music that other users are listening to), and in addition, it enables users to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In the example of FIG. 6M, the device 100 receives user input 648 corresponding to a request to view additional media recommendations. In some embodiments, the user input 648 includes a swipe-up gesture. As shown in fig. 6N, in response to receiving user input 648, device 100 displays a carefully organized recommendations section 650 that includes representations 652 for various media containers (e.g., playlists). In some embodiments, the orchestrated recommendation portion 650 is updated periodically (e.g., daily). Thus, in some embodiments, representation 652 changes periodically (e.g., daily). Representation 652 does not include join flags, for example, because the corresponding media container was not selected based on other users' joins with the media container. Displaying a carefully organized recommendations section 650 allows a user to view media recommendations that are not based on the engagement of other users, allowing the user to seek out different music and providing a rich user experience.

Fig. 7A-7T illustrate exemplary user interfaces displaying representations of media containers marked as recently played by a user. The user interfaces in these figures are used to illustrate the processes described below, including the processes in fig. 11A-11D. Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in fig. 4B.

Fig. 7A-7B illustrate a sequence in which the device 100 receives a request to display a recently played media container, and the device 100 displays a representation for the recently played media container. Fig. 7A illustrates an exemplary media browsing user interface 702 generated by a music application (e.g., the video and music player module 152 shown in fig. 3). The media browse user interface 702 allows a user to browse through various media containers. In some embodiments, a media container refers to a playlist that includes a sequence of media items, an album that includes a collection of media items, and/or a single media item. In some embodiments, a media item refers to a music item such as a song. In the example of FIG. 7A, the media browsing user interface 702 displays categories of media containers (e.g., downloaded music, playlists, albums, and songs). The media browsing user interface 702 includes affordances 704a, 704b.. 704e that, when activated, display different views of the media browsing user interface 702. Device 100 receives user input 706 at a location corresponding to affordance 704b. In some implementations, the user input 706 corresponds to a request to display a recently played media container.

Fig. 7B shows a view of the media browsing user interface 702 including a recently played portion 710. Recently played portion 710 displays a representation for media containers that have recently been played by a user of device 100. In some embodiments, the representation includes a corresponding icon. In some embodiments, the representations include respective selectable affordances. In other words, recently played portion 710 displays a representation of the media container recently played by the user account associated with the device (e.g., the media container played at the device or another device associated with the user account, such as a separate speaker or a computer or tablet). In the example of fig. 7B, recently played portion 710 includes representations 712 and 712a for two media containers that have recently been played by a user account associated with device 100. In some embodiments, the device 100 plays the media container in response to receiving verbal instructions from a user of the device 100. In some implementations, the device 100 displays the verbal indicator 714 to indicate that the media container is played in response to receiving verbal instructions. In some embodiments, the speech indicator 714 includes a symbol (e.g., an image of a microphone) indicative of speech input. In the example of fig. 7B, a verbal indicator 714 is overlaid on the representation 712a for "album DEF," indicating that "album DEF" is played in response to receiving verbal instructions. Displaying the verbal indicator 710 associated with the representation of the media container in the recently played portion 714 provides an intuitive and user-friendly way to indicate that the media container was played in response to verbal instructions. Displaying representations of media containers played in response to verbal instructions enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for subsequent verbal instructions identical to previous verbal instructions), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In the example of fig. 7C, the device 100 receives verbal instructions 720 a. In response to receiving the verbal instructions 720a, the device 100 plays the music requested by the verbal instructions 720 a. In the example of fig. 7C, the verbal instructions 720a include an artist name 722 that refers to the artist (e.g., "John Appleseed"). Thus, in response to receiving verbal instructions 720a, device 100 plays a media container created by the artist (e.g., device 100 plays an album created by the artist or a single song created by the artist). In the example of fig. 7C, device 100 plays an album created by "John Appleseed" (e.g., a media container associated with representation 712a shown in fig. 7B and 7D). The device 100 provides the user with the option of launching a music application. For example, device 100 displays a music application affordance 730 that, when activated, presents a user interface generated by a music application. In some implementations, the device 100 receives the verbal instructions 720a while the device 100 is displaying the home screen (e.g., while the user interface 400 shown in fig. 4A is being displayed). In some embodiments, the device 100 receives the verbal instructions 720a while the device 100 is displaying a user interface generated by an application other than a music application. In some embodiments, the device 100 receives the verbal instructions 720a while the device 100 is displaying a user interface generated by a music application (e.g., while the media browsing user interface 702 is displayed).

In the example of fig. 7D, the device 100 displays a representation 712a for "album DEF" after playing "album DEF". As described herein, the representation 712a includes verbal indicators 714 to instruct the device 100 to play "album DEF" in response to verbal instructions (e.g., verbal instructions 720a shown in fig. 7C). In the example of fig. 7D, the representation 712a includes at least a portion 721a of the verbal instructions 720 a. More generally, in some embodiments, the representation of the most recently played media container includes at least a portion of the verbal instructions that trigger the device 100 to play the media container. Including at least a portion of the verbal instructions in the representation of the media container provides an intuitive and user-friendly way to indicate verbal instructions that cause the device 100 to play the media container. Instructing verbal instructions enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for subsequent verbal instructions identical to previous verbal instructions), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 7E, the device 100 receives verbal instructions 720b to play music corresponding to a music genre 724 (e.g., a predefined category of music). In response to receiving the verbal instructions 720b, the device 100 plays music corresponding to the music genre 724 specified in the verbal instructions 720 b. In the example of fig. 7E, the device 100 plays a custom media container (e.g., a custom playlist) that includes media items corresponding to music genre 724. In some implementations, a custom media container refers to a media container that is generated in response to a request to play music that does not correspond to a pre-existing media container. In the example of fig. 7E, the device 100 generates (e.g., synthesizes) a "Hip-Hop" playlist in response to receiving the verbal instructions 720 b. The "Hip-Hop" playlist is a customized playlist that does not exist prior to the verbal instructions 720 b. In various embodiments, generating (e.g., synthesizing) a customized media container (e.g., a customized playlist, such as the "Hip-Hop" playlist shown in the examples of fig. 7E-7F) in response to a request (e.g., verbal instructions, such as verbal instructions 720b) for playing music enables the device to present the music even if the request does not correspond to a pre-existing media container, thereby improving operability of the device and providing a better user experience. Generating a custom media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to manually creating a media container or making repeated requests with different words when a particular word of the request fails to produce a media container with media matching the user's verbal instructions), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 7F, the apparatus 100 displays a representation 712b for the "Hip-Hop" playlist after playing the Hip-Hop playlist. As shown in fig. 7F, representation 712b includes verbal indicator 714 to indicate that device 100 recently played a "Hip-Hop" playlist in response to verbal instructions (e.g., verbal instructions 720b shown in fig. 7E). In the example of fig. 7F, the representation 712b includes at least a portion 721b of the verbal instructions 720 b. Representation 712b includes a custom container indication 713 to indicate that the Hip-Hop playlist is a custom playlist (e.g., rather than a pre-existing playlist). In the example of fig. 7F, custom container indication 713 includes a dark border. In various implementations, the custom container indication 713 distinguishes representations for custom media containers (e.g., icons for custom media containers) from representations for pre-existing media containers (e.g., icons for pre-existing media containers). For example, the custom container indication 713 changes the appearance of the representation for the custom media container such that the appearance of the representation for the custom media container is different than the appearance of the representation for the pre-existing media container. In other words, in various embodiments, the icon for the custom media container has a different appearance than for the pre-existing media container. In the example of FIG. 7F, representations 712a and 712b appear different due to custom container indication 713. Providing different appearances for representations of the custom media container and the pre-existing media container serves as an intuitive and user-friendly technique to distinguish the representations of the custom media container from the representations of the pre-existing media container. Providing different appearances for representations of custom media containers and representations of pre-existing media containers enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for subsequent user input to be made on one of the representations to discover whether the corresponding media container is a custom media container or a pre-existing media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 7G to 7H show: in some embodiments, the custom media container is a concatenation of two or more media containers carefully organized in editorial identity. In some embodiments, media containers that are carefully organized in editorial identity are created by a music service provider (e.g., by a subscription-based music service provider). Thus, in some embodiments, a media container orchestrated with an editing identity is a specific type of pre-existing media container, for example, because the media container orchestrated with the editing identity is orchestrated before a request for synthesizing a custom media container is received. In the example of fig. 7G, device 100 receives user input 732 at a location corresponding to representation 712b for the "Hip-Hop" playlist. In some embodiments, user request 732 corresponds to a request for displaying information about a "Hip-Hop" playlist. As shown in fig. 7H, in response to receiving user input 732, device 100 displays a playlist screen 734 that includes information about the "Hip-Hop" playlist. In The example of FIG. 7H, The "Hip-Hop" playlist is a concatenation of two carefully organized playlists 736a and 736b (e.g., The "The A-List Hip-Hop" playlist and The "Essential Sing-Along …" playlist) with editorial identities. Playlists 736a and 736b, which are carefully organized in editing identity, are associated with representations 738a and 738b, respectively. When the device 100 receives a user input selecting one of the representations 738a and 738b, the playlist screen 734 displays information about the corresponding playlist organized with an edit identity. Synthesizing the "Hip-Hop" playlist by splicing the carefully organized playlists 736a and 736b for editing identity enables the device 100 to present the "Hip-Hop" playlist in response to receiving the verbal instructions 720b shown in fig. 7E, thereby improving the functionality of the device 100 and providing a better user experience. More generally, in various embodiments, synthesizing a custom media container by splicing two or more media containers organized with an editing identity enables device 100 to present the custom media container in response to receiving verbal instructions to play music corresponding to the custom media container. The composite custom media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to manually creating custom media containers), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 7I-7J illustrate sequences in which the device 100, in response to verbal instructions referring to a particular artist, presents a pre-existing media container that includes only media items created by the particular artist. In the example of FIG. 7I, the device 100 receives verbal instructions 720c that include a designation 726 for an artist (e.g., "apple the mapper"). In some embodiments, the designation 726 for artist is the artist name of the artist. In response to receiving the verbal instructions 720c, the device 100 plays a media container (e.g., an album or playlist) that includes the media items created by the artist. In some embodiments, the media container includes only media items created by the artist. In the example of fig. 7I-7J, the device 100 plays an album created by the artist associated with the designation 726 for the artist (e.g., an "App Wrap" album). Referring to fig. 7J, recently played portion 710 includes a representation 712c for the media container (e.g., the "App Wrap" album) that device 100 recently played in response to receiving verbal instructions 720 c. By playing a media container that includes only media items created by a particular artist referred to in the verbal instructions, the device provides the user with an option to play media items created by the particular artist.

Fig. 7K-7L illustrate sequences in which the device 100 presents a customized media container including media items created by a particular artist and related media items created by other artists in response to verbal instructions that include predefined keywords other than those referring to the particular artist. In the example of FIG. 7K, the device 100 receives verbal instructions 720d that include predefined keywords 728 (e.g., "station") and a reference 726 to an artist (e.g., "apple the mapper"). In some embodiments, the predefined keywords 728 include words or phrases such as "station. In response to receiving the verbal instructions 720d, the device 100 plays a media container (e.g., a radio station or playlist) that includes related media items related to the specified artist but created by other artists, and optionally media items created by the artist. In some embodiments, the related media items are from the same genre of music as the media items created by the artist indicated by the reference 726 to the artist. In the example of fig. 7K-7L, the device 100 plays a station radio (e.g., "Apple the ripper at APP10 …") that includes songs created by "Apple the ripper" and related songs created by other artists (e.g., rap songs created by other rap singers from the same year as "Apple the ripper"). Referring to fig. 7L, recently played portion 710 includes a representation 712d of a media container (e.g., "apple ripper at APP10 …" station broadcaster) that device 100 recently played in response to receiving verbal instructions 720 d. By playing a media container that includes media items created by a particular artist as well as related media items created by other artists, the device provides the user with the option of seeking media items created by other artists, thereby enhancing the user experience. Playing related media items in addition to those created by a particular artist enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to effectuating playback of the related media items), and in addition, it enables a user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 7M-7N illustrate sequences in which the device 100 presents media containers according to a media taste profile of a user. In some embodiments, the media taste profile indicates a preferred genre of music by the user. In such embodiments, the device 100 presents a media container that includes media items belonging to a user's preferred music genre. In some implementations, the media taste profile indicates artists that the user likes. In such embodiments, the device 100 presents a media container that includes media items created by artists that the user likes. In the example of fig. 7M, the device 100 receives verbal instructions 720e corresponding to instructions for playing music without specifying which music to play (e.g., without referring to artist and/or genre of music). In response to receiving the verbal instructions 720e, the device 100 plays a media container that includes media items that satisfy the user's media taste profile. In the example of fig. 7M through 7N, the apparatus 100 plays a custom station broadcast station. In some implementations, a custom station broadcast station refers to a station broadcast station synthesized by the apparatus 100 in response to receiving the verbal instructions 720 e. In other words, the custom station broadcast station does not exist until the verbal instructions 720e are received. The custom station broadcast station includes media items that satisfy a user's taste profile. For example, if the user's media taste profile indicates that the user likes rap music, the custom radio station includes rap songs. Referring to fig. 7N, recently played portion 710 includes a representation 712e for a media container (e.g., a custom station broadcaster) that device 100 recently played in response to receiving verbal instructions 720 e. Because the custom station broadcast station did not exist prior to receiving the verbal instructions 720e, the representation 712e includes a custom container indication 713 to indicate that the representation 712e is for a custom station broadcast station. By playing the media container according to the user's media taste profile, the device provides the user with the option to listen to the user's preferred media items without explicitly specifying artists and/or music genres, thereby improving the efficiency of the device 100 and providing a better user experience. Playing a media container according to a user's media taste profile enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to manually selecting media items that meet the user taste), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 7O-7P illustrate sequences in which the device 100 presents media containers that include media items being engaged by other users having a predetermined relationship with the user of the device 100. As described herein, in some embodiments, the predetermined relationship refers to a user of device 100 connecting to other users via a music recommendation network and/or a social network. In some embodiments, the device 100 presents the media items that the other users are engaging in response to receiving verbal instructions 720f that include a designation 729 to the other users (e.g., a predefined word/phrase referring to the other users, such as "my friend," "my contact," "my connection," "my follower," etc.). In the example of FIG. 7O, the designation 729 to the other user includes the phrase "My friends". In response to detecting the designation 729 to the other user, the device 100 plays the media container that includes the media item that the other user is engaging. In the example of fig. 7O-7P, the device 100 plays a custom station radio that includes songs that the user's friends are engaging (e.g., listening, downloading, liking, love, explicit sharing, etc.). Referring to fig. 7P, recently played portion 710 includes a representation 712f of a media container (e.g., a custom station broadcaster) that device 100 recently played in response to receiving verbal instructions 720 f. Because the custom station broadcast station did not exist prior to receiving the verbal instructions 720f, the representation 712f includes a custom container indication 713 to indicate that the representation 712f is for a custom station broadcast station. By playing the media items that other users are engaging, the device 100 enables the user to listen to music that may be popular, thereby providing a better user experience. Playing the media item that the other user is engaging enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requesting the media item that the other user is engaging from the other user), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 7Q, device 100 receives user input 740 at a location corresponding to representation 712f for a custom station broadcaster that includes music that other users are engaging. In the example of fig. 7Q, user input 740 corresponds to a request to view a list of other users associated with the custom station broadcaster. In other words, in some embodiments, user input 740 corresponds to a request to view a list of other users who influence the content of the custom station broadcaster by engaging with a media item. In some implementations, the user input 740 is associated with a characteristic intensity that is greater than an intensity threshold (e.g., the user input 740 is a deep press or a hard press). As shown in fig. 7R, in response to receiving the user input 740, the device 100 displays an overlay interface 742 that includes representations 744 of other users that affect the media items in the custom station broadcaster corresponding to their engagement with the media items. Accordingly, the apparatus 100 allows the user to see which of the other users' music is included in the "music of my friend" customized station broadcasting station. The device 100 provides the user with the option of removing a particular user from the list of users who affect the content of the customized station broadcaster. In some examples, device 100 removes a particular user from the list in response to receiving user input (e.g., a swipe left gesture) at a location corresponding to respective representation 744 for the particular user. After removing a specific user from the list, music listened to by the specific user is not included in the "music of my friend" customized station broadcasting station. Accordingly, the apparatus 100 allows the user to select which of the other users' music is included in the "music of my friend" customized station broadcasting station.

In the example of fig. 7S, device 100 receives user input 746 at a location corresponding to representation 712f for a custom station broadcaster that includes music that satisfies the splice criteria (e.g., music that the user of device 100 is splicing with other users having a predetermined relationship). In some embodiments, user input 746 corresponds to a request to view additional information about the custom station broadcaster. For example, user input 746 corresponds to a request to view a list of individual media items in a custom station broadcaster. As shown in fig. 7T, in response to receiving user input 746, device 100 displays a station broadcast station screen 748 including information about the customized station broadcast station. In the example of fig. 7T, station radio screen 748 includes a representation 750 for media items (e.g., songs) in a custom station radio. As shown in fig. 7T, some of the representations 750 include respective engagement indicia 752 indicating engagement by other users having a predetermined relationship with the user of the device 100. The splice mark 752 is displayed as an intuitive and user-friendly way to indicate which of the other users are splicing with a particular media item in the custom station broadcaster. Displaying splice marks for media items enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display representations of other users that are splicing to a particular media item), and in addition, it enables a user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 8A-8X illustrate exemplary user interfaces that allow a first user (e.g., a user of device 100) to hide the first user's engagement with one or more media containers. Hiding the engagement of the first user with the media container may prevent other users in a predetermined relationship with the first user (e.g., other users who are following the user or have a friendship with the first user) from seeing the engagement of the first user with the hidden media container, thereby improving privacy for the first user. The user interfaces in these figures are used to illustrate the processes described below, including the processes in fig. 12A-12E. Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in fig. 4B.

Referring to fig. 8A, in some embodiments, device 100 displays an exemplary media engagement user interface 802. In the example of fig. 8A, the media engagement user interface 802 includes a recently played portion 810 that includes a representation of a media container that has recently been played for the device 100. The media engagement user interface 802 includes a representation of a media container for which a first user (e.g., a user of the device 100) has satisfied engagement criteria. In some implementations, the engagement criteria for the media container include a prerequisite that the first user has engaged (e.g., listened to, downloaded, indicated a preference for, shared with other users, etc.) the media container. In the example of FIG. 8A, the media engagement user interface 802 includes representations 812a and 812b for "album ABC" and "album FED," respectively. In the example of FIG. 8A, representations 812a and 812b are displayed in recently played portion 810. Thus, "album ABC" and "album FED" satisfy the engagement criteria, for example, because the first user has engaged "album ABC" and "album FED". In some embodiments, the representations 812a and 812b are displayed in another portion of the media engagement user interface 802 (e.g., in a portion other than the recently played portion 810, such as in a library portion of the media engagement user interface 802).

Fig. 8B shows a second device 100a corresponding to a second user. The second device 100a is displaying a public version 804 of the user profile for the first user (e.g., the user of the device 100 shown in fig. 8A). The public version 804 of the user profile for the first user includes information about the first user. In some embodiments, the public version of the user profile 804 for the first user includes a relationship indication 805 indicating that the second user has a predetermined relationship with the first user (e.g., the second user is connected to the first user). In the example of fig. 8B, the relationship indication 805 indicates that the second user is following the first user. In some embodiments, following the first user allows the second user to view a representation of the media container that the first user is engaging. In other words, following the first user allows the second user to view the music the first user is listening to. In some embodiments, following the first user allows the second user to receive (e.g., from a music recommendation engine) a music recommendation that includes the media container that the first user is engaging. In the example of fig. 8B, the published version of the user profile 804 for the first user includes a listening portion 806 that includes a representation of a media container that the first user is engaging. In the example of FIG. 8B, the listening portion 806 includes representations 812a and 812B for "album ABC" and "album DEF", respectively. The inclusion of representations 812a and 812b in the listening section 806 indicates that the first user recently listened to "album ABC" and "album DEF". In some embodiments, the public version of the user profile 804 for the first user includes badges 807 for other users with whom the first user has a predetermined relationship.

Fig. 8C-8F illustrate sequences in which the device 100 provides the first user with the option of hiding the first user's engagement with the media container. In the example of fig. 8C, the device 100 receives the user input 820 at a location corresponding to the representation 812b for "album FED". In some implementations, the user input 820 corresponds to a request to display a menu that provides the user with options to perform various operations associated with the "album FED". For example, as shown in fig. 8D, in response to receiving user input 820, device 100 displays menu 822. Menu 822 includes various affordances 824 that, when activated, trigger operations associated with "album FED". In the example of fig. 8D, one of the affordances 824 includes a hidden affordance 824 a. Hiding affordance 824a provides the user with the option of hiding the first user's engagement with "album FED". In fig. 8C-8D, in response to activating the hidden affordance 824a, the device 100 hides the engagement of the first user with the "album FED" such that other users with whom the first user has a predetermined relationship (e.g., a second user corresponding to the second device 100a shown in fig. 8B) cannot see that the first user is listening to the "album FED". In various embodiments, hiding the option of engaging with the media container provides a higher level of privacy for the first user, thereby improving the user experience.

Referring to FIG. 8E, device 100 receives user input 826 at a location corresponding to hidden affordance 824 a. The user input 826 corresponds to a request to hide the first user's engagement with the "album FED". In response to receiving the user input 826, the device 100 hides the first user's engagement with the "album FED". In some embodiments, concealing the splice comprises masking the splice of the first user. In some embodiments, hiding the splice comprises forgoing transmission of data indicating the splice of the first user. In some embodiments, hiding the splice comprises tracking transmission of data indicative of the splice of the first user. Hiding the first user's engagement with the "album FED" allows the user to keep the engagement private. In other words, hiding the first user's engagement with the "album FED" prevents other users from knowing that the first user is engaging with the "album FED," thereby improving controllability of the device 100 by providing the user with the option of selecting a higher level of privacy. Hiding the engagement of the first user with the media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requests to delete the media container or stop participating in music sharing to engage the media container without notifying them of engagement with the media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 8F illustrates the device 100 changing the appearance of the representation of the media container after receiving a request to hide the engagement of the first user with the media container. The changing appearance of the representation of the media container indicates that the media container has been hidden from public viewing. In other words, changing the appearance of the representation of the media container indicates that the first user's engagement with the media container is hidden from other users in a predetermined relationship with the first user (e.g., the other users are not visible or obtain the first user's engagement with the media container). In the example of fig. 8F, the device 100 changes the appearance of the representation 812b for "album FED" after receiving a request to hide the first user's engagement with the "album FED" (e.g., after receiving the user input 826 shown in fig. 8E). For example, as shown in FIG. 8F, the representation 812b for "album FED" has a dark background 814b, while the representation 812a for "album ABC" has a bright background 814 a. More generally, in various embodiments, the device 100 changes the appearance of the representation by changing the visual characteristics of the representation. In some examples, changing the visual characteristic includes changing a boundary thickness (e.g., reducing the boundary thickness), changing a brightness level (e.g., reducing the brightness level), changing a font (e.g., making the font smaller and/or changing a color of the font), and/or changing a color of the representation (e.g., displaying the representation in gray).

In the example of fig. 8G, the second device 100a displays a published version 804 of the user profile for the first user. As shown in fig. 8G, after the device 100 receives a user input 826 (shown in fig. 8E) corresponding to a request to hide the first user's engagement with the "album FED," the second device 100a stops displaying the representation 812b for the "album FED. In other words, after the first user hides the first user's engagement with the "album FED," the published version 804 of the user profile for the first user stops displaying the representation 812b for the "album FED. Thus, other users with whom the first user has a predetermined relationship (e.g., a second user corresponding to the second device 100 a) cannot see that the first user is engaging with the "album FED". More generally, in various embodiments, after a first user requests to hide a first user's engagement with a particular media container, the first user's engagement with the particular media container is hidden from other users with whom the first user has a predetermined relationship (e.g., the public version 804 of the first user's user profile stops displaying a representation for the particular media container). Thus, hiding the engagement of the first user with a particular media container provides more privacy for the user, thereby enhancing the user experience.

In the example of fig. 8H, device 100a displays a private version 804a of the user profile for the first user. The private version of the user profile 804a for the first user includes an editing affordance 805a that, when activated, allows the first user to make changes to the user profile. The private version of the user profile 804a includes a listening portion 806a that includes a representation of the media container that the first user is engaging. In the example of fig. 8H, the listening portion 806a includes representations 812a and 812b for "album ABC" and "album DEF," respectively. As shown in fig. 8H, after device 100 receives user input 826 (shown in fig. 8E) corresponding to a request to hide the first user's engagement with the "album FED," device 100 changes the appearance of representation 812 b. In the example of FIG. 8H, the representation 812b for "album FED" has a dark background 814b, while the representation 812a for "album ABC" has a bright background 814 a. The changing appearance (e.g., dark background 814b) of representation 812b indicates that the first user's engagement with the "album FED" is hidden. In other words, the changing appearance of representation 812b indicates that the other users cannot see that the first user is engaging with the "album FED". More generally, in various embodiments, changing the appearance of the media container representation being displayed on the private version 804a of the user profile for the first user provides a clear indication that the engagement with the corresponding media container is hidden relative to other users. Indicating that engagement with the media container is hidden relative to other users enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to a request to display whether engagement with the media container is hidden), and in addition, it enables a user to use the device more quickly and efficiently, thereby reducing power consumption and extending battery life of the device.

Fig. 8I-8L illustrate sequences in which the device 100 sorts the representations of the media containers based on engagement of the first user with the media containers (e.g., based on frequency and/or recency of engagement). FIG. 8I shows a first display order 830a for representations 812a and 812 b. In the example of fig. 8I, device 100 displays representation 812a toward the left edge of the touch-sensitive surface and device 100 displays representation 812b toward the right edge of the touch-sensitive surface, e.g., because device 100 recently played "album ABC" more than "album FED". Device 100 receives user input 832 corresponding to a request to display menu 822. As shown in fig. 8J, device 100 displays menu 822 in response to receiving user input 832. Menu 822 includes a play affordance 824b that, when activated, causes device 100 to next play "album FED". Referring to fig. 8K, the device 100 receives a user input 834 corresponding to a request for playing "album FED" next. The device 100 plays "album FED" in response to receiving the user input 834. As shown in FIG. 8L, the device 100 reorders the representations 812a and 812b according to a second display order 830 b. According to the second display order 830b, the representation 812b is displayed towards the left side of the touch-sensitive surface and the representation 812a is displayed towards the right side of the touch-sensitive surface. The second display order 830b indicates that the device 100 recently played "album FED" more than "album ABC". As shown in the examples of fig. 8I-8L, the first user may engage with the media container even after the first user has requested that the engagement of the first user with the media container be hidden from other users. For example, a user may listen to "album FED" even after hiding the first user's engagement with the "album FED" from other users. As shown in the examples of fig. 8I-8L, the device 100 determines the display order of the representations for the media containers based on the engagement of the first user with the media containers, even if the engagement of the first user with the media containers is hidden from other users. Determining the display order of the representations for the hidden media containers allows the device 100 to position the representations so that the representations can be more easily accessed by the user. Determining the display order of the representations for the hidden media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input corresponding to scrolling through the representations to view the representations of the hidden media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 8M to 8P show sequences in which the device 100 unholds the engagement of the first user with the media container in response to receiving a request for unholding the engagement. In the example of fig. 8M, the device 100 receives a user input 836 at a location corresponding to the representation 812b for "album FED". User input 836 corresponds to a request to display menu 822. As shown in fig. 8N, in response to receiving user input 836, device 100 displays menu 822. In the example of fig. 8N, menu 822 includes a unhide affordance 824c that, when activated, unhides the first user's engagement with the media container (e.g., "album FED"). Referring to FIG. 8O, device 100 receives user input 838 at a location corresponding to unhide affordance 824 c. The user input 838 corresponds to a request to unhide the first user's engagement with the "album FED". Thus, in response to receiving the user input 838, the device 100 unholds the first user's engagement with the "album FED". In some embodiments, unhiding the join includes unmasking data indicating the first user's join with the "album FED". In some embodiments, unhiding the join includes resuming transmission of data indicating the first user's join with the "album FED". As shown in fig. 8P, after unhiding the first user's engagement with the "album FED," device 100 changes the appearance of representation 812b to indicate that the engagement with the "album FED" is no longer hidden. In the example of fig. 8P, device 100 switches the background of representation 812b from a dark background 814b to a bright background 814 a. Providing the user with the option of hiding and unhiding the user's engagement with a particular media container provides the user with more control over the user's privacy, thereby improving the operability of the device 100. Providing the option of hiding the engagement of the first user with the media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requests to delete the media container or stop participating in music sharing to engage the media container without announcing their engagement with the media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Fig. 8Q-8T illustrate that the other users cannot see the engagement of the first user with the media container after the first user hides the engagement of the first user with the media container. In the example of fig. 8Q, the second device 100a is displaying a recommendation module 850 that includes a music recommendation for the second user. In some embodiments, the recommendation module 850 includes a representation of the media container being listened to by other users in a predetermined relationship with the second user. In the example of fig. 8Q, recommendation module 850 includes representations 812b, 812d, and 812e for "album FED," "album GHI," and "album KLM," respectively. In the example of fig. 8Q, the recommendation module 850 includes a representation 812b for "album FED" because the first user corresponding to the device 100 is listening to "album FED" and the first user's engagement with "album FED" is not hidden. As shown in FIG. 8R, when the first user hides the first user's engagement with the "album FED," the recommendation module 850 stops displaying the representation 812b for the "album FED. Thus, when the first user hides the engagement of the first user with a particular media container, then the particular media container is not recommended to other users based on the engagement of the first user with the particular media container. Hiding the engagement with the media container allows the first user to listen to the media container without letting the other users know that the first user is listening to the media container, thereby providing the first user with a higher level of privacy. Hiding the engagement of the first user with the media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requests to delete the media container or stop participating in music sharing to engage the media container without notifying them of engagement with the media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 8S, in some embodiments, recommendation module 850 includes badges 852 corresponding to respective other users. The recommendation module 850 displays badges 852 associated with the representations 812b, 812d, and 812 e. Badge 852 indicates engagement by the respective other user. In the example of fig. 8S, badge 852a represents a first user (e.g., corresponding to the user of device 100 shown in fig. 8E-8F). Since the badge 852a is overlaid on the representation 812b for "album FED," the badge 852a indicates that the first user is listening to "album FED. In the example of FIG. 8S, the badge 852a is visible because the first user' S engagement with the "album FED" is not hidden. As shown in FIG. 8T, when the first user chooses to hide the first user's engagement with the "album FED", then a badge 852a representing the first user is not displayed on the representation 812b for the "album FED". As shown in fig. 8T, the recommendation module 850 stops the display of the badge 852a in response to the first user hiding the first user's engagement with the "album FED". The recommendation module 850 maintains the display of the representation 812b because another user is engaging with the "album FED". Hiding the engagement with the media container allows the first user to listen to the media container without letting the other users know that the first user is listening to the media container, thereby providing the first user with a higher level of privacy.

Fig. 8U-8W illustrate sequences in which the device 100 displays privacy settings affordances corresponding to respective media containers. These affordances hide or unhide the engagement of the first user with the corresponding media container when activated. Referring to fig. 8U, device 100 displays privacy settings affordances 860a and 860b for representations 812a and 812b, respectively. In the example of fig. 8U-8W, the privacy settings affordances 812a and 812b include toggle switches with two mutually exclusive positions: an ON position and an OFF position. The ON position indicates that the engagement of the first user with the corresponding media container is not hidden. The OFF position indicates that the engagement of the first user with the corresponding media container is hidden. In some embodiments, the privacy settings affordances 860a and 860b are in the ON position by default. Thus, in such embodiments, the engagement of the first user with the media container is not hidden from other users by default. In the example of fig. 8V, device 100 receives user input 862 at a location corresponding to privacy settings affordance 860b for representation 812b of "album FED". The user input 862 corresponds to a request to switch the privacy settings affordance 860b from the ON position to the OFF position. The user input 862 corresponds to a request to hide the first user's engagement with the "album FED" from other users. As shown in fig. 8W, in response to receiving the user input 862, the device 100 hides the first user's engagement with the "album FED". In fig. 8W, the privacy settings affordance 860b is in the OFF position, indicating that the first user's engagement with the "album FED" is hidden from other users. Further, in fig. 8W, representation 812b has a dark background 814b (e.g., rather than a light background 814a) to indicate that the joint with "album FED" is hidden. Displaying the privacy settings affordances for the media containers (e.g., privacy settings affordances 860a and 860b) allows the first user to selectively hide/unhide the first user's engagement with a particular media container, thereby improving controllability of device 100 and providing a higher level of privacy for the first user. Displaying the privacy settings affordance enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to hide the first user's engagement with the media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In the example of fig. 8W, the device 100 receives the user input 864 at a location corresponding to the representation 812b for "album FED". The user input 864 corresponds to a request to view more information about "album FED". For example, the user input 864 corresponds to a request to view a list of various media items (e.g., songs) in the "album FED". As shown in fig. 8X, in response to receiving user input 864, device 100 displays an album screen 870, which displays information about "album FED". For example, album screen 870 displays representations 872 for songs in "album FED". The album screen 870 also includes an indication 874 that hides the engagement of the first user with the respective songs from other users. The first user's engagement with the individual songs in the "album FED" is hidden because the first user chooses to hide the first user's engagement with the "album FED". More generally, in various embodiments, when a user selects to hide a user's engagement with a particular media container, then the user's engagement with individual media items in that particular media container is also hidden. By hiding the user's engagement with the various media items when the user has selected to hide the engagement with the media container, the device 100 reduces the need for a sequence of user inputs corresponding to requests for hiding the engagement with the various media items, thereby improving the efficiency of the device 100 and providing a better user experience.

Fig. 9A-9F illustrate a flow chart of a method 900 of registering and/or selectively sharing music with other users. Method 900 is performed in a device (e.g., device 100 in fig. 1A or device 300 in fig. 3) having one or more processors, non-transitory memory, a display, and one or more input devices. In some embodiments, the display is a touch screen display and the one or more input devices are located on or integrated with the display. In some embodiments, the display is separate from the one or more input devices. Some operations in method 900 are optionally combined, and/or the order of some operations is optionally changed.

As described below, the method 900 provides a way to register for music sharing and/or selectively share music with other users. Referring to fig. 9A, a device receives (902), via the one or more input devices, a request to register for music sharing. In some embodiments, registering for music sharing allows the first user to share music with other users. For example, in FIG. 5A, device 100 receives user input 506 at a location corresponding to affordance 504 a.

After receiving the request, the device displays (904) a registration user interface on the display, the registration user interface including simultaneously displaying representations of a plurality of playlists created by the first user and privacy settings for the plurality of playlists. For example, in FIG. 5D, device 100 displays a playlist share screen 524 that includes representations 524a, 524b, and 524c of playlists and corresponding privacy affordances 526a, 526b, and 526 c. The privacy settings for the plurality of playlists have default values. For example, in FIG. 5D, privacy affordances 526a, 526b, and 526c are in the OFF position, indicating that the corresponding playlist is not shared with other users by default. The enrollment user interface includes a first affordance (906) (e.g., a first toggle switch for the first playlist, such as privacy affordance 526a shown in fig. 5D) corresponding to a first playlist of the plurality of playlists created by the first user and a second affordance (908) (e.g., a second toggle switch for the second playlist, such as privacy affordance 526b shown in fig. 5D) corresponding to a second playlist of the plurality of playlists created by the first user. Displaying the first affordance and the second affordance allows a user to selectively mark the first playlist and the second playlist as private or public, thereby providing an intuitive and user-friendly experience for sharing music with other users. Displaying the first affordance and the second affordance enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to explicitly share a playlist with various users), and furthermore, it enables users to use the device faster and more efficiently, thereby reducing power consumption and extending battery life of the device.

While displaying the privacy settings for the plurality of playlists, the device receives (910), via the one or more input devices, one or more user inputs (e.g., a user input that activates one or more of the first and second affordances and/or switches the first toggle switch ON and leaves the second toggle switch OFF) that changes the privacy settings for one or more of the plurality of playlists from the corresponding default privacy settings to the user-specified privacy settings. For example, in fig. 5E, device 100 receives user input 528 to change the privacy setting of the "Work" playlist from private to public. In some embodiments, the private playlist is a playlist that is not shared with any other users. In some embodiments, the public playlist is a playlist that is shared with one or more other users (e.g., the first user is visible on a user profile in a music sharing service such as the music recommendation engine described herein) as shown in fig. 5D, and in some embodiments, the default privacy is set to "private" for all playlists. However, in some embodiments, the default privacy setting is "public" for all playlists. In some embodiments, the default privacy setting is "my followers" for all playlists. In some embodiments, the default privacy settings are dependent on the content of the playlist or other user settings. In some embodiments, playlists that are marked as public are accessible to other users having a predetermined relationship with the user of device 100. In some embodiments, playlists that are marked as public are presented to other users as music recommendations. For example, in FIG. 5F, since the "Work" playlist is marked public, the "Work" playlist is accessible to other users having a predetermined relationship with the user. In some embodiments, playlists marked as private are not accessible to other users having a predetermined relationship with the user of device 100. In some embodiments, playlists that are marked as private are not presented to other users as music recommendations. For example, in FIG. 5F, since the "Date Nite" and "Gym" playlists are marked as private, the "Date Nite" and "Gym" playlists are not accessible to other users having a predetermined relationship with the user of device 100. In some embodiments, the predetermined relationship refers to the user of device 100 connecting to other users via a music recommendation engine. The user input allows the user to selectively mark the first playlist and the second playlist as private or public, thereby providing an intuitive and user-friendly experience for sharing music with other users.

After completing the registration, the device provides (912) access to the plurality of playlists of the first user to other users having a predetermined relationship with the first user (e.g., other users following the user, other users specifically identified by the user, and/or other users having a two-way "friend" relationship with the user or otherwise connected to the user) based on the privacy settings for the plurality of playlists. For example, in FIG. 5F, device 100 provides access to the "Work" playlist to other users having a predetermined relationship with the first user, but does not provide access to the "Date Nite" and "Gym" playlists. Providing access to playlists based on privacy settings of the playlists allows the device to selectively provide access to some playlists while denying access to other playlists, thereby providing the user with more control over which playlists are shared publicly. Providing access to playlists based on privacy settings of the playlists enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to explicitly share playlists with individual users), and in addition, it enables users to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

The privacy settings for the plurality of playlists comprise (914): in accordance with a determination that the one or more user inputs detected while displaying the enrollment user interface change the default privacy settings for the first playlist, the device provides other users connected with the first user access to the first playlist of the first user based ON user-specified privacy settings (e.g., if the first toggle switch is turned ON, then the first playlist is made public). For example, in FIG. 5F, based ON the privacy affordance 526b being in the ON position, the device 100 provides other users with access to a "Work" playlist. In accordance with a determination that the one or more user inputs detected while displaying the enrollment user interface change the default privacy settings for the second playlist, the device provides other users connected with the first user with access to the first user's second playlist based on user-specified privacy settings (e.g., if the second come-back toggle switch is turned OFF, the second playlist is made private). For example, in FIG. 5F, based on the privacy affordance 526c being in the OFF position, the device 100 does not provide other users access to the "Gym" playlist. Providing access to playlists based on user-specified settings for the playlists allows the device to selectively provide access to some playlists while denying access to other playlists, thereby providing the user with more control over which playlists are shared publicly.

Referring to fig. 9B, in some embodiments, during enrollment, the device receives (916) a request to create a profile. In accordance with a determination that the request is for creation of a public profile, the device creates a public profile for the first user. In accordance with a determination that the request is for creating a private profile, the device creates a private profile for the first user. In some embodiments, a public profile is a profile that can be viewed by any member of the music sharing service (e.g., by any member receiving a music recommendation from the music recommendation engine described herein). In some embodiments, the private profile is a profile that can only be viewed by members of the music sharing service that have been approved by the first user (e.g., by other users having a predetermined relationship with the first user). For example, in fig. 5M, the profile creation screen 508 includes a private profile affordance 548 that provides the user with the option of creating a private profile. In the example of fig. 5M, private profile affordance 548 is in the ON position, indicating that the user has selected to create a private profile. In some embodiments, receiving the request to create the profile includes (918) receiving one or more of a name, a username, and a photo. For example, in FIG. 5B, the profile creation screen 508 includes various data fields 510 that allow the user to provide information about the user (e.g., name, username, etc.). Providing the option of creating a private profile allows the user to restrict access to the user's shared music, thereby providing the user with more control and a better user experience.

In some embodiments, after completing the check-in, the device receives (920) a follow-up request from a second user (e.g., a user not in a predetermined relationship with the first user) when the profile for the first user is a private profile. In response to receiving the follow-up request, the device displays (920) a notification on the display indicating the follow-up request. For example, in fig. 5O, device 100 displays a follow request notification 556 indicating that device 100 has received a follow request from a second device corresponding to a second user. The notification includes a first affordance (e.g., an accept button, such as accept affordance 560c shown in fig. 5P) that accepts the follow-up request when activated, a second affordance (e.g., a reject button, such as reject affordance 560a shown in fig. 5P) that rejects the follow-up request when activated, and a third affordance (e.g., a view profile button, such as view profile affordance 560b shown in fig. 5P) that displays a user profile for the second user when activated. Displaying the follow-up request notification provides the user with the option of viewing follow-up requests from other users and deciding whether to accept or reject the follow-up request, thereby providing the user with more control over which other users may access the user's shared music. Displaying follow-up request notifications enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to view follow-up requests from other users), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device receives (922) a user selection to select one of the first affordance and the second affordance. After receiving the user selection (e.g., in response to receiving the user selection, or receiving the user selection followed by confirming the selection), in accordance with a determination that the user selection includes a selection of a first affordance (e.g., accept affordance 560c, shown in fig. 5P), the device provides (922) access to the first playlist of the first user to the second user based on the user-specified privacy setting (e.g., provides the second user with access to a public playlist of the first user), and in accordance with a determination that the user selection includes a selection of a second affordance (e.g., reject affordance 560a, shown in fig. 5P), the device denies (922) access to the plurality of playlists of the first user by the second user. The first affordance and the second affordance provide the user with an option to accept or reject follow-up requests from other users, thereby providing the user with more control over which other users may access the user's shared music.

Referring to fig. 9C, in some embodiments, during enrollment, the device displays (924) on the display a plurality of representations of other users that do not have a predetermined relationship with the first user. For example, in fig. 5I, device 100 displays representations 536a, 536b, and 536c for other users that do not have a predetermined relationship with the first user. In some examples, device 100 displays a representation for users that are not connected to the first user but are recommended to establish a predetermined relationship with the first user as a result of shared social contacts via one or more social networks. For example, device 100 displays a recommendation for a user who is a friend with, follows, or is followed by a first user on a social network. In some examples, device 100 displays a recommendation to the user that device 100 stores his contact information (e.g., phone number, email address, etc.) in an address book on device 100. The device displays relationship affordances corresponding to other users (e.g., the follow affordances 538a, 538b, and 538c shown in FIG. 5I) on the display. Each respective relationship affordance, when activated, triggers establishment of a predetermined relationship with a user corresponding to the affordance. Displaying the other users that do not have the predetermined relationship with the first user represents providing the first user with the option to establish the predetermined relationship with the other users and access the music shared by the other users (e.g., receive a music recommendation that includes the music shared by the other users), thereby reducing the need for a sequence of user inputs corresponding to manually requesting the music of the other users. Displaying representations of other users enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requesting music from other users), and in addition, it enables users to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device displays (926) on the display a plurality of representations of other users that do not have a predetermined relationship with the first user. Selecting representations of other users for inclusion in the plurality of representations of other users based on a comparison of the music preferences of the first user to the music preferences of a plurality of candidate users other than the first user. For example, in fig. 5V, the device 100 displays a representation 576c of contacts that have a similar musical taste 578 to the first user. The device displays a first subset (less than all) of the candidate users included in the plurality of representations of users based on their similarity of music preferences to the music preferences of the first user (e.g., representation 576c in fig. 5V represents a subset of representation 576a shown in fig. 5T). The device displays a second subset (less than all) of the candidate users excluded from the plurality of representations of users based on similarity of their music preferences to the music preferences of the first user. The music preferences of the users in the first subset of candidate users are closer to the music preferences of the first user than the users in the second set of candidate users. Displaying representations of other users having music preferences similar to the music preferences of the first user allows the first user to connect with other users having similar music preferences. Displaying representations of other users having similar music preferences as the first user enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requests to view user profiles of the other users to discern their music preferences), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device displays (928) on the display a plurality of representations of other users that do not have a predetermined relationship with the first user. Displaying the representations of the other users includes arranging (e.g., sorting) the representations of the other users based on a degree of similarity between the music preferences of the first user and the music preferences of the other users that do not have a predetermined relationship with the first user. For example, in fig. 5V, representations 576c of other users are ordered based on their similar music tastes 578. Ranking the representations of the other users based on a similarity between the music preferences of the other users and the music preferences of the first user allows the first user to connect with other users having similar music preferences.

In some embodiments, the device displays (930) on the display a plurality of representations of other users that do not have a predetermined relationship with the first user. Displaying representations of the other users includes simultaneously displaying a graphical indication of music preferences of a first one of the other users along with information identifying the first user and a graphical indication of music preferences of a second one of the other users along with information identifying the second user. For example, in fig. 5V, similar music taste 578 is a graphical indication of the music preferences of other users. In some embodiments, the graphical indication of the music preference of the respective user indicates artists to which the respective user listens frequently. In some embodiments, the graphical indication of the music preference of the respective user indicates a genre of music that the respective user frequently listens to. In some embodiments, the graphical indication of the music preferences of the respective user includes representations of content items, artists, and genres that the respective user frequently listens to and the first user also frequently listens to (e.g., an indication of shared music tastes between the first user and the respective user). Displaying graphical indications of the music preferences of other users provides the first user with more information to decide whether the first user wants to establish a predetermined relationship with the other users, thereby providing a better user experience. Indicating music preferences enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to view user profiles of other users in order to discern their music preferences), and in addition, it enables users to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device displays (932) on the display a plurality of representations of other users that do not have a predetermined relationship with the first user. Displaying representations of other users includes selecting the other users based on the geographic location of the first user (e.g., the other users are within a predefined location relative to the first user, such as within the same country/region, the same city, the same state, or within 1 mile, 20 feet, or some other predefined distance) and one or more of the social networks associated with the device (e.g., if the other users are connected to the first user via a social network application installed on the device and/or a social network associated with the device). For example, in fig. 5U, the device 100 displays a representation 576b for other users that are near the device 100 (e.g., other users are within a predefined location relative to the device 100, such as within the same country/region, the same city, the same state, or within 1 mile, 20 feet, or some other predefined distance). Displaying their representations based on the locations of other users allows the first user to connect with other users in the vicinity.

Referring to fig. 9D, in some embodiments, during enrollment, the device provides (934) an affordance to the first user to control settings for requiring approval from the first user before allowing the user to establish the predetermined relationship with the first user. For example, in fig. 5M, when private profile affordance 548 is in the ON position, approval from the first user is required before allowing other users to follow the first user. After registration, in response to receiving a request from a respective other user to establish a predetermined relationship with the first user: in accordance with a determination that the setting is in a first state in which approval by the first user is required to establish the predetermined relationship, the device displays (934) a notification that the respective other user has requested establishment of the predetermined relationship with the first user. For example, if private profile affordance 548 is in an ON position, device 100 displays follow request notification 556 indicating that another user has requested to follow the first user. In some embodiments, the notification includes an acceptance or rejection of one or more options for establishing the predetermined relationship with the first user (e.g., an acceptance affordance 560c and a rejection affordance 560a, shown in fig. 5P).

In some embodiments, the notification includes a name of the user who is attempting to follow the first user. In some embodiments, the notification includes an option to view the user profile of the user who is attempting to follow the first user (e.g., view profile affordance 560b shown in fig. 5P). After registration, in response to receiving a request from a respective other user to establish a predetermined relationship with the first user: in accordance with a determination that the setting is in a second state in which approval by the first user is not required to establish the predetermined relationship, the device establishes the predetermined relationship with the first user. In some embodiments, the predetermined relationship is established without displaying a notification that the respective other user has requested establishment of the predetermined relationship with the first user. For example, if the private profile affordance 548 (shown in fig. 5M) is in the OFF position, the device 100 establishes the predetermined relationship without displaying the follow-up request notification 556 (shown in fig. 5O). In some embodiments, the predetermined relationship is established in conjunction with displaying a notification that the respective other user has requested that the predetermined relationship be established with the first user. The settings for requiring approval give the first user more control over which other users have access to the music shared by the first user, thereby improving the controllability of the device and providing a better user experience.

In some implementations, the device receives (936), via the one or more input devices, a request to establish a verified account for the first user. In some embodiments, the verified account indicates that the first user is a verified artist. In some embodiments, the verified account indicates that the first user is a verified celebrity. For example, in FIG. 5Q, the profile creation screen 508 provides the user with the option of requesting an authenticated account. For example, the profile creation screen 508 includes an authentication request affordance 562 that a user may select to indicate a request for an authenticated account. The device transmits the request to a verification entity, which determines whether the request satisfies a verification criterion. In some embodiments, the verification criteria includes being artist. In some embodiments, the verification criteria includes having a threshold number of followers. Providing the option of establishing an authenticated account allows the first user to create a user profile indicating a higher level of authenticity. Providing the option of requesting an authenticated account enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to submitting a request to establish an authenticated account), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device displays (938) a link on the display for music created by the first user. In some embodiments, the first user is an artist and the link is to a most recent album of the artist. For example, in fig. 5R, the device 100a associated with the second user displays the user profile 564 for the first user. The user profile 564 displays a representation 568 of music (e.g., a music album) created by the first user.

In some embodiments, in accordance with a determination that the first user has not completed the registration, the device displays (940) a notification on the display that the music sharing is registered. For example, in fig. 5L, the device 100 displays a notification 546 that prompts the user to register for music sharing. In the example of fig. 5L, the notification 546 includes a banner displayed toward the top of the touch-sensitive display. Displaying the reminder notification provides the user with an option to register for the music share even if the user previously ignored or forgotten to register for the music share. Alerting the user to register for music sharing enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to a request to register for music sharing), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 9E, in some embodiments, prior to displaying the enrollment user interface, the device determines (942) whether the first user is subscribed to a subscription-based music streaming service. In response to determining that the first user is subscribed to the subscription-based music streaming service, the device displays (942) a registered user interface, and in response to determining that the first user is not subscribed to the subscription-based music streaming service, the device forgoes (942) display of the registered user interface. In some embodiments, subscribing to a subscription-based music streaming service provides users with the option of registering for music sharing.

In some embodiments, prior to displaying the enrollment user interface, the enrollment user interface includes (944) a third affordance (e.g., a third toggle switch that controls privacy settings for all playlists) that, when activated, changes a default value of the privacy settings for the plurality of playlists. For example, in FIG. 5G, device 100 displays privacy affordance 526d that allows the user to control privacy settings for all playlists. The third affordance allows the user to change the privacy settings for all playlists, thereby reducing the need to change the sequence of user inputs corresponding to changing the privacy settings for each playlist.

In some embodiments, the representations of the plurality of playlists are scrollable (946). In some embodiments, a default value of the privacy settings for the plurality of playlists indicates that the plurality of playlists are private (948). For example, in FIG. 5E, by default, the privacy affordances 526a, 526b, and 526c are in the OFF position, indicating that the default values of the privacy settings are private. In some embodiments, the one or more user inputs change the privacy settings for the first playlist from private to public and, in response to the privacy settings for the first playlist changing from private to public, provide other users access to the first playlist (950). For example, in fig. 5E, device 100 receives user input 528 to change the "Work" playlist from private to public.

Referring to fig. 9F, in some embodiments, the first affordance includes a first toggle switch (952) displayed adjacent to the representation of the first playlist. The first toggle switch is in one of a first state indicating that the first playlist is private and a second state indicating that the first playlist is public. In some implementations, the first toggle switch is in a first state (e.g., a private position) by default. For example, in FIG. 5E, the privacy affordance 526a is a toggle switch displayed adjacent to the representation 524a for the "Work" playlist. Further, the privacy affordance 526a has an OFF position indicating that the "Work" playlist is private and an ON position indicating that the "Work" playlist is public.

It should be understood that the particular order in which the operations in fig. 9A-9F are described is merely exemplary and is not intended to suggest that the order described is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g., methods 1000, 1100, and 1200) also apply in a similar manner to method 900 described above in connection with fig. 9A-9F. For example, the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described above with reference to method 900 optionally have one or more features of the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described herein with reference to other methods described herein (e.g., methods 1000, 1100, and 1200). For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus, such as a general-purpose processor (e.g., as described above with respect to fig. 1A and 3) or an application-specific chip. Further, the operations described above with reference to fig. 9A-9D are optionally implemented by components depicted in fig. 1A-1B or fig. 3. For example, receiving operation 902 and receiving operation 910 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112 and event dispatcher module 174 communicates the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186 and determines whether a first contact at a first location on the touch-sensitive surface (or whether rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface or rotation of the device from one orientation to another. When a respective predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handlers 190 access respective GUI updaters 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

Fig. 10A-10E illustrate a flow chart of a method 1000 of providing notifications and splice marks for music. Method 1000 is performed in an electronic device (e.g., device 100 in fig. 1A or device 300 in fig. 3) having one or more processors, non-transitory memory, a display, and one or more input devices. In some embodiments, the display is a touch screen display and the one or more input devices are located on or integrated with the display. In some embodiments, the display is separate from the one or more input devices. Some operations in method 1000 are optionally combined, and/or the order of some operations is optionally changed.

As described below, the method 1000 provides a way to notify and/or provide splice marks for music. Referring to fig. 10A, the device displays (1002) a media browsing user interface for a first user (e.g., for a user logged into a music application and/or device) on a display. For example, in fig. 6B, device 100 displays media browsing user interface 602.

While displaying the media browsing user interface, the device receives (1004) input corresponding to a request to display a different view of the media browsing user interface (e.g., a search input, a request to display a representation of a user's recommended playlist, album, artist, and/or a request to display a predetermined set of playlists, albums, or artists) via the one or more input devices. For example, in fig. 6A, device 100 receives user input 604 corresponding to a request to display a user's playlist. In response to the input, the device simultaneously displays (1004) multiple representations of containers of media items within the media browsing user interface. The plurality of representations includes a representation of a first media container (e.g., a first playlist/album/song/station broadcast station) and a representation of a second media container (e.g., a second playlist/album/song/station broadcast station). In some embodiments, a media container is a collection of one or more media items (e.g., songs, playlists, radio stations, or albums) that have been grouped together in a user interface and represented by a shared graphical representation. For example, in fig. 6B, device 100 displays word Playlist representation 606a representing "Work Playlist", studio Playlist representation 606B representing "studio Playlist", and word kout Playlist representation 606c representing "Work kout Playlist".

In accordance with a determination that the first media container satisfies engagement criteria for the first user, wherein the engagement criteria for the respective media container include criteria that the first user has engaged (e.g., within a predetermined time threshold) with media in the respective media container by other users with which the first user has a predetermined relationship (e.g., users that the first user follows or is a "friend") the device displays (1006) an engagement indicia of a representation (e.g., proximate to, overlaid on, or otherwise visually associated with) the first media container to indicate that the first user has engaged with one or more media items in the first media container by users with which the first user has a predetermined relationship. In some embodiments, the engagement indicia indicates which user is engaged with the container (e.g., the engagement indicia includes a picture of another user). For example, in FIG. 6B, the device 100 displays a splice mark 608a for "Work Playlist". In the example of FIG. 6B, the splice mark 608a includes a badge 610a that represents the first other user that is being spliced with "Work Playlist". Displaying engagement indicia for a representation of a media container provides an intuitive and user-friendly experience to obtain information about other users' engagement with the media container. Displaying engagement indicia for the media container enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display representations of media containers that other users are engaging), and in addition, it enables users to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In accordance with a determination that the first media container does not satisfy the engagement criteria for the first user, a representation of the first media container is displayed (1008) without displaying an engagement label for the representation of the first media container (e.g., forgoing displaying the engagement label for the representation of the first media container). For example, in fig. 6B, device 100 displays studio Playlist representation 606B and workkoutplaylist representation 606c without displaying a splice mark, e.g., because "studio Playlist" and "workkout Playlist" do not satisfy the splice criteria for the first user (e.g., the first user does not splice with "studio Playlist" and "workkout Playlist" other users with which the first user has a predetermined relationship). Displaying the representation of the media container without displaying the engagement indicia indicates that the first user has a predetermined relationship with other users not engaged with the media container.

In accordance with a determination that the second media container satisfies engagement criteria for the first user, the device displays (1010) an engagement indicium of a representation for the second media container (e.g., proximate to, overlaid on, or otherwise visually associated therewith) to indicate that the user with which the first user has a predetermined relationship has engaged one or more media items in the second media container. In some embodiments, the engagement indicia indicates which user is engaged with the container (e.g., the engagement indicia includes a picture of another user). In accordance with a determination that the second media container does not satisfy the engagement criteria for the first user, a representation of the second media container is displayed without displaying an engagement marking for the representation of the second media container (e.g., forgoing displaying the engagement marking for the representation of the second media container). For example, in FIG. 6D, device 100 displays engagement indicia 608c for the workout playlist representation 606 c. The engagement tag 608c includes a second badge 610b representing a second other user. Displaying engagement indicia associated with the media containers serves as an intuitive and user-friendly way to indicate which media containers meet the engagement criteria. Including badges of different users in the engagement tag for the media container enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display representations of other users being engaged with the media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending battery life of the device.

Referring to fig. 10B, in some embodiments, the device displays (1012) a recommendation page (e.g., a "personal-specific page") within the media browsing user interface that includes recommendations (including sets of recommended content) for the first user. The plurality of sets of recommended content includes a first set of recommended content selected based on engagement of users having a predefined relationship with the first user. The first set of recommended content includes only containers of media items from among the containers of the plurality of media items that satisfy the engagement criteria (e.g., the first set of recommended content does not include media items that do not satisfy the engagement criteria). For example, in FIG. 6M, device 100 displays a media recommendation screen 640 that includes a social recommendation portion 642 that recommends a media container that meets engagement criteria for the user of device 100. The sets of recommended content include a second set of recommended content selected based on criteria other than engagement by a user having a predefined relationship with the first user (e.g., the first user's taste profile, the first user's recently played media, the recently published content matching the first user's taste profile), including at least one media container that does not meet the engagement criteria. In some embodiments, the second set of recommended content does not include a container for any media items that meet the engagement criteria. For example, in FIG. 6N, the orchestrated recommendations section 650 includes recommendations for media containers that do not meet the engagement criteria. Displaying the first set of recommended content allows the user to seek music that other users are engaging, and displaying the second set of recommended content allows the user to seek music that other users may be engaging, thereby providing a variety of different music recommendations. Displaying the first set of recommended content enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display representations of media containers that other users are engaging), and in addition, it enables users to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some implementations, the containers of the media items in the first set of content are ordered (1014) based on one or more of a degree of engagement (e.g., frequency of interaction) and a recency of engagement (e.g., recency of interaction). For example, in FIG. 6M, the representations 644a, 644b, and 644c are sorted based on the number of badges that their respective engagement markers 646a, 646b, and 646c include, respectively. Ranking media containers based on engagement degrees allows a user to easily view the media containers associated with the highest engagement degree.

In some embodiments, the device displays (1016), within the media browsing user interface, a recommendation page (e.g., a "personal-specific page") that includes recommendations for the first user, and displays (1016), within the recommendation page, a set of content that includes a container of media items that have been explicitly shared with the first user (e.g., via information and/or directly through a music application). Displaying the media container that has been explicitly shared with the first user provides the first user with the option to engage with the explicitly shared media container.

In some embodiments, concurrently displaying the plurality of representations of containers of media items includes (1018) displaying a first set of the plurality of representations with respective splice marks and displaying a second set of the plurality of representations without respective splice marks. In some embodiments, the first group includes containers of two or more media items that satisfy the engagement criteria for the first user. In some embodiments, the second group includes containers of two or more media items that do not meet the engagement criteria for the first user. In some embodiments, the library displays the plurality of representations. Some of these representations have join marks while others do not, for example, as shown in fig. 6C-6D, which enables a user to quickly browse through media items or media containers or suggested media items or media containers in the user's media library to identify media items or containers being joined by other users that the first user is following.

In some embodiments, the device receives (1020) a follow-up request from a second user that is not in a predetermined relationship with the first user and displays (1020) a notification on the display indicating the follow-up request (e.g., follow-up request notification 556 shown in fig. 5O). While displaying the notification, the device detects (1020), via the one or more input devices, one or more user inputs (e.g., a hard press, swipe, or tap on the notification) corresponding to the request to display the expanded version of the notification. In response to receiving the one or more user inputs corresponding to the request to display the expanded version of the notification, the device displays (1020) the expanded version of the notification (e.g., expanded version 560 shown in fig. 5P). The expanded version of the notification includes: a first affordance (e.g., an accept button, such as accept affordance 560c) that, when activated, accepts a follow-up request; a second affordance (e.g., a decline button, such as decline affordance 560a) that, when activated, declines to follow the request; and a third affordance (e.g., a view profile button, such as view profile affordance 560b) that, when activated, displays a user profile for the second user. In some embodiments, the expanded version of the notification includes one button selected from an accept button, a decline button, and a view profile button. In some embodiments, the expanded version of the notification includes two buttons selected from an accept button, a decline button, and a view profile button. The display notification provides a visual indication to the first user that another user has requested to establish a predetermined relationship with the first user. Displaying the expanded version of the notification provides the first user with an option to accept or decline the request.

Referring to fig. 10C, in some embodiments, the device displays (1022) a notification (e.g., a banner notification, such as similar to follow request notification 556 shown in fig. 5O) on the display indicating that at least one of the other users has engaged (e.g., has liked/loved/added to the library/downloaded/shared) with one or more of the containers of the plurality of media items.

In some embodiments, the engagement indicia for the representation of the first media container indicates (1024) a type of engagement that at least one of the other users has with the container of the first media item. For example, in FIG. 6G, the device 100 displays a splice type indicator 620c indicating that "Breda" likes "Work Playlist". As another example, in fig. 6H, the device 100 displays a splice type indicator 620b indicating "Eric" love "Work Playlist". In accordance with a determination that the type of engagement is a first type of engagement (e.g., like, love, download, listen), the engagement indicia includes a first symbol indicating a first score (e.g., if the other user likes the media item, the engagement indicia includes a like symbol). Indicating the type of engagement provides the first user with additional information about the engagement of other users. Indicating the type of engagement enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to view the type of engagement), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, in accordance with a determination that the type of engagement is a first type of engagement (e.g., like, love, download, listen), the engagement indicia includes (1026) a first symbol indicating a first score (e.g., if the other user likes the media item, the engagement indicia includes a like symbol). For example, in FIG. 6G, the splice type indicator 620c includes a like symbol indicating that "Brenda" likes "Work Playlist". In accordance with a determination that the type of engagement is a second type of engagement (e.g., like, love, download, listen) that is different from the first type of engagement, the engagement indicia includes (1026) a second symbol that is different from the first symbol (e.g., if the other user loves the media item, the engagement indicia includes a hearts symbol). For example, in fig. 6H, the splice type indicator 620b includes a heart symbol indicating "Eric" love "Work Playlist". Using different symbols to indicate different types of engagement provides an intuitive and user-friendly way to indicate the type of engagement. Indicating the type of engagement enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to view the type of engagement), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the third score is assigned to the first media container in accordance with a determination that the type of engagement includes at least one of the other users, the engagement flag does not include (1028) a third symbol indicating the third score because the third score is less than the first score (e.g., if the other user dislikes the media item, the engagement flag does not indicate that the other user dislikes the media item).

In some embodiments, the device determines (1030) whether other users (e.g., friends of the first user, such as a user connected to the first user via a music recommendation network) have engaged with one or more of the first media container and the second media container (e.g., have listened to/liked/loved/added to their playlists). In some implementations, the device receives an indication that a second device corresponding to another user played media items from one or more of the first media container and the second media container.

In some embodiments, the engagement criteria for determining that the respective other user has engaged the respective media container includes (1032) a criterion that is met when the device receives that the second device has played the respective media container more than a threshold amount, indicating that the respective other user has listened to (e.g., repeatedly listened to) the respective media container more than a threshold amount (e.g., a threshold number of times, a threshold duration, a threshold number of times within a predetermined amount of time). For example, in FIG. 6B, a first badge 610a within the splice mark 608a indicates that a first other user represented by the first badge 610a has listened to "Work Playlist". In some embodiments, the engagement criteria include a criterion that is met when the device receives an indication that a second device associated with a respective other user has explicitly indicated a preference for a respective media container (e.g., marking the media container or media items within the respective media container as liked or liked, or assigning a score/rating greater than a threshold score to the respective media container or media items within the respective media container). For example, in FIG. 6G, the splice type indicator 620c indicates that "Breda" has explicitly indicated a preference for "Work Playlist" (e.g., "Breda" likes "Work Playlist"). In some embodiments, the engagement criteria include a criterion that is met when the device receives an indication that a second device associated with a respective other user has received input corresponding to a request to add a respective media container or a media item from a respective media container to the media library. In some embodiments, the engagement criteria include a criterion that is met when the device receives an indication that a second device associated with a respective other user has received input corresponding to a request to add a respective media container or a media item from a respective media container to the playlist. In some embodiments, the engagement criteria include criteria that are met when the device receives an indication that a second device associated with a respective other user has downloaded a respective media container or a media item from a respective media container. Including different criteria in the engagement criteria allows the device 100 to indicate different types of engagement. Indicating different types of engagement enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to view the type of engagement), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 10D, in some embodiments, the engagement criteria for determining that the respective other user has engaged the respective media container include (1034) a criterion that is met when a number of interactions by the other user with the respective media container meets a threshold amount of interactions (e.g., a number of interactions or a frequency of interactions with the respective media container). In some embodiments, the number of interactions includes interactions of the same type (e.g., listening only). In some embodiments, the number of interactions includes different types of interactions (e.g., listening, downloading, favorites). In some embodiments, the respective other user is not identified as having engaged with the respective media container if the respective other user has had less than a threshold amount of interaction with the respective media container.

In some embodiments, in accordance with a determination that the engagement criteria include explicit criteria (e.g., like/love/add to library/explicitly share), the device determines (1036) whether the number of interactions is greater than a first threshold (e.g., one interaction). In accordance with a determination that the engagement criteria include implicit criteria (e.g., listening), the device determines (1036) whether the number of interactions is greater than a second threshold, wherein the second threshold is greater than the first threshold (e.g., five or more interactions).

In some embodiments, the device displays (1038) a badge that instructs other users to engage with the one or more media items in the first media container. In some implementations, the badge does not indicate which particular users are engaged with the media container. For example, in FIG. 6I, the device 100 displays a generic badge 610x representing a group of other users who are engaged with "Work Playlist". The device detects (1038) user input on the badge via the one or more input devices and, in response to detecting the user input on the badge, displays (1038) selectable affordances corresponding to other users engaged with the one or more media items in the first media container, each selectable affordance corresponding to a respective one of the other users. For example, in fig. 6L, device 100 detects user input 632 and displays a list 636 of users who are joining "Work Playlist". Displaying affordances corresponding to other users that are engaging the media container allows the first user to see which other users are engaging the media container. Displaying affordances corresponding to other users engaging the media container enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to see which other users are engaging the media container), and in addition, it enables users to use the device faster and more efficiently, thereby reducing power consumption and extending battery life of the device.

In some embodiments, the device displays (1040), via the one or more input devices, a user input that activates one of the selectable affordances, and in response to detecting the user input that activates the one of the selectable affordances, displays (1040) a user profile for a respective one of the other users engaged with the one or more media items in the first media container. In some embodiments, the user profile displays a media container (e.g., a playlist) of a respective one of the other users. In some embodiments, the user profile displays a representation of a user having a predetermined relationship with a respective one of the other users (e.g., a person who is following the respective one of the other users and/or a person who is being followed by the respective one of the other users). Thus, displaying the selectable affordances of other users allows the first user to view a user profile for the other users who are engaging music shared by the first user. Displaying the selectable affordances of other users enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to view user profiles for other users engaged with media shared by the first user), and in addition, it enables users to use the device faster and more efficiently, thereby reducing power consumption and extending battery life of the device.

Referring to fig. 10E, in some embodiments, the device displays (1042) a first badge indicating a first user of the other users engaged with the one or more media items in the first media container. In some embodiments, the first badge includes (1044) a picture (e.g., a profile picture) of a first user of the other users engaged with the one or more media items in the first media container. For example, in FIG. 6B, the first badge 610a includes a picture representing the first other user who is joining "Work Playlist". Displaying pictures representing other users makes it easier for the first user to identify other users who are engaging the music being shared by the first user. Displaying pictures representing other users enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to requests to display pictures representing other users), and in addition, it enables users to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device displays (1046) at least a portion of a second badge indicating a second user of the other users engaged with the one or more media items in the first media container. The second badge includes a picture of a second user of the other users. In some embodiments, the device displays (1048) at least a portion of a third badge that indicates a third user of the other users that engaged the one or more media items in the first media container, wherein the third badge includes a picture of the third user of the other users. In some embodiments, the number of badges displayed (1050) is less than a threshold number of badges (e.g., less than four badges). For example, in fig. 6E-6F, the device 100 displays three badges in the "Work Playlist" representation 606a, even if there are four users engaged with the "Work Playlist". Limiting the number of badges avoids cluttering the user interface and improves the legibility of the limited number of badges displayed.

In some embodiments, the device detects (1052) a user input on one of the first, second, and third badges and, after detecting the user input, displays (1052) a list of other users engaged with the first media container. For example, in fig. 6L, device 100 detects user input 632.

In some embodiments, the device determines (1054) whether the other user engaged with the first media container within a predetermined time period (e.g., within the last 7 days). In accordance with a determination that the other user has engaged with the first media container within the predetermined time period, the device determines (1054) that the first media container satisfies engagement criteria for the first user. In accordance with a determination that the other user has not engaged with the first media container within the predetermined time period (e.g., the other user has engaged with the first media container before the predetermined time period), the device determines (1054) that the first media container does not satisfy the engagement criteria for the first user. In some embodiments, the engagement criteria take into account the stage of interaction with the media item based on other rules. For example, recent interactions with a media item are optionally weighted more heavily than earlier interactions with the media item, such that interactions with older media items contribute less to a determination as to whether the media item or media container meets the engagement criteria.

It should be understood that the particular order in which the operations in fig. 10A-10E are described is merely exemplary and is not intended to suggest that the order described is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g., methods 900, 1100, and 1200) also apply in a similar manner to method 1000 described above in connection with fig. 10A-10E. For example, the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described above with reference to method 1000 optionally have one or more features of the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described herein with reference to other methods (e.g., methods 900, 1100, and 1200) described herein. For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus, such as a general-purpose processor (e.g., as described above with respect to fig. 1A and 3) or an application-specific chip. Further, the operations described above with reference to fig. 10A-10E are optionally implemented by the components depicted in fig. 1A-1B or fig. 3. For example, receiving operation 1004 is optionally implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112 and event dispatcher module 174 communicates the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186 and determines whether a first contact at a first location on the touch-sensitive surface (or whether rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface or rotation of the device from one orientation to another. When a respective predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handlers 190 access respective GUI updaters 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

11A-11D illustrate a flow diagram of a method 1100 of displaying a representation of a media container marked as recently played by a user (e.g., by a user account associated with a device). Method 1100 is performed in an electronic device (e.g., device 100 in fig. 1A or device 300 in fig. 3) having one or more processors, non-transitory memory, a display, and one or more input devices. In some embodiments, the display is a touch screen display and the one or more input devices are located on or integrated with the display. In some embodiments, the display is separate from the one or more input devices. Some operations in method 1100 are optionally combined, and/or the order of some operations is optionally changed.

Referring to fig. 11A, the device displays (1102) a media browsing user interface for a media application (e.g., media browsing user interface 702 shown in fig. 7A) on the display. While displaying the media browsing user interface, the device receives (1102), via the one or more input devices, a request to display a recently played media container (e.g., a recently played playlist, a recently played album, a recently played radio station, and/or a recently played media item). For example, in FIG. 7A, device 100 receives user input 706 at a location corresponding to affordance 704 b. In response to receiving a request to display a recently played media container, the device displays (1102) a plurality of representations of media containers marked as recently played by a user (e.g., played by a user account associated with the device). For example, in fig. 7B, device 100 displays a recently played portion 710 that includes representations 712 and 712a for two media containers that have recently been played by a user of device 100 (e.g., played by a user account associated with device 100). The plurality of representations of media containers includes a first media container generated based on verbal instructions (e.g., verbal utterances recorded and interpreted by a virtual assistant) requesting playback of media that matches a portion of the verbal instructions. In some embodiments, receiving the verbal instructions occurs prior to displaying the media browsing user interface (e.g., receiving the verbal instructions while displaying the home screen and/or receiving the verbal instructions while displaying a user interface generated by another application, such as a browser application). For example, in fig. 7B, the representation 712a for "album DEF" includes a verbal indicator 714 that instructs the device 100 to play "album DEF" in response to receiving verbal instructions 720 a. Displaying a representation for a media container played in response to verbal instructions allows a user to play the media container at a later time without speaking the same verbal instructions again, thereby improving the efficiency of the device and providing a better user experience. Displaying representations of media containers played in response to verbal instructions enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for subsequent verbal instructions identical to previous verbal instructions), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some implementations, the first media container includes (1104) a representation of verbal instructions for generating the first media container. In some embodiments, the representation of the verbal instructions comprises at least a portion of the verbal instructions. For example, in FIG. 7D, the representation 712a includes at least a portion 721a of the verbal instructions 720 a. The representation including verbal instructions helps the user remember which verbal instructions cause the device 100 to play the media container.

In some embodiments, the first media container includes (1106) media items selected according to a media taste profile of the user. For example, in fig. 7M-7N, the device 100 plays media items that satisfy the user's media taste profile in response to receiving verbal instructions 720 e. Playing music that meets the user's media taste profile reduces the need for user input sequences corresponding to manually selecting user preferred media items, thereby improving the efficiency of the device and providing a better user experience. Playing a media container according to a user's media taste profile enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to manually selecting media items that meet the user taste), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the first media container includes (1108) media items that other users are engaging (e.g., listening, liking/favoring, downloading, and/or explicitly sharing). In some embodiments, the other user has a predetermined relationship with the user (e.g., the other user is connected to the user). For example, in fig. 7O-7P, the device receives verbal instructions 720f corresponding to a request to play music that the other user is engaging (e.g., "play my friend's music"). Playing music that other users are engaging reduces the need for a user input sequence corresponding to manually selecting music that other users are engaging, thereby improving the efficiency of the device and providing a better user experience. Playing the media item that the other user is engaging enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requesting the media item that the other user is engaging from the other user), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In some implementations, the device receives (1110), via the one or more input devices, user input on the representation of the first media container (e.g., receives a hard press or a long press). For example, in fig. 7Q, device 100 receives user input 740 on representation 712 f. In response to receiving user input on the representation of the first media container, the device displays (1110) affordances for other users that affect the first media container by engaging with the media item. For example, in fig. 7R, device 100 displays an overlay interface 742 that includes representations 744 (e.g., affordances, such as selectable affordances) for other users. The device receives (1110), via the one or more input devices, user input on one of the affordances corresponding to one of the other users, and removes (1110), from the first media container, the media item engaged by the one of the other users in response to receiving the user input on the one of the affordances. The device 100 provides the user with the option of removing a particular user from a group of users that affect the content of the media container.

Referring to fig. 11B, in some embodiments, a device displays (1112) one or more representations of a custom media container (e.g., a custom playlist and/or a custom station broadcaster) and displays (1112) one or more representations of a pre-existing media container (e.g., a pre-existing playlist and/or a pre-existing station broadcaster). In some embodiments, the one or more representations of the custom media container include (1114) one or more icons for the custom media container, the one or more representations of the pre-existing media container include (1114) one or more icons for the pre-existing media container, and the one or more icons for the custom media container have (1114) a different appearance than the one or more icons for the pre-existing media container (e.g., the icons for the custom container have an obscured boundary). For example, in FIG. 7F, device 100 displays a custom container indication 713 associated with representation 712b for a custom "Hip-Hop" playlist. Changing the appearance of the representation for the custom media container helps the user distinguish the custom media container from the pre-existing media container. Providing different appearances for representations of custom media containers and representations of pre-existing media containers enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for subsequent user input to be made on one of the representations to discover whether the corresponding media container is a custom media container or a pre-existing media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, a first media container is generated based on verbal instructions received at the device (1116). In some embodiments, the first media container is generated based on verbal instructions received at a different device associated with the user (1118). In some embodiments, the other device is a device that does not have a display or has limited display capabilities, such as a stand-alone speaker that is able to access the user's music library.

Referring to fig. 11C, in some embodiments, the device receives (1120), at the device, verbal instructions for playing the media item. In response to receiving the verbal instruction to play the media item, the device selects (1120) one of a plurality of pre-existing media containers as a first container in accordance with a determination that the verbal instruction matches the one of the plurality of pre-existing media containers. For example, in fig. 7C-7D, the device 100 plays an "album DEF," which is a pre-existing media container. In accordance with a determination that the verbal instructions do not match one of the plurality of pre-existing media containers, the device composites (1120) the custom media container as a first container. For example, in fig. 7E through 7F, the device 100 plays a customized "Hip-Hop" playlist, which is a customized media container. In some embodiments, the device determines whether the verbal instructions match one of a plurality of pre-existing media containers. For example, the device determines whether the verbal instructions include a portion of text corresponding to a pre-existing media container. In some embodiments, synthesizing the custom media container includes splicing (1122) two or more media containers associated with an artist in an editorial identity (e.g., having two playlists of songs from the artist and optionally other media items associated with the artist, e.g., a playlist organized in an editorial identity followed by "all songs") and media items in a user's library. For example, in FIG. 7H, the custom "Hip-Hop" playlist is a concatenation of playlists 736a and 736b that are carefully organized in editorial identity. The composite custom media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to manually creating custom media containers), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device receives (1124), at the device, verbal instructions for playing the media item. In response to receiving verbal instructions for playing the media item, in accordance with a determination that the verbal instructions include the predefined keyword, the first media container includes (1124) media items that match a portion of the verbal instructions and related media items that do not match a portion of the verbal instructions. In accordance with a determination that the verbal instructions do not include the predefined keywords, the first media container includes (1124) only media items that match a portion of the verbal instructions. In some embodiments, the device determines whether the verbal instructions include predefined keywords (e.g., determines whether the verbal instructions include the word "station"). In some embodiments, when the verbal instructions include predefined keywords, the first media container further includes media items that match a portion of the verbal instructions and media items related to the media items. For example, in fig. 7K-7L, the device 100 receives verbal instructions 720d that include predefined keywords 728, and the device 100 plays a media container that includes media items that match the verbal instructions 720d (e.g., songs from artists called "applets the ripper") and related media items that do not match the verbal instructions 720d (e.g., songs from other artists that are similar songs from "applets the ripper"). Detecting predefined keywords in the verbal instructions causes the device to play related media items other than the requested media item, thereby allowing the user to discover related music. Playing related media items in addition to those created by a particular artist enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to effectuating playback of the related media items), and in addition, it enables a user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 11D, in some embodiments, the first media container is updated periodically (1126) (e.g., weekly/daily/monthly). Updating the media container allows the user to engage with relevant music (e.g., music that other users are engaging).

In some embodiments, the device determines (1128) whether the media item not currently in the first media container satisfies a join criterion. The engagement criteria for the respective media container include criteria that the first user has a predetermined relationship with other users with whom (e.g., users that the first user follows or is a "friend" of) have engaged (e.g., within a predetermined time threshold) with the media in the respective media container. In accordance with a determination that the media item satisfies the engagement criteria, the device includes (1128) the media item in a first media container. In some embodiments, the engagement criteria include an engagement threshold (e.g., an engagement frequency threshold and/or an engagement nearness threshold). In some embodiments, the media item satisfies the engagement criteria if the amount of engagement with the media item is greater than an engagement threshold. Including media items in the media container based on engagement of other users with the media items allows the user to listen to the media items that the other users are currently engaging.

In some implementations, the device determines (1130) whether the media items currently in the first media container satisfy engagement criteria, where the engagement criteria for the respective media container include criteria that the first user has a predetermined relationship with other users (e.g., users that the first user follows or is a "friend" of) that have engaged (e.g., within a predetermined time threshold) with the media in the respective media container. In accordance with a determination that the media item does not meet the engagement criteria, the device removes (1130) the media item from the first media container. In some embodiments, the engagement criteria include an engagement threshold (e.g., an engagement frequency threshold and/or an engagement nearness threshold). In some embodiments, the media item does not meet the engagement criteria if the amount of engagement with the media item is less than the engagement threshold. Removing media items from the media container based on the lack of engagement of other users with the media items allows the user to listen to the media items that the other users are currently engaging.

It should be understood that the particular order in which the operations in fig. 11A-11D are described is merely exemplary and is not intended to suggest that the order described is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g., methods 900, 1000, and 1200) also apply in a similar manner to method 1100 described above in connection with fig. 11A-11D. For example, the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described above with reference to method 1100 optionally have one or more features of the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described herein with reference to other methods described herein (e.g., methods 900, 1000, and 1200). For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus, such as a general-purpose processor (e.g., as described above with respect to fig. 1A and 3) or an application-specific chip. Further, the operations described above with reference to fig. 11A-11D are optionally implemented by components depicted in fig. 1A-1B or fig. 3. For example, receiving operation 1102 is optionally implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112 and event dispatcher module 174 communicates the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186 and determines whether a first contact at a first location on the touch-sensitive surface (or whether rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface or rotation of the device from one orientation to another. When a respective predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handlers 190 access respective GUI updaters 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

Fig. 12A-12E illustrate a flow diagram of a method 1200 of hiding music from public view. Method 1200 is performed in an electronic device (e.g., device 100 in fig. 1A or device 300 in fig. 3) having one or more processors, non-transitory memory, a display, and one or more input devices. In some embodiments, the display is a touch screen display and the one or more input devices are located on or integrated with the display. In some embodiments, the display is separate from the one or more input devices. Some operations in method 1200 are optionally combined, and/or the order of some operations is optionally changed.

As described below, the method 1200 provides a way for a first user to hide the first user's engagement with a particular media container from other users in a predetermined relationship with the first user. Referring to fig. 12A, the device displays (1202) on the display a media engagement user interface that includes a plurality of representations of containers of media items for which the first user has satisfied engagement criteria. For example, in fig. 8A, the device 100 displays a media engagement user interface 802 that includes representations 812a and 812b for a media container that the first user is listening to. Engagement of the first user with the container of the plurality of media items is visible to other users having a predetermined relationship with the first user (e.g., as engagement indicia in a media browsing user interface as described above or a user profile for the first user as described above). For example, in fig. 8B, the second device 100a displays a public version 804 of the user profile for the first user, the public version including representations 812a and 812B for the media container that the first user is listening to.

The device simultaneously displays a representation (1204) of the first media container and a representation (1206) of the second media container. In some implementations, the container includes a single music item. For example, in fig. 8A, device 100 displays representations 812a and 812b for two media containers. The device detects (1206), via the one or more input devices, a sequence of one or more inputs (e.g., user taps on the first container) corresponding to a request to hide the engagement of the first user with the respective media container. In some implementations, a first portion of a sequence of one or more inputs corresponding to a request to hide engagement of a first user with a respective media container is detected when a representation of the media item container for which the first user has satisfied engagement criteria is displayed on a display. For example, device 100 receives user input 820 (shown in FIG. 8C) corresponding to a request to display menu 822 (shown in FIG. 8D). After displaying the menu 822, the device 100 receives a user input 826 (shown in fig. 8E) corresponding to a request to hide the first user's engagement with the media container (e.g., with the "album FED"). Providing the option of hiding the engagement with the media container provides a higher level of privacy for the first user, thereby improving the user experience. Hiding the engagement of the first user with the media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to requests to delete the media container or stop participating in music sharing to engage the media container without notifying them of engagement with the media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In response to detecting, via the one or more input devices, a sequence of one or more inputs corresponding to a request to hide the engagement of the first user with the respective media container, in accordance with a determination that the sequence of one or more inputs corresponds to the request to hide the engagement of the first user with the first media container, the device changes (1208) an appearance of the representation of the first media container without changing an appearance of the representation of the second media container. For example, in fig. 8E-8F, device 100 changes the appearance of representation 812b after receiving user input 826. In the example of fig. 8F, representation 812b has a dark background 814b (e.g., rather than a light background 814 a). The change to the representation of the first media container indicates that the first user's engagement with the first media container is hidden from view by other users having a predetermined relationship with the first user. In some embodiments, a representation of a first container (e.g., with a changing appearance) is displayed concurrently with a representation of a second container. In some embodiments, hiding the engagement of the first user removes engagement tags for the first user on media items in the media library of other users. In some embodiments, hiding the engagement of the first user removes the media container from the public version of the first user's user profile so that other users cannot see that the first user is engaging the media container. Changing the appearance of the representation makes it easier for the first user to identify which media containers are hidden and which media containers are not hidden, thereby improving the user experience. Indicating that engagement with the media container is hidden relative to other users enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to a request to display whether engagement with the media container is hidden), and in addition, it enables a user to use the device more quickly and efficiently, thereby reducing power consumption and extending battery life of the device.

In accordance with a determination that the sequence of one or more inputs corresponds to a request to hide the engagement of the first user with the second media container, the device changes (1210) an appearance of the representation of the second media container without changing an appearance of the representation of the first media container, wherein the change in appearance of the representation of the second media container indicates that the engagement of the first user with the second media container is hidden from view by other users having a predetermined relationship with the first user. In some embodiments, the representation of the second container (with the altered appearance) is displayed simultaneously with the representation of the first container.

Referring to fig. 12B, in some embodiments, the plurality of representations of containers of media items are displayed (1212) in a user profile portion of a media engagement user interface. For example, in FIG. 8G, the second device 100a displays a public version 804 of the user profile for the first user that includes a representation 812a for "album ABC" but does not include a representation 812b for "album FED" because the first user chooses to hide the first user's engagement with the "album FED".

In some embodiments, the plurality of representations of containers of media items are displayed (1214) in a recommendation module (e.g., in a "personal-specific" portion) of a media-engagement user interface. For example, in FIG. 8Q, the second device 100a displays a recommendation module 850 that includes representations 812b, 812d, and 812e for media containers that other users are engaging.

In some implementations, the plurality of representations of containers of media items are ordered (1216) based on one or more of a joint frequency and a joint recency. For example, in FIG. 8L, the device 100 sorts the representations 812a and 812b based on the first user's closeness of engagement with the corresponding media container. Ordering representations of media containers based on recency makes it easier for a user to access media containers that have been recently played by the user. Determining the display order of the representations for the hidden media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input corresponding to scrolling through the representations to view the representations of the hidden media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the one or more media items in the first media container include (1218) a plurality of media items, and wherein the engagement of the first user with each of the plurality of media items is hidden from view by other users having a predetermined relationship with the first user. Hiding the engagement of the first user with each of the plurality of media items allows the first user to hide the engagement with the media container and reduces the need for a sequence of user inputs corresponding to hiding each of the media items in the media container, thereby improving the efficiency of the device and providing a better user experience. Hiding the engagement of the first user with each of the plurality of media items enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a user input sequence corresponding to the engagement of each of the hidden media items), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the plurality of representations of containers of media items are displayed (1220) in a module of a profile page for the first user (e.g., the listening portion 806 shown in fig. 8G and/or the listening portion 806a shown in fig. 8H). The module indicates the media item that the first user is listening to (e.g., in the "listening" section). In some implementations, the device presents (1222), to at least one of the other users with which the first user has a predetermined relationship, at least one of the containers of the plurality of media items as a media recommendation (e.g., in recommendation module 850 shown in fig. 8Q). In some embodiments, after the engagement of the first user with the first media container is hidden from view by other users having a predetermined relationship with the first user, the device forgoes (1224) presenting the first media container to at least one of the other users with whom the first user has a predetermined relationship as a media recommendation (e.g., in fig. 8R, after the first user hides the engagement of the first user with the "album FED," the second device 100a forgoes display of the representation 812b for the "album FED"). Hiding the engagement with the media container allows the first user to listen to the media container without letting the other users know that the first user is listening to the media container, thereby providing the first user with a higher level of privacy. Hiding the engagement of the first user with the media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input sequences corresponding to deleting the media container or checking out the device to prevent other users from seeing the first user is engaging with the media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 12C, in some embodiments, the one or more media items in the first container include (1226) one or more of a playlist, an album, a station broadcaster (e.g., pre-existing or carefully organized), and individual music items.

In some embodiments, the device receives (1228), via the one or more input devices, user input (e.g., hard/long press) on a representation of the first media container, and displays (1228) on the display a menu including affordances that, when activated, trigger respective user interface operations. For example, in fig. 8M-8N, device 100 displays menu 822 in response to receiving user input 836. In some embodiments, the menu is an overlay interface, and the user interface operations triggered by the affordance include (1230) one or more of hiding a representation of the first container, adding the first container to the library, adding the first container to the playlist, sharing the first container, and playing the media item from the first container. For example, in FIG. 8J, menu 822 includes various affordances 824 that allow a user to perform various operations.

In some embodiments, the device displays (1232) the privacy settings affordance (e.g., toggle switch) on the display. The device detects (1232) a sequence of one or more inputs at a location corresponding to the privacy settings affordance. In some implementations, a user toggles a switch to hide engagement with a receptacle corresponding to the switch. For example, in fig. 8U, device 100 displays privacy settings affordances 860a and 860b for representations 812a and 812b, respectively. The privacy settings affordance allows the first user to selectively hide/unhide the first user's engagement with a particular media container, thereby improving controllability of the device 100 and providing the first user with a higher level of privacy. Displaying the privacy settings affordance enhances operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to hide the first user's engagement with the media container), and in addition, it enables the user to use the device more quickly and efficiently, thereby reducing power consumption and extending the battery life of the device.

In some embodiments, the device detects (1234) a user input at a location corresponding to a representation of a respective media container. In some implementations, the user taps the representation of the container to hide the container.

Referring to fig. 12D, in some embodiments, after the first user's engagement with the first media container is hidden from view by other users having a predetermined relationship with the first user, the device detects (1236) subsequent engagement of the first user with one or more of the containers of media items. In response to detecting subsequent engagement of the first user with the container of the one or more media items, the device updates (1236) the rankings of the plurality of representations of the container of media items based on one or more of the frequency of engagement and the recency of engagement (e.g., the media container remains available in the user's profile but is hidden from other users). In some embodiments, the device detects (1238) engagement of the first user with the first media container after the engagement of the first user with the first media container is hidden from view by other users having a predetermined relationship with the first user, and after detecting engagement of the first user with the first media container, the device maintains (1238) changes to the representation of the first media container indicating that the engagement of the first user with the media container remains hidden from view by other users having a predetermined relationship with the first user. For example, in fig. 8K-8L, device 100 updates the location of representation 812b after playing "album FED" in response to user input 834. Updating the location of the representation for the media container after the user engages with the media container makes it easier for the user to engage with the media container in subsequent attempts, thereby providing a better user experience. Updating the location of the representations of the hidden media container enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for user input corresponding to scrolling through the representations to view the representations of the hidden media container), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

Referring to fig. 12E, in some embodiments, after the engagement of the first user with the first media container is hidden from view by other users having a predetermined relationship with the first user, the device forgoes (1240) displaying a representation of the first media container on the published version of the profile page for the first user. The public version of the profile page is visible to other users having a predetermined relationship with the first user. For example, in fig. 8G, after the first user hides the first user's engagement with "album FED," the display of representation 812b is abandoned for the published version 804 of the first user's user profile. In some embodiments, the device maintains (1240) a display of the altered representation of the first media container on a private version of a profile page for the first user. The private version of the profile page is visible only to the first user. For example, in fig. 8H, after the first user hides the first user's engagement with the "album FED," a display of a representation 812b is maintained for the private version 804a of the first user's user profile. Forgoing the display of the representation of the hidden media container according to the private version of the user profile provides more privacy for the user, thereby enhancing the user experience.

In some embodiments, after the first user's engagement with the first media container is hidden from view by other users having a predetermined relationship with the first user, the device receives (1242), via the one or more input devices, a request to unhide the first user's engagement with the first media container (e.g., receiving a tap on the representation and/or receiving a long press/hard press and then a tap on the "unhide" affordance in the menu). In response to receiving the request to unhide the splice, the device restores (1242) the change in appearance of the representation of the first media container. The change in appearance of the representation of the first media container indicates that the first user's engagement with the first media container is no longer hidden from view by other users having a predetermined relationship with the first user. For example, in fig. 8O, the device 100 receives a user input 838 to unhide the first user's engagement with the "album FED". In response to receiving user input 838, in fig. 8P, device 100 changes the appearance of representation 812b to indicate that the first user's engagement with "album FED" is no longer hidden from other users. Changing the appearance of the representation of the media container to indicate that the engagement of the first user with the media container is no longer hidden enhances the operability of the device and makes the user device interface more efficient (e.g., by reducing the need for a sequence of user inputs corresponding to a request to determine whether the engagement of the first user with the media container is hidden), and in addition, it enables the user to use the device faster and more efficiently, thereby reducing power consumption and extending the battery life of the device.

It should be understood that the particular order in which the operations in fig. 12A-12E are described is merely exemplary and is not intended to suggest that the order described is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g., methods 900, 1000, and 1100) also apply in a similar manner to method 1200 described above in connection with fig. 12A-11E. For example, the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described above with reference to method 1200 optionally have one or more features of the user interfaces, user interface elements, media containers, playlists, profiles, notifications, music preferences, predetermined relationships, and the like described herein with reference to other methods described herein (e.g., methods 900, 1000, and 1100). For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus, such as a general-purpose processor (e.g., as described above with respect to fig. 1A and 3) or an application-specific chip. Further, the operations described above with reference to fig. 12A-12E are optionally implemented by components depicted in fig. 1A-1B or fig. 3. For example, detection operation 1208 is optionally implemented by event classifier 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112 and event dispatcher module 174 communicates the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186 and determines whether a first contact at a first location on the touch-sensitive surface (or whether rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface or rotation of the device from one orientation to another. When a respective predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handlers 190 access respective GUI updaters 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments described, with various modifications as are suited to the particular use contemplated.

168页详细技术资料下载

上一篇：一种医用注射器针头装配设备

下一篇：一种电子商务购物记录发布系统

Device, method and graphical user interface for presenting representations of media containers

相关技术

网友询问留言