NETWORK-BASED DISTRIBUTION OF APPLICATION PRODUCTS

BACKGROUND OF THE INVENTION
Field of the Invention

The present invention relates to distribution of digital products and, more particularly, to network-based distribution of digital products.

Description of the Related Art

Today, online media stores, such as iTunes™ Media Store, allow customers (i.e., online users) to purchase or rent media items, such as music or videos, over the Internet. Often, at online media stores, numerous media items made available and are provided by various different content providers, such as music labels or movie companies. Software tools, such as iProducer™ and Label Connect™ available from Apple Inc. of Cupertino, Calif., can assist content providers with online submission of media content to the iTunes™ Media Store.

Software programs are also available to purchased or licensed at retail stores as well as online stores. Conventionally, a software program is primarily purchased as a compact disc (CD) containing the software program. Alternatively, purchasers can often purchase and download a software program from an online retailer or a software provider's website. However, when an online retailer operates to sell software programs of various independent parties, there are difficulties in providing the digital program files and supporting information/files to the online retailers. This problem is exacerbated by a large number of small software providers that often desire to partner with the online retailer. As a result, online retailers that receive online submissions face substantial burdens and difficulties due to the wide range of variation with respect to the submissions.

Therefore, there is a need for improved approaches to facilitate distribution of software programs to online retailers.

SUMMARY OF THE INVENTION

The invention relates to an improved system and method for submitting, distributing and/or managing digital products with respect to a product distribution site. The submission of digital products to the product distribution site is able to be performed by numerous submitters in a uniform and computer-assisted manner. The submitted digital products can then be managed in a largely automated manner and made available for online purchase and distribution at the product distribution site. Once a digital product is submitted, the user can access the status of the digital product submission to obtain information of whether the digital product has been approved or rejected. After digital products are approved, the digital products are made available at the product distribution site such that user can search, browse and purchase any of the digital products. In one embodiment, the digital products are computer program products (e.g., computer software programs). The product distribution site can also be referred to as an online product hosting site.

According to one embodiment, an online distribution system for digital products, namely computer program products, can receive electronic submission of not only computer program products but also product information, developer information and distribution parameters. The product distribution system can then present the computer program products for distribution at an online product distribution site in accordance with the distribution parameters. The online product distribution site also can present potential purchases with product information and/or developer information prior to any purchase.

Product information and/or developer information can be used to generate windows (or webpages) for presentation of such information. In one embodiment, these windows can be automatically generated from the electronic submission of the product information and/or the developer information. Further, these windows can have a consistent pattern that facilitates usage by users that often search and browse through many different available computer program products.

The invention can be implemented in numerous ways, including as a method, system, device, apparatus (including computer readable medium and graphical user interface). Several embodiments of the invention are discussed below.

As a method for locating information on a digital product that is made available for distribution at an online repository, one embodiment of the invention includes at least: receiving an electronic submission of product information and distribution information pertaining to the digital product; rendering the digital product available for distribution from an online store in accordance with the distribution information; and assisting a user to the online store in locating at least a portion of the product information pertaining to the digital product.

As a computer-implemented method for accessing information concerning application products from an online repository, one embodiment of the invention can, for example, include at least: presenting an electronic information page providing descriptive information on a plurality of different application programs, the electronic information page including, for each of the different application programs, at least descriptive information, a first user interface control to access developer information and a second user interface control to access application information; presenting a developer information page in response to selection of the first user interface control of the electronic information page, the developer information page including at least text data pertaining to the particular developer; and presenting an application information page in response to selection of the second user interface control of the electronic information page, the application information page including at least text and graphic data pertaining to the particular application program.

As a graphical user interface for locating and downloading a digital product from an online distribution site, one embodiment of the invention can, for example, include at least: a main window configured to promote a plurality of digital products and to enable a user to search or browse the digital products or access information about the digital products; a search dialog or window configured to assist the user in searching the digital products; and a main application window configured to promote a plurality of digital computer program products. The main window can be replaced by the main application window when the user initiates presentation of the main application window

Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The file of this patent contains at least one drawing executed in color. Copies of this patent with color drawing(s) will be provided by the Patent and Trademark Office upon request and payment of the necessary fee.

The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like elements, and in which:

FIG. 1 is a block diagram of a product submission and distribution system according to one embodiment of the invention.

FIG. 2 is a flow diagram of a digital product submission process according to one embodiment of the invention.

FIG. 3 is a block diagram of a product submission and management system according to one embodiment of the invention.

FIG. 4 is a block diagram of a project management system according to one embodiment of the invention.

FIG. 5 is a flow diagram of an application configuration and distribution process according to one embodiment of the invention.

FIGS. 6A and 6B are flow diagrams of an online store navigation process according to one embodiment of the invention.

FIG. 7A is a flow diagram of a search process according to one embodiment of the invention.

FIG. 7B is a flow diagram of a browse process according to one embodiment of the invention.

FIG. 8 is a flow diagram of an application list process according to one embodiment of the invention.

FIG. 9 is a flow diagram of an application update process according to one embodiment of the invention.

FIG. 10 is a diagram of a graphical user interface system according to one embodiment of the invention.

