Source: https://patents.google.com/patent/US9965146B2/en
Timestamp: 2018-12-12 17:11:27
Document Index: 52718823

Matched Legal Cases: ['§ 119', 'Application No. 60', 'Application No. 10', 'Application No. 2010153571', 'Application No. 2014215929', 'Application No. 2009255409', 'Application No. 2012203197', 'Application No. 2014', 'Application No. 10', 'Application No. 2726117', 'Application No. 2', 'Application No. 200980127249', 'Application No. 2', 'Application No. 201088250', 'Application No. 09', 'Application No. 2016', 'Application No. 200980127249', 'Application No. 200980127249', 'Application No. 10', 'Application No. 7906', 'Application No. 2009255409', 'Application No. 200980127249', 'Application No. 2', 'Application No. 2010153571', 'Application No. 200980127249', 'Application No. 09', 'Application No. 200980127249', 'Application No. 2012203197', 'Application No. 200980127249', 'Application No. 10', 'Application No. 2011', 'Application No. 10', 'Application No. 10', 'Application No. 2011', 'Application No. 200980127249', 'Application No. 2', 'Application No. 2', 'Application No. 2011', 'Application No. 2726117', 'Application No. 2014', 'Application No. 11113270', 'Application No. 201008825']

US9965146B2 - User interface for application management for a mobile device - Google Patents
US9965146B2
US9965146B2 US14279168 US201414279168A US9965146B2 US 9965146 B2 US9965146 B2 US 9965146B2 US 14279168 US14279168 US 14279168 US 201414279168 A US201414279168 A US 201414279168A US 9965146 B2 US9965146 B2 US 9965146B2
US14279168
US20140250015A1 (en )
This application is a continuation of U.S. patent application Ser. No. 13/350,563 filed Jan. 13, 2012, which is a continuation of U.S. patent application Ser. No. 12/354,616, filed Jan. 15, 2009, and which claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application Ser. No. 61/059,730, filed Jun. 6, 2008. The disclosures of the foregoing applications are hereby incorporated by reference in their entirety for all purposes.
The mobile device 100 can also include one or more wireless communication subsystems, such as an 802.11 b/g communication device 186, and/or a Bluetooth™ communication device 188. Other communication protocols can also be supported, including other 802.x communication protocols (e.g., WiMax, Wi-Fi, 3G), code division multiple access (CDMA), global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), etc.
In some implementations, the port device 190, e.g., a Universal Serial Bus (USB) port, or a docking port, or some other wired port connection, is included. The port device 190 can, for example, be utilized to establish a wired connection to other computing devices, such as other communication devices 100, network access devices, a personal computer, a printer, or other processing devices capable of receiving and/or transmitting data. In some implementations, the port device 190 allows the mobile device 100 to synchronize with a host device using one or more protocols, such as, for example, the TCP/IP, HTTP, UDP and any other known protocol. In some implementations, a TCP/IP over USB protocol can be used, as described in U.S. Provisional Patent Application No. 60/945,904, filed Jun. 22, 2007, for “Multiplexed Data Stream Protocol,”, which is incorporated by reference here in its entirety.
The user interface for the application store includes a display portion 236 and a menu portion 226. The menu portion 226 can include several tabs. In particular, the menu portion 226 includes a featured tab 216, a categories tab 218, a top 25 tab 220, a search tab 222, and an updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store, each of which will be described in greater detail below. In some implementations, other tabs can be provided and/or the tab order can vary, for example, as determined by the application store, the mobile device, or based on input received from another remote location.
The display portion 236 displays a featured interface 203 associated with the featured tab 216, which is shown as highlighted in the menu portion 226. The featured interface 203 includes a title bar 201. The title bar 201 includes a recently added button 202 and a staff favorites button 204. The recently added button 202 and staff favorites button 204 are shown as separate buttons. However, the buttons can take other forms including, for example, a single toggle button that can be switched from one to the other by touching the button more than once.
In particular, the application objects 240 shown in the display portion 236 include application objects 210, 212, and 214. Additionally, when the display portion 236 cannot display all of the application objects 240 at one time, the user can scroll 238 up or down to view additional application objects 240. While a scroll 238 is represented by a dotted arrow at a particular portion of the display portion 236, the user can scroll 238 from other points. In particular, the user can scroll by gesturing in a particular direction (e.g., up or down) across the touch-sensitive display 102.
Each application object 240 includes information associated with the particular application. For example, application object 210 includes application information 228. The application information 228 can include an image representing the application, the application name (e.g., “Application 1” for application object 210), a developer's name, and rating information. In some implementations, the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating (e.g., three out of five 5) for the application. In some implementations, stars are partially filled to represent a finer degree of granularity of the average rating.
Additionally, in some implementations, touching the purchase information 408 initiates a process for downloading the application. For example, if the application is free, the download process can begin without further user input. Alternatively, if purchase is required, a user account can be accessed to purchase the application. In some implementations, the user can redeem a coupon or similar credit to purchase the application, In some other implementations, the user is required to provide account or other authentication information before purchasing the application.
The review interface 802 includes menu buttons with suggested problems to report. In particular, the review interface 802 includes a report a bug button 808, a report as offensive button 810, and a concern not listed button 812. The user can select one of the menu buttons by touching a particular menu button in the review interface 802. In some implementations, when a user selects a particular menu button, the selected menu button is highlighted. In some other implementations, when the user selects a menu button an icon is displayed to indicate selection, for example, a checkmark.
Each category button allows the user to transition to an interface providing application objects associated with the particular category. For example, a selection of the games button 904 can cause the categories interface to transition to a game objects interface that includes one or more application objects corresponding to games or otherwise associated with the games category.
The display portion 1002 can also include one or more advertisements. In the display portion 1002, a first advertisement 1008 and a second advertisement 1010 arc shown near the title bar 1001. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements can be presented. Additionally, while the advertisements are shown near the title bar 1001, one or more advertisements can be presented at different locations on the display portion 1002.
In response to holding the application, the held application along with one or more other display objects 106 can become editable (e.g., movable to other locations on the touch-sensitive display 102). Some display objects 106 can be deleted. The system can present an indicator in the editing mode identifying those display objects, for example, a badge with an “X” presented for those display objects that can be deleted. As shown in FIG. 18, “Application 1” 1802 has a badge indicating that this application can be deleted. The user can select the badge (e.g., by touching the “X” on the touch-sensitive display 102) in order to initiate a deletion process for the application.
FIG. 19 is a block diagram 1900 of an example user interface of the mobile device 100 illustrating a rating prompt 1902. When a user selects an application for deletion (e.g., application 1802 of FIG. 18), the rating prompt 1902 can be displayed, for example, on the user-interface provided by the touch-sensitive display 102. In sonic implementations, the portion of the user interface outside of the rating prompt 1902 can be dimmed relative to the rating prompt 1902.
displaying, on a display of a mobile device, an application management interface that includes:
a set of application objects corresponding to respective applications from an application store server that are available for installation on the mobile device;
a first user activated element associated with only displaying application objects that require payment, and
a second user activated element associated with displaying application objects that do not require payment;
detecting selection of the first user activated element associated with only displaying application objects that require payment;
in response to detecting selection of the first user activated element, ceasing to display application objects that do not require payment and displaying at least some of the application objects that require payment;
detecting a selection of an application object from the displayed application objects;
receiving, from the application store server, an application that corresponds to the selected application object; and
installing, on the mobile device, the application that corresponds to the selected application object.
displaying a set of application icons on a home screen; and
receiving a request to display the application management interface, wherein the application management interface is displayed in response to receiving the request.
3. The method of claim 2, wherein receiving the request to display the application management interface includes receiving an input directed to a selection of an app store icon, and wherein the app store icon is included in the displayed set of application icons.
displaying the set of application icons on the home screen prior to installing the application on the mobile device, wherein the set of application icons does not include the application icon corresponding to the installed application.
determining and presenting purchasing information associated with the application that corresponds to the selected application object, the purchasing information indicating a cost associated with the application that corresponds to the selected application object; and
prior to installing the application that corresponds to the selected application object on the mobile device:
accessing a user account to purchase the application that corresponds to the selected application object; and
receiving an indication that the application that corresponds to the selected application object has been purchased, wherein the indication that the application that corresponds to the selected application object has been-purchased is received when the user account has been charged the cost associated with the application that corresponds to the selected application object via an electronic payment.
6. The method of claim 5, wherein accessing the user account includes requesting and receiving authentication information associated with the user account.
detecting a selection of the second user activated element associated with displaying application objects that do not require payment; and
in response to detecting selection of the second user activated element, ceasing to display the application objects that require payment and displaying at least some of the application objects that require payment.
8. The method of claim 7, wherein at least one application object of the displayed application objects displays purchase information.
9. The method of claim 8, wherein the purchase information for the at least one application object includes at least one of:
an indication that an application that corresponds to the at least one application object does not require payment; or
an indication that the application that corresponds to the at least one application object has already been installed.
10. The method of claim 1, including detecting an input to view additional application objects from the application objects that require payment; and, in response to detecting the input to view the additional application objects that require payment, scrolling the set of application objects that require payment to present additional application objects that require payment.
11. The method of claim 1, wherein at least one application object of the displayed application objects includes a rank and the displayed application objects are presented in ranked order.
12. The method of claim 1, including, before installing the application that corresponds to the selected application object, transitioning from displaying the application management interface to displaying a home screen including a placeholder object corresponding to the selected application.
13. The method claim 12, wherein the placeholder object includes an indicator of installation progress of the application that corresponds to the selected application object.
displaying, on a display of the mobile device, an application management interface that includes:
a set of application objects corresponding to respective applications from an application store server that are available for installation on the electronic device;
15. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions which, when executed by a mobile device with a display, cause the mobile device to:
display, on a display of the mobile device, an application management interface that includes:
detect selection of the first user activated element associated with only displaying application objects that require payment;
in response to detecting selection of the first user activated element, cease to display application objects that do not require payment and displaying at least some of the application objects that require payment;
detect a selection of an application object from the displayed application objects;
receive from the application store server an application that corresponds to the selected application object; and
install, on the mobile device, the application that corresponds to the selected application object.
16. The mobile device of claim 14, further comprising instructions for:
17. The mobile device of claim 16, wherein receiving the request to display the application management interface includes receiving an input directed to a selection of an app store icon, and wherein the app store icon is included in the displayed set of application icons.
18. The mobile device of claim 16, further comprising instructions for:
19. The mobile device of claim 14, further comprising instructions for:
20. The mobile device of claim 19, wherein accessing the user account includes requesting and receiving authentication information associated with the user account.
21. The mobile device of claim 14, further comprising instructions for:
22. The mobile device of claim 21, wherein at least one application object of the displayed application objects displays purchase information.
23. The mobile device of claim 22, wherein the purchase information for the at least one application object includes at least one of:
24. The mobile device of claim 14, further comprising instructions for:
detecting an input to view additional application objects from the application objects that require payment; and,
in response to detecting the input to view the additional application objects that require payment, scrolling the set of application objects that require payment to present additional application objects that require payment.
25. The mobile device of claim 14, wherein at least one application object of the displayed application objects includes a rank and the displayed application objects are presented in ranked order.
26. The mobile device of claim 14, further comprising instructions for, before installing the application that corresponds to the selected application object, transitioning from displaying the application management interface to displaying a home screen including a placeholder object corresponding to the selected application.
27. The mobile device of claim 26, wherein the placeholder object includes an indicator of installation progress of the application that corresponds to the selected application object.
28. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
display a set of application icons on a home screen; and
receive a request to display the application management interface, wherein the application management interface is displayed in response to receiving the request.
29. The non-transitory computer readable storage medium of claim 28, wherein receiving the request to display the application management interface includes receiving an input directed to a selection of an app store icon, and wherein the app store icon is included in the displayed set of application icons.
30. The non-transitory computer readable storage medium of claim 28, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
display the set of application icons on the home screen prior to installing the application on the mobile device, wherein the set of application icons does not include the application icon corresponding to the installed application.
31. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
determine and present purchasing information associated with the application that corresponds to the selected application object, the purchasing information indicating a cost associated with the application that corresponds to the selected application object; and
access a user account to purchase the application that corresponds to the selected application object; and
receive an indication that the application that corresponds to the selected application object has been purchased, wherein the indication that the application that corresponds to the selected application object has been-purchased is received when the user account has been charged the cost associated with the application that corresponds to the selected application object via an electronic payment.
32. The non-transitory computer readable storage medium of claim 31, wherein accessing the user account includes requesting and receiving authentication information associated with the user account.
33. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
detect a selection of the second user activated element associated with displaying application objects that do not require payment; and
in response to detecting selection of the second user activated element, cease to display the application objects that require payment and displaying at least some of the application objects that require payment.
34. The non-transitory computer readable storage medium of claim 33, wherein at least one application object of the displayed application objects displays purchase information.
35. The non-transitory computer readable storage medium of claim 34, wherein the purchase information for the at least one application object includes at least one of:
36. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
detect an input to view additional application objects from the application objects that require payment; and,
in response to detecting the input to view the additional application objects that require payment, scroll the set of application objects that require payment to present additional application objects that require payment.
37. The non-transitory computer readable storage medium of claim 15, wherein at least one application object of the displayed application objects includes a rank and the displayed application objects are presented in ranked order.
38. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to, before installing the application that corresponds to the selected application object, transition from displaying the application management interface to displaying a home screen including a placeholder object corresponding to the selected application.
39. The non-transitory computer readable storage medium of claim 38, wherein the placeholder object includes an indicator of installation progress of the application that corresponds to the selected application object.
US14279168 2008-06-06 2014-05-15 User interface for application management for a mobile device Active US9965146B2 (en)
US15974510 Continuation US20180335904A1 (en) 2008-06-06 2018-05-08 User Interface for Application Management for a Mobile Device
US20140250015A1 true US20140250015A1 (en) 2014-09-04
US9965146B2 true US9965146B2 (en) 2018-05-08
JP6036852B2 (en) * 2013-01-24 2016-11-30 富士通株式会社 Portable information terminals, control method, control program
JPH03233750A (en) 1990-02-09 1991-10-17 Fujitsu Ltd Process state display/conversion system
US20040130576A1 (en) 2003-01-08 2004-07-08 Pioneer Corporation Touchscreen display device
JP2005196617A (en) 2004-01-09 2005-07-21 Sony Corp Information processor, information processing method, recording medium and program
JP2005251167A (en) 2004-01-09 2005-09-15 Microsoft Corp On-device application catalog updated by management server
US20060212548A1 (en) 2005-03-15 2006-09-21 Microsoft Corporation Method and system for installing applications via a display page
RU2005125837A (en) 2004-08-16 2007-02-20 Майкрософт Корпорейшн (Us) Team user interface for display on the screen of selectable functionality controls software
AU2002359001A1
JP2001521254A (en) 1997-10-24 2001-11-06 マイクロソフト コーポレイション Application installation management system and method of the mobile device
CN1534471A (en) 2003-03-27 2004-10-06 微软公司 Application program centrol user interface technology
JP2004326736A (en) 2003-03-27 2004-11-18 Microsoft Corp Application-centered user interface method
KR101086125B1 (en) 2003-03-27 2011-11-25 마이크로소프트 코포레이션 Application-centric user interface techniques
KR20040086535A (en) 2003-03-27 2004-10-11 마이크로소프트 코포레이션 Application-centric user interface techniques
CN1906565A (en) 2004-01-09 2007-01-31 诺基亚公司 Adaptive user interface input device
US20120117504A1 (en) 2008-06-06 2012-05-10 Apple Inc. User Interface for Application Management for a Mobile Device
Ascii.jp, "Listen and Purchase & Play Immediately!! A Wonderful World of Wi-Fi Stores", Ascii.jp [online] Japan, Kabushiki Kaisha Kadokawa, http://ascii.jp/elem/000/000/069/69364, Sep. 23, 2007, 5 pages.
Certificate of Patent, dated Aug. 13, 2015, received in Korean Patent Application No. 10-2013-7002719, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Decision to Grant, dated Sep. 28, 2012, received in Russian Patent Application No. 2010153571, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Final Office Action mailed on Apr. 27, 2011 for U.S. Appl. No. 12/354,616, 10 pages.
Hirokawa, Getting Started with Super Easy iPod Touch Hack, MAC Power 2008 Winter, Japan, Kabushiki Kaisha Ascii, first edition, ISBN 978-4-7561-5081-3, Dec. 21, 2007, 4 pages.
Ikeda, iPhone 2.0 Beta & Software Development Kit (SDK) Released, MacFan, Japan, Kabushiki Kaisha Mainichi Communications, vol. 16, No. 5, (vol. 301), May 1, 2008, 10 pages.
International Preliminary Report on Patentability mailed Dec. 6, 2010 for PCT Patent Application No. PCT/US2009/043840, 8 pages.
International Search Report and Written Opinion mailed Aug. 12, 2009 for PCT Patent Application No. PCT/US2009/043840, 15 pages.
Non-Final Office Action mailed on Aug. 24, 2010 for U.S. Appl. No. 12/354,616, 9 pages.
Non-Final Office Action mailed on Jul. 31, 2013 for U.S. Appl. No. 13/350,563, 20 pages.
Notice of Acceptance, dated Jul. 14, 2016, received in Australian Patent Application No. 2014215929, which corresponds with U.S. Appl. No. 13/354,616, 2 pages.
Notice of Acceptance, dated Jul. 5, 2012, received in Australian Patent Application No. 2009255409, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Notice of Acceptance, dated Jun. 30, 2014, received in Australian Patent Application No. 2012203197, which corresponds with U.S. Appl. No. 13/354,616, 1 page.
Notice of Allowance mailed on Jan. 31, 2014 for U.S. Appl. No. 13/350,563, 12 pages.
Notice of Allowance mailed on Nov. 16, 2011 for U.S. Appl. No. 12/354,616, 5 pages.
Notice of Allowance, dated Apr. 22, 2016, received in Japanese Patent Application No. 2014-031795, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Notice of Allowance, dated Jun. 30, 2015, received in Korean Patent Application No. 10-2013-7002719, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Notice of Allowance, dated Mar. 16, 2017, received in Canadian Patent Application No. 2726117, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Notice of Allowance, dated May 6, 2014, received in U.S. Appl. No. 13/350,563, 5 pages.
Notice of Allowance, dated Sep. 22, 2015, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Notice of Grant, dated Apr. 22, 2016, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Notice of Reinstatement, dated Apr. 27, 2016, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 4 pages.
Notification of Grant, dated Nov. 26, 2014, received in Singapore Patent Application No. 201088250, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, date Jul. 15, 2015, received in Australian Patent Applicaton No. 2012203197, which corresponds with U.S. Appl. No. 13/354,616, 3 pages.
Office Action, dated Apr. 10, 2013, received in Mexican Patent Application No. MX/a/2010/013377, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Office Action, dated Apr. 10, 2014, received in European Patent Application No. 09 758 944.4, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Office Action, dated Apr. 3, 2017, received in Japanese Patent Application No. 2016-100793, which corresponds with U.S. Appl. No. 12/354,616, 8 pages.
Office Action, dated Aug. 1, 2013, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Aug. 4, 2014, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Aug. 8, 2014, received in Korean Patent Application No. 10-2013-7002719, which corresponds with U.S. Appl. No. 12/354,616, 4 pages.
Office Action, dated Dec. 16, 2013, received in Mexican Patent Application No. MX/a/2010/013377, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Office Action, dated Dec. 19, 2016, received in Indian Patent Application No. 7906/CHENP/2010, which corresponds with U.S. Appl. No. 12/354,616, 7 pages.
Office Action, dated Dec. 6, 2011, received in Australian Patent Application No. 2009255409, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Feb. 2, 2016, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Feb. 21, 2013, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Feb. 29, 2012, received in Russian Patent Application No. 2010153571, which corresponds with U.S. Appl. No. 12/354,616, 4 pages.
Office Action, dated Jan. 17, 2014, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Jan. 18, 2012, received in European Patent Application No. 09 758 944.4, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Office Action, dated Jan. 4, 2015, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Jul. 1, 2013, received in Australian Patent Application No. 2012203197, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Jul. 2, 2015, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Jun. 28, 2013, received in Korean Patent Application No. 10-2011-7000351, which corresponds with U.S. Appl. No. 12/354,616, 4 page.
Office Action, dated Jun. 29, 2015, received in Japanese Patent Application No. 2011-512509, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Jun. 30, 2012, received in Korean Patent Application No. 10-2011-7000351, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Office Action, dated Mar. 15, 2016, received in Korean Patent Application No. 10-2014-7014295, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Office Action, dated May 7, 2013, received in Japanese Patent Application No. 2011-512509, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Office Action, dated Nov. 23, 2012, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Nov. 25, 2013, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Oct. 2, 2014, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Sep. 7, 2012, received in Japanese Patent Application No. 2011-512509, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Patent, dated Apr. 11, 2017, received in Canadian Patent Application No. 2726117, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Patent, dated May 27, 2016, received in Japanese Patent Application No. 2014-031795, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Patent, dated Sep. 1, 2017, received in Honk Kong Application No. 11113270.1, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Softbank Corporation, "Task Bar Type Launcher," Oh! PC, Japan, Nov. 1, 1997, vol. 16, No. 11, p. 187.
Submission of Prior Art Under 37 CFR1.501, dated Apr. 26, 2012, received in U.S. Appl. No. 12/235,616, 38 pages.
Submission of Prior Art Under 37 CFR1.501, dated Jul. 19, 2012, received in U.S. Appl. No. 12/235,616, 86 pages.
Submission of Prior Art Under 37 CFR1.501, dated Jun. 11, 2012, received in U.S. Appl. No. 12/235,616, 53 pages.
Toru, "For iPod & iTunes Beginners," Nikkei Personal Computing No. 533, Nikkei Business Publications, Inc., Jul. 9, 2007, No. 533, 8 pages.
Written Opinion, dated Feb. 15, 2012, received in Singapore Patent Application No. 201008825-0, 5 pages.