FIGS. 11-26 are exemplary screen illustrations pertaining to representative graphical user interfaces.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of various aspects of the invention are discussed below with reference to FIGS. 1-26. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.

FIG. 1 is a block diagram of a product submission and distribution system 100 according to one embodiment of the invention. The product submission and distribution system 100 includes a product distribution site 102. The product distribution site 102 provides an online access point for distribution of various digital products. For example, the product distribution site 102 can be referred to as an online store. A product submission and management system 104 operates to receive submissions of digital products from various digital product submitters. The product submission and management system 104 can process submission of digital products and authorize distribution of approved digital products. The digital products can be stored in a products store 106. In one embodiment, the products store 106 includes a mass data store and one or more databases. The products store 106 provides mass storage of the numerous digital products that are available for distribution (e.g., purchase or rental). For example, digital products that have been purchased can be accessed from the products store 106 over a data network 108 by way of the product distribution site 102. Examples of digital products are computer program products such as applications (or application programs), animations, or presentations.

The product submission and distribution system 100 also includes a first client 110 and a second client 112. Typically, the product submission and distribution system 100 would include a plurality of different clients 110, 112. The first client 110 includes a network access program 114. The second client 112 includes a product submission program 116. Some clients can also include both the network access program 114 and the product submission program 116. The network access program 114 is an application program (e.g., software application) that operates on the first client 110, which is a computing device. One example of a suitable network access program is a network browser (e.g., Microsoft Explorer or Safari). Another example of a suitable network access program is iTunes™ offered by Apple Inc. The first client 110 is coupled to the product distribution site 102 through the data network 108. Hence, any of the first clients 110 can interact with the product distribution site 102 to review, purchase and/or manage digital products.

The product submission program 116 is also an application program (e.g., software application) that operates on the second client 112, which is a computing device. The product submission program 116 is used to submit digital products to the product submission and management system 104 for eventual distribution by the media distribution site 102. Although the network access program 114 and the product submission program 116 are shown in FIG. 1 as separate programs, it should be understood that such programs can be integrated into a single program or reside on the same client machine.

In the product submission and distribution system 100 shown in FIG. 1, the digital products are submitted to the product submission and management system 104 by way of the product submission program 116. The digital products that have been submitted (e.g., via the second client 112 are processed and then stored in the products store 106. Thereafter, the stored digital products are available to be purchased from the product distribution site 102. Upon purchasing a particular digital product, the product distribution site 102 permits the digital data for the particular digital product to be retrieved from the products store 106 and then delivered (e.g., downloaded) from the product distribution site 102 to the requesting client 110 through the data network 108. In this regard, the product distribution site 102 or some other delivery server (not shown) obtains the digital data corresponding to the particular digital product from the products store 106 and downloads such digital data through the data network 108 to the client 110. The downloaded digital data can then be stored on the client 110. In one embodiment, the downloaded digital data is encrypted as received at the client 110 but is decrypted and then perhaps re-encrypted before persistently stored on the client 110. Thereafter, the client 110 can utilize (e.g., execute) the digital data of the digital product at the client 110.

The product submission and distribution system 100 allows a user of the client 110 to utilize the network access program 114 to browse, search or sort through a plurality of digital products that can be purchased from the product distribution site 102. The network access program 114 may also allow the user to preview or demo some or all of a digital product. In the event that the user of the network access program 114 desires to purchase a particular digital product, the user (via the network access program 114) and the product distribution site 102 can engage in an online commerce transaction in which the user pays for access rights to the particular digital product. In one embodiment, a credit card associated with the user is credited for a purchase or rental amount of the particular digital product.

The submission and purchase of the digital products can be achieved over the data network 108. In other words, the submission and purchase of the digital products can be achieved online. The purchase of media items online can also be referred to as electronic commerce (e-commerce). In one embodiment, the data network 108 makes use of at least a portion of the Internet. The clients 110, 112 can vary with application but generally are computing devices that have memory storage. Often, the clients 110, 112 are personal computers or other computing devices that are capable of storing and presenting media to their users. In one embodiment, the connections through the data network 108 between the product distribution site 102 and the clients 110, 112 can be through secure connections, such as Secure Sockets Layer (SSL).

Although the product distribution site 102, the product submission and management system 104 and the products store 106 are shown in FIG. 1 as being separate components, it should be understood that any of these components can be combined into one or more apparatus. For example, the product submission and management system 104 can be incorporated into the product distribution site 102. As another example, the products store 106 can be incorporated into the product distribution site 102 or the product submission and management system 104.

FIG. 2 is a flow diagram of a digital product submission process 200 according to one embodiment of the invention. The digital product submission process 200 can, for example, be performed by a client device, such as the client 114, or a server device, such as the product submission and management system 104.

The digital product submission process 200 can receive 202 product information pertaining to a digital product. The product information can vary depending upon the type of digital product being submitted. In one implementation, one type of digital product that can be submitted to an online repository by the digital product submission process 200 is a digital program product, such as a computer program product. Examples of product information for a computer program product can include one or more of: a product name, a supported device type indication, genre indication, version number, product identifier, support information, and license agreement information.

Next, a least one electronic file pertaining to a digital product can be uploaded 204. The digital product can have one or more electronic files associated therewith. For example, the digital product may include a binary file, a support or help file, and/or one more exemplary screen illustrations.

In addition, a least one distribution parameter to be used with the digital product can be received 206. A distribution parameter is a parameter that can be utilized to control or influence the manner in which the digital product is able to be distributed. One example of a distribution parameter is a pricing parameter. As an example, a pricing parameter can specify a price or a price tier to be associated with the digital product. Other distribution parameters can pertain to digital storefronts from which the digital product is to be distributed from. Still further, distribution parameters could also pertain to preview eligibility, license categories (types), etc.

Thereafter, the digital product can be submitted 208 to the online repository. The online repository can, for example, correspond to the product submission and management system 104. The online repository can receive the one or more electronic files, the associated product information and the one or more distribution parameters. The online repository can then operate to permit distribution of the digital product, as contained in the one or more electronic files, from a product distribution site (e.g., an online store) in accordance with the product information and the one or more distribution parameters. After the submission 208 of the digital product to the online repository, the digital product submission process 200 can end.

FIG. 3 is a block diagram of a product submission and management system 300 according to one embodiment of the invention. The product submission and management system 300 can, for example, represent one embodiment of the product submission and management system 104 illustrated in FIG. 1.

The product submission and management system 300 can require a login 302. For example, the login can require a user (i.e., digital product submitter) to provide a user name and a password. If the digital product submitter has successfully logged into the product submission and management system 300, the digital product submitter can be presented with a system navigation page 304. From the system navigation page 304, the digital product submitter can access one or more modules that are supported by the product submission and management system 300. According to one embodiment, as illustrated in FIG. 3, the modules supported by the product submission and management system 300 can include a product management module 306, a contract request module 308, a royalty module 310, and an account management module 312.

The product management module 306 can allow the digital product submitter to submit new products and control distribution of such new products. The product management module 306 can also allow the digital product submitter to edit previous submissions. The contract request module 308 can permit the digital product submitter to request a contract with an entity that provides the product distribution. Such a contract can enable the digital products submitter to distribute digital products using a product distribution site (e.g., online store) provided by the entity. The royalty module 310 can assist the digital product submitter in monitoring distribution of all digital products associated with the digital product submitter, including monitoring royalties that will or have in provided to the digital submitter due to distribution of such digital products. For example, the digital product submitter can access monthly royalty reports. The account management module 312 can provide centralized account management for the digital products, including, for example, access permissions, email settings, basic account information to be associated with the digital products matter.

FIG. 4 is a block diagram of a project management system 400 according to one embodiment of the invention. The project management system 400 includes a product management base page 402. From the project management base page 402 a user can navigate to different pages to facilitate (i) addition of a new product to the project management system 400, (ii) preview of product representations for distribution, and/or (iii) review of status details pertaining to one or more products.

When the user interacts with the product management base page 402, a default setting page 404 can be presented. The default setting page 404 allows the user to configure default settings. Following the default setting page 404, a product information page 406 can be presented. The product information page 406 allows a user to enter product information pertaining to a new product. Following the product information page 406, a file upload page 408 can be presented. The file upload page 408 allows the user to specify digital files to be uploaded and associated with the new product. Following the file upload page 408, a distribution parameters page 410 can be presented. The distribution parameters page 410 allows the user to enter various parameters that affect distribution, such as pricing information. Following the distribution parameters page 410, a storefront and localization page 412 can be presented. The storefront and localization page 412 can allow the user to specify all or certain storefronts from which the new product is to be available for distribution (e.g., purchase). Also, to the extent that some of such storefronts are in geographically different regions of the world, the localization information can also be provided by the user. For example, the localization information can provided foreign language versions of some of the product information. Following the storefront and localization page 412, a product submission page 414 can be presented. The product submission page 414 can allow the user to confirm data that has been provided for the new product and then cause the submission of such information to a product submission and management system, such as the product submission and management system 104 illustrated in FIG. 1.

FIG. 5 is a flow diagram of an application configuration and distribution process 500 according to one embodiment of the invention. The application configuration and distribution process 500 can, for example, be performed by an online product distribution site, such as the product distribution site 102 illustrated in FIG. 1.

The application configuration and distribution process 500 is processing performed after submission of one more digital products to a product submission and management system. In particular, the application configuration and distribution process 500 produces 502 a developer page using developer information previously provided to the product submission and management system. Here, the developer page is an electronic information page that is specific to a particular developer of products, namely, application programs. The developer page can be produced 502 in advance of being utilized or can be dynamically generated as needed.

In addition, an application page can be produced 504 using product information previously provided to the product submission and management system. The application page is an electronic information page that is specific to a particular application program (computer program product) that has been submitted to the product submission and management system for distribution by an online product distribution site. As discussed below, persons interested in purchasing the particular application can gain access to the application page to review information pertaining to the particular application. The application page can be produced in 504 in advance of being utilized or can be dynamically generated as needed.

Thereafter, the application configuration and distribution process 500 can facilitate 506 user navigation at an online store to a developer page or an application page. Typically, the online product distribution side hosts an online store that stores numerous developer pages and numerous application pages. As potential purchasers search, browse or otherwise navigate through the various available applications at the online store, such potential purchasers can access appropriate developer pages or application pages. These developer pages or application pages thus assist potential purchasers in determining whether to purchase the associated application program. In one embodiment, the developer pages and the application pages contain user interface controls that allow potential purchasers to initiate purchase of the associated application program. Following the block 506, the application configuration and distribution process 500 can end.

Allowing users to navigate an online store that supports the sale of numerous application programs developed by numerous different developers requires a series of informational pages (webpages). The appropriate ones of the informational pages can be presented to the users as they navigate the online store. According to one embodiment, a graphical user interface system can provide a series of informational pages that can be accessed by the users. The series of informational pages can support a plurality of different functions with respect to the online store. Examples of supported functions can include searching, browsing, sorting, purchasing, updating, listing and reporting.

FIGS. 6A and 6B are flow diagrams of an online store navigation process 600 according to one embodiment of the invention. The online store navigation process 600 can present 602 an online store main page. From the online store main page, a user can initiate a search function, a browse function, an application listing function, update function or some other function. The functions can be available on the online store main page or can be available from other pages that can be navigated to (directly or indirectly) from the online store main page.

A decision 604 can determine whether a search request has been received. When the decision 604 determines that a search request has been received, a search process can be performed 606. On the other hand, when the decision 604 determines that a search request has not been received, a decision 608 can determine whether a browse request has been received. When the decision 608 determines that a browse request has been received, a browse process can be performed 610. Alternatively, when the decision 608 determines that a browse request has not been received, a decision 612 can determine whether an application list request has been received. When the decision 612 determines that an application list request has been received, an application list process can be performed 614.

On the other hand, when the decision 612 determines that an application list request has not been received, a decision 616 can determine whether an update request has been received. When the decision 616 determines that an update request has been received, an update process can be performed 618. Following the performance 618 of the update process, the online store navigation process 600 can return to repeat the block 602 and subsequent blocks.

Alternatively, when the decision 616 determines that an update request has not been received, a decision 620 can determine whether some other request has been received. When the decision 620 determines that in another request has been received, the other request can be processed 621. Here, the other request represents a general request that can depend upon the implementation of the online store navigation process 600. As examples, the other request might initiate a purchase, a preview, a download, a rating, a review, a navigation operation, etc. When the decision 620 determines that another request has not been made, a decision 622 can determine whether the online store navigation process 600 should end. If the decision 622 determines that the online store navigation process 600 should end, the online store navigation process 600 can end. On the other hand, if the decision 622 determines that the online store navigation process 600 should not and, the online store navigation process can return to repeat me decision 604 and subsequent blocks.

Following any of the blocks 606, 610 and 614, additional processing can be performed by the online store navigation process 600. The additional processing can, for example, provide users with access to developer information, application product information and other related information. Accordingly, as shown in FIG. 6B, be additional processing can begin with a decision 624 that can determine whether a developer information request has been received. When the decision 624 determines that a developer information request has been received, a developer page can be presented 626. The developer page is an electronic informational page that presents information concerning a particular developer. Alternatively, when the decision 624 determines that a developer information request has not been received (or following the block 626), a decision 628 can determine whether an application product information request has been received. When the decision 628 determines that an application product information request has been received, an application product page can be presented 630. The application product page is an electronic informational page that presents information concerning a particular application program.

After the application product page is presented 630, a decision 632 can determine whether a license information request has been received. Then the decision 632 determines that a license information request has been received, a license page can be presented 634. Alternatively, when the decision 632 determines that a license information request has not been received, a decision 636 can determine whether a related page request has been received. When the decision 636 determines that a related page request has been received, a related page can be presented 638. One example of a related page is a page containing information on other products, such as applications, that other users were interested in besides the application product of the application product page that has been presented 630.

Following the decision 628 when an application product information request is not received, following the block 634, following the decision 636 when a related page request is not received, or following the block 638, a decision 640 can determine whether another request has been received. The another request represents a generic request they can also be processed by the online store navigation process 600. When the decision 640 determines that another request has been received, the another request can be processed 642.

On the other hand, when the decision 640 determines that another request has not been received, a decision 644 can determine whether a home request has been received. A home request is a navigation command to go back to display of a home page that was previously displayed. When the decision 644 determines that a home request has been received, the online store navigation process 600 can return to repeat the block 602 which represents the beginning of the online store navigation process 600. Alternatively, when the decision 644 determines that a home request has not been made, the online store navigation process 600 can return to repeat the decision 624 so that the user can continue to navigate to a developer page or an application product page.

FIG. 7A is a flow diagram of a search process 700 according to one embodiment of the invention. The search process 700 is, for example, processing that can be performed by the block 606 of the online store navigation process 600 illustrated in FIG. 6A. The search process 700 initially presents 702 into a search page. In one implementation, the search page is a graphical user interface that provides a text box in which a search string can be entered by a user. Additionally, the graphical user interface might also permit the user to select a category, type, price, genre or other attribute of digital products that can be utilized in narrowing search results. After the search page is presented 702, search criteria can be received 704. The search criteria being received represents the search string and possibly other search attributes to be applied. Thereafter, the search can be performed 706. In one embodiment, the search operation searches a database of digital products to determine those one or more digital products that satisfy the search criteria. After the search is being performed 706, the search results can be presented 708. From the search results, the user can further navigate to (i) obtain additional information on one or more application programs provided or identified by the search results, or (ii) obtain additional information on one or more developers of such application programs.

FIG. 7B is a flow diagram of a browse process according to one embodiment of the invention. The browse process 750 can, for example, be performed by the block 610 of the online store navigation process 600 illustrated in FIG. 6A. The browse process 750 can initially present 752 a browse page. The browse page can facilitate a user with identifying browse criteria to be utilized in browsing through the plurality of digital products that are made available at the online store. Next, browse criteria can be received 754. The browse criteria can be provided by the user through interaction with the browse page. After the browse criteria has been received 754, a browse operation can be performed 756. Since the browse process yields a list of one or more digital products that satisfy the browse criteria, browse results can then be presented 758. From the browse results, the user can further navigate to (i) obtain additional information on one or more application programs provided or identified by the browse results, or (ii) obtain additional information on one or more developers of such application programs.

FIG. 8 is a flow diagram of an application list process 800 according to one embodiment of the invention. The application list process 800 can, for example, perform processing associated with the block 614 of the online store navigation process 600 illustrated in FIG. 6A. The application list process 800 can present 802 an application main page. The application main page can present an informational electronic page (webpage) that primarily contains information on application programs. The application main page can also facilitate users in navigating to more particular informational electronic pages that contain a subset of the available application programs. Hence, the application list process 800 can include a decision 804 that determines whether a top applications request has been received. When a top applications request has been received, a top applications page can be presented in 806. Here, the top applications page allows the user to quickly navigate to those application programs that are most popular (i.e., top applications). In one implementation, the top applications page can be provided for all applications or just for free applications. Alternatively, when the decision 804 determines that a top applications request has not been received, a decision 808 can determine whether an all applications request has been received. When the decision 808 determines that an all applications request has been received, an all applications page can be presented 810. In one implementation, the all applications page can be provided for all applications or just for all free applications. When the decision 808 determines that an all applications request has not been received, a decision 812 can determine whether an application category request has been received. When the decision 812 determines that an application category request has been received, an application category page can be presented 814. Following the decision 812 when an application category request has not been received or following any of the blocks 806, 810 or 814, the application list processed 800 can end.

FIG. 9 is a flow diagram of an application update process 900 according to one embodiment of the invention. The application update process 900 can, for example, pertain to processing performed by the block 614 of the online store navigation process 600 illustrated in FIG. 6A. The application update process can present 902 an authentication page. In response to the authentication page, a user that is requesting to update one or more of its previously purchased application programs, can provide authentication information. Hence, authentication information is then received 904. A decision 906 can then determine whether the user has been successfully authenticated using the authentication information. When the decision 906 determines that the user has not been successfully authenticated, the update request can be declined 908. In this case, the application update process 900 ends without having performed any application update.

On the other hand, when the decision 906 determines that the user has been successfully authenticated, the application update process 900 can determine 910 those updates that are available to the user. An update availability page can then be presented 912 to the user. The update availability page can inform the user of the one or more updates to previously purchased application programs that are now available to the user. These updates may be provided free of charge or may require payment of a fee. Next, a decision 914 can determine whether a download request has been received. In one embodiment, from the update availability page, the user can elect to proceed to download the one or more available updates or can decline to download any of the available updates. Of course, if there are no updates available to the user, the decision 914 can effectively likewise determined that download is not to be performed. In the case where the decision 914 determines that a download request has been received, the one or more available application updates are downloaded 916 for the benefit of the user. Typically, the one or more application updates are downloaded 916 to a client machine, such as a personal computer, that is accessing the online store via a network connection. In cases where the application updates are not for previous applications on the personal computer, but instead for another device that couples to the personal computer on occasion, then the application updates are eventually delivered and installed on the another device. For example, the another device might a portable computing device, such as a portable media player, a mobile telephone, or a personal digital assistant, that subsequently couples to the personal computer. In such case, when the portable computing device couples to the client machine, the application updates can be provided to the portable computing device that has the corresponding previous applications installed thereon. A synchronization operation between the client machine and the portable computing device can be used to transfer the application updates from the client machine to the portable computing device. Thereafter, following any downloading 916, the application update process 900 can end.

FIG. 10 is a diagram of a graphical user interface system 1000 according to one embodiment of the invention. The graphical user interface system 1000 includes a plurality of different electronic informational pages. These electronic informational pages (hereafter abbreviated to “pages”) can also be referred to as webpages or graphic user interfaces. In any case, the plurality of different electronic informational pages are interrelated such that a user can often navigate to different pages in a variety of different ways, such of which are described below with reference to FIG. 10. Advantageously, the graphical user interface system 1000 supports user navigation through various different pages to access developer information as well as application product information that are made available online for various application programs (computer program products) being offered for distribution at an online store.

The graphical user interface system 1000 includes an online store main page 1002. From the online store main page 1002, a user can navigate to a search page 1004 that can be utilized to produce a search results page 1006. Also, from the online store main page 1002, a user can navigate to a browse page 1008 that can be utilized to produce a browse results page 1010. Still further, from the online store main page 1002, a user can navigate to an application main page 1012, which provides information substantially dedicated to a plurality of different application programs. From the application main page 1012, a user can navigate to a number of different application listing pages. For example, if the user is interested in a listing of top applications, the user can navigate to a top application page 1014. As another example, if the user is interested in all applications (whether available for free or for a fee), the user can navigate to an all applications page 1016. As still another example, if the user is interested in a particular category of applications, the user can navigate to an application category page 1018.

In addition, the graphical user interface system 1000 includes a developer page that provides information pertaining to a developer. Since the underlying system supports a plurality of different developers, the graphical user interface system 1000 can provide navigation to the developer page 1002 for a particular developer.

The graphical user interface system 1000 also includes application product pages 1022 for the plurality of application programs that are offered for distribution by a product distribution site (e.g., online store). Hence, the graphical user interface system 1000 can facilitate the user in navigating to an application product page 1022 pertaining to a particular application product. More particularly, a user can navigate from various points in the graphical user interface system 1000 to either the developer page 1020 or the application product page 1022 that are relevant to a particular application that has been identified through searching, browsing or listing. Hence, as an example, the user can navigate from the search results page 1006, the browse results page 1010, the top application page 1014, the all application page 1016 or the application category page 1018 to either the developer page 1020 or the application product page 1022 for a particular application. Additionally, a user can navigate from the application product page 1022 to a license page 1024 or a related page 1026. The license page 1024 can provide the user with access to a license agreement that applies to the particular application product. The related page 1026 can provide the user with access to recommendations or correlated purchases from others that may be of interest. Still further, the application product page can also provide a link (i.e., hyperlink) to a developer support website. The network location (address) for the developer support website can be provided by the developer when submitting the application product to the product submission and management system. Accordingly, if the user is having technical difficulties with a particular application product, the user can navigate to the corresponding application product page 1022 and then select (e.g., “click-on”) the available link to be directed to a developer support website.

The online store main page 1002 can also support user navigation to an update operation. The update operation can make available to users those application updates that are available to the user with respect to prior purchases. For example, if the user has previously purchased from an online store an application program that has recently been updated to correct a deficiency or provide a minor enhancement, such an updated application program can be made available to the prior purchaser. In one implementation, the updated application program can be provided free of charge to the prior purchaser. Hence, the online store main page 1002 can provide the user with the ability to initiate an update process whereby the user can obtain the available updates for the application programs they have previously purchased. In one implementation, the online store main page 1002 can provide a user interface control (e.g., hyperlink) to initiate the update process or to navigate to another page from which the update process can be initiated. Optionally, the online store main page 1002 or the another page can also include a numerical indication of the number of available updates. When a user selects the user interface control, the user can navigate to an authentication page 1028. The authentication page 1028 can require that the user enter authentication information so that the system can authenticate the user prior to permitting the user to update any application programs. In the event that the authentication is successful, than an update availability page 1030 can be presented to the user. The update availability page can inform the user of one or more updates that may be available for download by the user. In the event that there are one or more available updates, the user can then elect to decline or proceed with the updates. If the user request the updates, the user can be directed to a download page 1032 which indicates that download is either in process or has been completed.

Another aspect of the invention pertains to graphical user interfaces. The graphical user interfaces can present various pages (or screens) to assist a user in interacting with an online product distribution site. FIGS. 11-26 are exemplary screen illustrations pertaining to representative graphical user interfaces. Each of the different exemplary screen illustrations can be considered a graphical user interface.

FIG. 11 is an exemplary screen illustration of an online store main page 1100 according to one embodiment of the invention. The online store main page 1100 can, for example, represent one implementation of the online store main page 1002 illustrated in FIG. 10. The online store main page 1100 presents information pertaining to a plurality of digital products that are available for purchase (or rental) by an online store. In this example, the online store is the iTunes™ store. The online store main page 1100 can categorize or organize the numerous digital products to facilitate user understanding and/or navigation. Among other things, the online store main page 1100 can include a user interface control 1102 that enables a user to navigate to an application store. The application store can represent a portion of the online store that pertains exclusively to application programs. The online store main page 1100 can also include a user interface control 1104 for initiating application updates. Additionally, the online store main page 1100 can also provide an indication 1106 that represents availability of application updates for the particular user of the online store. As illustrated in FIG. 11, the indication 1106, in one embodiment, can pertain to a numerical indicator, where the numeric value provided in the numerical indicator specifies the number of application updates that are available to the particular user. As used herein, many of the user interface controls can pertain to links, such as hyperlinks to other pages.

FIG. 12 is an exemplary screen illustration of a search results page 1200 according to one embodiment of the invention. The search results page 1200, for example, represents one implementation of the search results page 1006 illustrated in FIG. 10. The search results page 1200 can display a plurality of digital products that satisfy previously identified search criteria. In the search results page 1200 illustrated in FIG. 12, the search results include digital products of various different types. For example, the digital products that satisfied the search criteria can include matching music (e.g., albums), TV seasons, music videos, and application programs. A user interface control that facilitates user purchase of the corresponding digital product can be provided proximate to displayed representations for each of these digital products.

FIG. 13 is an exemplary screen illustration of a search results page 1300 according to one embodiment of the invention. The search results page 1300, for example, represents another implementation of the search results page 1006 illustrated in FIG. 10. The search results page 1300 can display a plurality of application programs that satisfy previously identified search criteria. In the search results page 1300 illustrated in FIG. 13, the search results include a plurality of application programs sorted by popularity.

FIG. 14 illustrates an exemplary screen illustration of an advanced search page 1400 according to one embodiment of the invention. The advanced search page 1400 can permit a user to search the online store for application programs based on search criteria provided for one more specified fields. The fields can pertain to: title/description, developer name, particular category, or device compatibility. For example, device compatibility can specify particular type device on which the application programs are to be executed. Additionally, the application search can be limited to those application programs that are provided free of charge.

FIG. 15 illustrates an exemplary screen illustration of a search results page 1500 according to one embodiment of the invention. The search results page 1500 can represent search results produced by an advanced search carried out in accordance with utilization of the advanced search page 1400.

FIG. 16 illustrates an exemplary screen illustration of a browse page 1600 according to one embodiment of the invention. The browse page 1600 can, for example, represent one implementation of the browse page 1008 illustrated in FIG. 10. As illustrated in FIG. 16, the browse operation can be performed by a user specifying a type of digital product of interest, followed by a category selection, and then followed by a subcategory selection. As each of these selections is made, a lower window region can be updated to list those one or more digital products that satisfied the browse criteria. For example, as illustrated in the browse page 1600, the user has selected “applications” as the digital product type, selected “games” as the appropriate category, and has selected “arcade” as the selected subcategory. Accordingly, the lower window region lists those application programs available from the online store that are arcade games.

FIG. 17 illustrates an exemplary screen illustration of an application main page 1700 according to one embodiment of the invention. The application main page 1700 can be presented to a user that selects the user interface control 1102 on the online store main page 1100 illustrated in FIG. 11. The application main page 1700 principally displays information pertaining to applications that are available for distribution from an online store. The applications can be organized or categorized to assist users in locating applications of interest or to promote certain applications. For example, a user can specify a particular category of application programs to better target the applications being presented by the application main page 1700. Examples of categories include: business, education, entertainment, finance, games, health care & fitness, lifestyle, music, navigation, news, photography, productivity, reference, social networking, sports, travel, utilities, and weather. Some specialized categories (or groupings) can also be utilized, such as all iPhone™ applications, all iPod TouchT™ applications, all free applications, and iPod™ games. Other organizational categories can include top applications, top free application, new releases, just added, staff favorites, etc. Search or navigating through the application programs can be done through searching, browsing, category selections. A user can select any application portrayed on the application main page 1700. In one embodiment, the presentation of application programs can utilize an image-based browser 1702 that can be animated. As another example, applications can organizationally grouped into new releases, just added, top applications and various other groupings. From the application main page 1700, the user can also request application updates. The application main page 1700 can also include a user interface control 1704 that enables a user to request application updates. An indication 1706 can also be display proximate to the user interface control 1704 to signal availability of application updates for the particular user of the online store. In one implementation, the indication 1706 can pertain to a numerical indicator specifying a number of application updates that are available to the particular user.

FIG. 18 illustrates an exemplary screen illustration of a top applications page 1800 according to one embodiment of the invention. The top applications page 1800 can, for example, represent one implementation of the top applications page 1014 illustrated in FIG. 10.

FIG. 19 illustrates an exemplary screen illustration of an all applications page 1900 according to one embodiment of the invention. The all applications page 1900 can, for example, represent one implementation of the all applications page 1016 illustrated in FIG. 10. The all applications page 1900 illustrates a plurality of application programs that are available free of charge and sorted by popularity. In the available applications can also be sorted by different criteria, such as title, release date, etc.

FIG. 20 illustrates an exemplary screen illustration of an application category page 2000 according to one embodiment of the invention. The application category page 2000 can, for example, represent one implementation of the application category page 1018 illustrated in FIG. 10. The application category page 2000 illustrates a plurality of application programs that are associated with the “utilities” category and sorted by popularity.

FIG. 21 illustrates an exemplary screen illustration of a developer page 2100 according to one embodiment of the invention. The developer page 2100 can, for example, represent one implementation of the developer page 1020 illustrated in FIG. 10. The developer page 2100 illustrates a plurality of application programs that are associated with developer and sorted by popularity. Hence, by navigating to a developer page 2100, a user can review those one or more application programs that are associated with a particular developer. In another embodiment, a developer page can include information about the developer, such as descriptive information about the developer and/or the developer's business.

FIG. 22 illustrates an exemplary screen illustration of an application product page 2200 according to one embodiment of the invention. The application product page 2200 can, for example, represent one implementation of the application product page 1022 illustrated in FIG. 10. The application product page 2200 presents detailed information about a particular application product (e.g., application program). In one embodiment, as illustrated in FIG. 22, the application product page 2200 can include a developer name 2202 and application identifying information 2204. The application identifying information 2204 can include various information pertaining to the application program, including a name 2206, a category 2208, a release date 2210, a copyright date 2212, a version 2214, an application size 2216, and a representative image 2218. A user interface control 2220 can provide a “Get App” button when the application is available free of charge. In an alternative embodiment, the user interface control 2220 can provide a “Buy App” button when the application is available for a fee. The application product page 2200 can also include an application description 2222 that provides a brief description of the application program, features, languages and/or requirements. In addition, the application product page 2200 can also include an image viewing region 2223 to present one or more images (e.g., exemplary screen shots) associated with the application program. The application product page 2200 can also include a user interface control 2224 (e.g., link) to a developer's website, a user interface control 2226 (e.g., link) to support for the application program, and/or a user interface control 2228 to a license agreement for the application program. Still further, the application product page 2200 can also include a customer review region 2230 that can contain one or more customer ratings and/or reviews of the application product. In cases, where the application program of the application product page 2200 is a minor version update, the application product page can also indicate what changes have been made (e.g., release notes). The application product page 2200 can also provide a recommendation region 2232 that can list or link to other digital products (e.g., application programs) that customers of the particular application product (e.g., Street Fighter”) also bought.

FIG. 23 illustrates an exemplary screen illustration of a license page 2300 according to one embodiment of the invention. The license page 2300 can, for example, represent one implementation of the license page 1024 illustrated in FIG. 10. The license page 2300 can be presented (e.g., in place of the application product page 2200) when the user interface control 2228 is selected by a user. The license page 2300 provides text of a license agreement that applies to the application program. The license page 2300 can also include the developer name 2202 and the application identifying information 2204 as discussed above with reference to FIG. 22.

FIG. 24 illustrates an exemplary screen illustration of a recommendation page 2400 according to one embodiment of the invention. The recommendation page 2400 can, for example, represent one implementation of the related page 1026 illustrated in FIG. 10. The recommendation page 2400 can be presented (e.g., in place of the application product page 2200) when a user interface control (e.g., link) in the recommendation region 2232 is selected by a user. The recommendation page 2400 provides one or more recommendations of other digital products that the user might be interested in. For example, since the user is presumably interested in the particular application program pertaining to the application product page 2200 illustrated in FIG. 22, the system can predict what other available digital products the user might be interested in. In the recommendation page 2400, the one or more digital products being presented are other applications that customers of the particular application program also bought.

FIG. 25 illustrates an exemplary screen illustration of an update availability page 2500 according to one embodiment of the invention. The update availability page 2500 can, for example, represent one implementation of the update availability page 1030 illustrated in FIG. 10. In this embodiment, the update availability page 2500 indicates that there are no application updates available to the user.

FIG. 26 illustrates an exemplary screen illustration of an update availability page 2600 according to one embodiment of the invention. The update availability page 2600 can, for example, represent another implementation of the update availability page 1030 illustrated in FIG. 10. In this embodiment, the update availability page 2600 indicates that there are a plurality of application updates available to the user. In one implementation, the online store can determine whether any application updates are available based on prior purchases with the online store. The update availability page 2600 can include a user interface control 2602 that allows a user to initiate download of all of the available application updates as well as user interface controls 2604 that allow a user to initiate download of individual one of the available application updates.

This application also references and/or incorporates: (1) U.S. patent application Ser. No. 10/687,534, filed Oct. 15, 2003, and entitled “METHOD AND SYSTEM FOR SUBMITTING MEDIA FOR NETWORK-BASED PURCHASE AND DISTRIBUTION” [Att. Dkt. No. 101-P291], which is hereby incorporated herein by reference; (2) U.S. patent application Ser. No. 11/712,303, filed Feb. 27, 2007, and entitled “PROCESSING OF METADATA CONTENT AND MEDIA CONTENT RECEIVED BY A MEDIA DISTRIBUTION SYSTEM” [Att. Dkt. No. 101-P502], which is hereby incorporated herein by reference; (3) U.S. patent application Ser. No. 11/609,815, filed Dec. 12, 2006, and entitled “TECHNIQUES AND SYSTEMS FOR ELECTRONIC SUBMISSION OF MEDIA FOR NETWORK-BASED DISTRIBUTION” [Att. Dkt. No. 101-P508], which is hereby incorporated herein by reference; (4) U.S. patent application Ser. No. 11/622,923, filed Jan. 12, 2007, and entitled “COMPUTERIZED MANAGEMENT OF MEDIA DISTRIBUTION AGREEMENTS” [Att. Dkt. No. 101-P511], which is hereby incorporated herein by reference; and (5) U.S. Provisional Patent Application No. 61/050,478, filed May 5, 2008, entitled “ELECTRONIC SUBMISSION AND MANAGEMENT OF DIGITAL PRODUCTS FOR NETWORK-BASED DISTRIBUTION”, which is hereby incorporated herein by reference.

The various aspects, features, embodiments or implementations of the invention described above can be used alone or in various combinations.

Embodiments of the invention can, for example, be implemented by software, hardware, or a combination of hardware and software. Embodiments of the invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium generally include read-only memory and random-access memory. More specific examples of computer readable medium are tangible and include Flash memory, EEPROM memory, memory card, CD-ROM, DVD, hard drive, magnetic tape, and optical data storage device. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The many features and advantages of the present invention are apparent from the written description. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.

Number	Date	Country
61059790	Jun 2008	US
61050478	May 2008	US
61059792	Jun 2008	US
61059791	Jun 2008	US

	Number	Date	Country
Parent	12286075	Sep 2008	US
Child	16378302		US

NETWORK-BASED DISTRIBUTION OF APPLICATION PRODUCTS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Provisional Applications (4)

Continuations (1)