Customizing the app store information page

Abstract

Techniques for digital asset classification are described. One or more holiday scores are assigned to a set of digital media assets. The one or more holiday scores are calculated based on weighted holiday metrics determined based on characteristics of the set of digital assets. A holiday classification is assigned based on the one or more holiday scores, and the set of digital media assets is provided for presentation according to the holiday classification.

Description

Technical Field

[0001] The embodiments described herein relate to the presentation of software applications. More particularly, the embodiments described herein relate to providing a custom visual representation of a software application.

Background Art

[0002] In recent years, the download of software applications (or "apps") from online app stores has become a common way to obtain software applications. An online app store enables a user to download a software application onto the user's device such as a desktop computer or laptop computer, smartphone, or other mobile device, and then install the app on the user's device. Before downloading an app, the user often locates the app within the app store. In response to a user search, the app store can provide the user with results along with a particular set of representative data such as icons, screenshots, text descriptions, and the like.

Brief Description of the Drawings

[0003] The embodiments described herein are shown by way of example and not by way of limitation in the accompanying drawings, with like references indicating like features. Further, some conventional details are omitted in the drawings so as not to obscure the concepts of the invention described herein.

[0004] [Figure 1] A network accessed by an app store by a client device is shown in block diagram form according to one or more embodiments.

[0005] [Figure 2] An example of a variation of a product page provided to different users is shown according to one or more embodiments.

[0006] [Figure 3] This shows an example of app installation from different variations of the product page, using one or more embodiments.

[0007] [Figure 4] A flowchart illustrates a technique for providing variations on a product page to different users, based on one or more embodiments.

[0008] [Figure 5] A flowchart illustrates a technology for providing custom product pages in an app store, based on one or more embodiments.

[0009] [Figure 6] A flowchart illustrates, in one or more embodiments, the technology for providing custom product pages in an app store.

[0010] [Figure 7] A simplified functional block diagram of an exemplary programmable electronic device according to one embodiment is shown. [Modes for carrying out the invention]

[0011] This disclosure relates to a system, method, and computer-readable medium for providing multiple variations of app presentation in an app store, according to one or more embodiments. More specifically, embodiments described herein relate to a technology for providing multiple processes of apps in an app store such that a subsequently downloaded app is presented in the app store in a consistent manner with the original process through which the app was downloaded.

[0012] This disclosure also relates to systems, methods, and computer-readable media for providing multiple variations of app presentation in an app store, in one or more embodiments. In particular, the embodiments described herein relate to techniques for providing custom variations to product pages for specific apps. More specifically, the embodiments described herein relate to techniques for determining a particular version of app information to present to a user in an app store based on a trigger event. The particular version may be selected based on contextual information surrounding the trigger event such that the selected version has some relevance to the user experience prior to navigation to the app information page.

[0013] Embodiments described herein operate within and interface with an app store environment and context in which one or more users can search for and download one or more applications (also called apps) using a client device. The app store 100 may include one or more servers, such as servers 101, 102, and 103, which can provide the functions described herein. For example, server(s) 101 may interface with a client device to implement the method shown in Figures 4 and 6 in order to generate and / or provide a custom app information page and / or customized app content for presentation on one or more client devices, such as client devices 107 and 109, which can take various different forms (e.g., tablet computers such as iPads, smartphones such as iPhones, laptop computers, desktop computers, network media players such as Apple TVs, game / entertainment systems, or other home electronic devices). Client devices 107 and 109 can be connected to the app store 100 by one or more networks 105, such as the Internet, which provide data communication between the client devices and the app store, so that the client devices can send search queries to the app store, receive search results, send requests to download one or more apps, and then receive the download of one or more apps. In one embodiment, a server 101 can create data structures used when providing custom app information pages and / or custom representations of apps to a particular subset of users (e.g., associations between app representations and specific user or device identifiers), and can store those data structures in a storage device 104 for later use by a server 102, which can be configured to receive search queries from client devices and then perform a lookup of one or more data structures to provide a consistent view of app representations in the app store.

[0014] App stores, such as the one shown in Figure 1, can collect information about queries used to search for applications, and information about downloads resulting from user selections of apps presented in the search results generated by those search queries. This information can be collected in logs maintained by the app store that record the queries used and the downloads resulting from those queries. In one embodiment, one or more servers 102 can maintain a record of the queries used and the selections made from the search results of those queries during a user's search session, and this record can be recorded in one or more logs. In one embodiment, in addition to tracking downloads resulting from a particular search query, the app store can track user selections that seek further information about a particular application without necessarily downloading the application. In another embodiment, the app store can track only downloads resulting from search results in order to limit the amount of information that may be relevant. In other words, downloads may be considered more relevant and important information than user selections about more information about an application that do not result in a download.

[0015] The servers (101, 102, 103) and / or client devices 107 and 109 may also include memory for storing and / or retrieving apps from the app store 100. According to some embodiments, client devices 107 and 109 may provide access to the app store 100, which may host multiple applications. The app store 100 may provide a particular user with specific processing regarding the app information page within the app store for a particular app. That is, the view of the app information page from client device 107 may differ from the view of the app information page from client device 109. In some embodiments, client devices 107 and 109 may obtain the same binary download package, and the app store 100 may send metadata indicating specific processing for use in the application so that the user experience is consistent with the app information page presented to the user within the app store 100.

[0016] Figure 2 illustrates an example of how the application's representation can be altered when presented to different users. In some embodiments, an app developer may want to provide multiple representations of the app for different users to download. For example, a developer may want to provide different processing of the application to different users. As a result, according to some embodiments, a developer can track which processing in the app store attracts more users. In some embodiments, the different processing may be encoded in the app's binary so that, depending on which visual representation the user responds to in the app store, the app can be downloaded and launched on the user's device in a consistent manner as the visual processing that the user obtained the app from the app store.

[0017] According to one or more embodiments, an app store can provide different processing 202 and 204 of an app within the app store to different users 200. For example, as shown in Figure 2, if a first user searches for a game called "The Coast" in the app store, they can see an app information page 202 that includes a first icon 206 and a description 208. In some embodiments, the processing includes multiple presentation versions of the app information page. Thus, while processing 202 is presented to some users of the app store, a second processing 204 may be provided to other users 200. For illustrative purposes, the app store information page of the second processing 204 includes a second icon 220 and a second description 222 that are different from the icon 206 and description 208 provided in the first processing of the app information page 202.

[0018] Multiple presentation versions may include a default presentation version and one or more updated variations. In some embodiments, other information may be specific to a particular process, such as screenshots or media items (video content, graphic content, etc.). The processes offered to a particular user may be randomly selected or predefined. Furthermore, in some embodiments, the predefined sharing of user 200 may offer specific processes based, for example, on traffic distribution. As an example, 80% of user 200 may see the default process, and 20% of user 200 may see one or more additional variations of the app information page. For example, process 202 may be the default process offered to users in the app store, while process 204 is a new process that the developer wishes to offer to a subset of users in order to test the appeal or response rate of variations in the process. Thus, a developer can offer multiple processes of the same page to different users in the app store. Furthermore, by doing so, the app store can track the response rates to different processes. For example, an app store may track download rates among users who landed on each variation of the app information page, the time spent on the app information page for each process, and the sharing rate for each process. As an example, a developer may be able to track that over a certain period, a first process 202 in the app store resulted in a 1.9% download rate for the app, while a second process 204 in the app store resulted in a 2.5% download rate for the app. For the purposes of this disclosure, the download rate refers to the percentage of views of a particular process of a presented version of the app information page that resulted in a user downloading the app, for example, by requesting a download through a download icon 210 or 224 on the app information page in the app store.

[0019] As another example, a developer may track the sharing rate of an app to determine, for example, how a particular presented version of an app becomes "viral" within an app store. For example, a user 200 presented with a first version of the app may "share" the app information page 202 at a rate of 0.5% over a certain period, and a user 200 presented with a second version of the app may "share" the app information page 204 at a rate of 1.2%. For the purposes of this disclosure, the sharing rate refers to the percentage of views of a particular version of the presented version of the app information page that resulted in a user sharing the app by sending a link to the app information page to another user, for example, through a share icon 212 or 226 within the app information page in an app store. According to some embodiments, additional users who are recipients of the sharing may have their information page directed to the same presented version that was shared. For example, metadata may be embedded in the sharing link to indicate a particular presented version. Alternatively, different presented versions may be provided either randomly or through a predetermined set of rules. In some embodiments, the app store may provide developers with a user interface that presents performance information regarding various processes, such as download and share rates for each process. Additionally, or alternatively, the user interface may include other statistics such as query traffic (e.g., visits to one or more variations of an information page from shared or direct URLs), confidence values ​​for a particular process to "perform" better (i.e., meet a predetermined threshold performance rate based on download rates, share rates, referral traffic, etc.), estimated increase rates indicating a predicted rate that a particular process will improve the performance of a default process, and / or one or more confidence values ​​related to various predicted rates.

[0020] According to some embodiments, the user experience with an app should remain consistent from the time the app is downloaded and / or launched on the user's device, through to the actual experience of using the app within the app store. Figure 3 shows an illustrative flowchart of how the presentation process remains consistent outside the app store after the application has been downloaded and / or launched.

[0021] In Figure 3, a first user may be presented with a first process 302A on the app's information page, and a second user may be presented with a second process 302B on the same app's information page. As shown in the example in Figure 3, the first process 302A presented on the first user's device shows a first version 304A of the icon for a game called "The Coast," and a first version 306A of the description. Simultaneously, the second process 302B presented on the second user's device shows a second version 304B of the icon for the same game, and a second version 306B of the description. According to some embodiments, downloading the game from either presented version results in the download of the same binary download package. For example, the download package associated with either app's information page may be the same as the various embedded presentation elements.

[0022] In some embodiments, the user experience using the downloaded app should remain consistent when the app is installed and launched. Thus, as shown in desktop 310A, an icon 312A is presented that maintains consistency with the icon 304A presented on the app information page 302A where the app was downloaded. Similarly, on desktop 310B, an icon 312B is presented that maintains consistency with the icon 304B presented on the app information page 302B where the app was downloaded. For example, the same icon presented to the user to represent the app information page in the app store may be configured to be presented on the user's desktop when the app is downloaded and installed on the user device. Other app information may be presented consistently from the information pages within the app store and the installed application, such as screenshots, text, and other media.

[0023] Figure 4 shows a flowchart of a technique for providing different users with variations on a product page according to one or more embodiments. Although various actions are shown in a particular order, in some embodiments, the various actions may be performed in a different order. In still other embodiments, two or more actions may occur simultaneously. According to yet other embodiments, some of the actions may not be required, or other actions may be included. For clarity, the flowchart is described with respect to the various components of FIG. 1. However, it should be understood that according to one or more embodiments, the various actions may be taken by alternative components.

[0024] Flowchart 400 begins with block 402 where access to the app store is detected from a first user identifier. In some embodiments, app store access may be detected on a client device such as a user device or from a server, e.g., from the app store. The first user identifier may be associated with a user account identifier, a device identifier, etc. In some embodiments, access may be detected when the user directly links to an application information page for a particular application in the store, as a result of a search query in the store bringing up a list of applications in the app store, etc.

[0025] Flowchart 400 continues to block 404 where a presentation version of the first application is selected for the first user identifier. As described above, a particular presentation version may be randomly selected from a plurality of presentation versions or selected according to a set of rules. For example, a certain percentage of users may be determined to be presented with a certain process of a particular application. As another example, specific user characteristics can be tied to rules to provide a particular process to that user. In some embodiments, the processes provided to various users can be tracked within a data structure by the app store such that the same process is presented if another access to the same application by the same user and / or device is detected. Further, statistics can be collected and provided to developers by tracking the association of processes to user identifiers.

[0026] In block 406, based on the selected presentation version, a representation of the first application is displayed within the app store. The presentation version may be associated with a particular process and may include specific icons, descriptions, and / or media items presented within the application's information page. Thus, the view of an app information page for one user may be different from the view of an app information page for another user.

[0027] The flowchart, following block 408, describes how the selection of a first application is detected from the app store via a representation. The selection of an application may include, for example, downloading the application or requesting to share the application. In some embodiments, the selection may be made within an app information page about an app, from an interface that includes a list of apps along with a representation of the app (i.e., a search query result in which the app is presented within the query results page according to a specific visual representation of the processing associated with a particular user). In block 410, the application is downloaded. The application may be downloaded, for example, in response to the detection of a download request selection from within the app store. According to some embodiments, a download package containing a binary file is sent from the app store 100 to the requesting client device in response to the download request. Furthermore, according to one or more embodiments, the binary file may be the same for two users requesting to download the same app from different processing on the app information page for the app in the app store.

[0028] The flowchart ends at block 412, where the application is presented on the device according to the presented version. In some embodiments, the user experience with the app remains consistent from the view in the app store to the use of the app on the user's device. Thus, the variations of the app presented on the app information page in the app store are maintained for the user when the user launches the application on their local device. In some embodiments, specific processing of the app for a particular user is tracked by the app store 100, for example, in storage device 104, and the app store can communicate specific processing components that propagate throughout the app to the client device, such as icons, descriptions, color schemes, and media items.

[0029] According to several embodiments, a technology is provided for custom information pages for apps. Different app information pages may be provided to different users. According to several embodiments, the app store 100 may have the ability to generate and / or present multiple information pages for a single application. In some embodiments, a particular product page provided for a particular product may be selected according to some contextual information regarding the client device's request for the product page. For example, a particular medium or layout provided may be selected according to the characteristics of the request, such as the location where the request is received (on the internet and / or a physical location). In some embodiments, each of the custom app information pages may be associated with a unique URL such that the app information page reached from a first website link may be presented differently from a second app information page reached from a second website link. According to several embodiments, the first app information page and the second app information page may each include an option to download the app. The downloaded material may be the same as that from a download request from either the first app information page or the second app information page.

[0030] Figure 5 shows a flowchart illustrating a technology for providing custom app information pages to various users. The flowchart begins with two users, 502A and 502B, accessing an app information page in the app store 100 for an app called "Mountain Climber". According to one or more embodiments, each user can request access to a Mountain Climber information page with different contextual information. For example, the first user 502A can access the app store 100 from a first internet location, and the second user 502B can access the app store 100 from a second internet location. In some embodiments, the first user 502A can access the app store 100 from a different URL. For example, the first user 502A can click the URL of the first app information page 504 for the Mountain Climber app, and the second user 502B can click a different URL of the second app information page 506 for the same Mountain Climber app. Therefore, the app store 100 may be configured to manage multiple app information pages for a single app. Thus, a first user 502A can view a first presentation version 510A of the Mountain Climber app on a first device 508A, and a second user 502B can view a second presentation version 510B of the Mountain Climber app on a second device 508B. For example, Mountain Climber page A 504A may be a stored version of the first app information page 510A, and Mountain Climber page B 504B may be a stored version of the second app information page 510B. Thus, media items in the first presentation version 510A are different from media items presented in the second presentation version 510B. In some embodiments, the presentation versions may have different app preview presentations, screenshot presentations, text presentations, etc., within the app information page.

[0031] In particular, each of the first app information page 510A and the second app information page 510B may include user-selectable options for downloading the Mountain Climber app to a local device. For example, the first app information page 510A may include a download interface component 512A, and the second app information page 510B may include a download interface component 512B. According to one or more embodiments, when either the download interface component 512A or the download interface component 512B is selected, the Mountain Climber app is downloaded from the app store 100 as Mountain Climber Download 514. That is, according to one or more embodiments, each download selection of the variation of the app information page triggers the download of the same download package. Thus, as shown in 516, the first devices 508A and 508B can download and deploy the same app. Furthermore, in some embodiments, the launched app may appear identical on either device.

[0032] Figure 6 shows a flowchart illustrating a technique for providing multiple app information pages for a specific app in an app store, according to one or more embodiments. While various actions are shown in a specific order, in some embodiments, the various actions may be performed in a different order. Furthermore, in other embodiments, two or more actions may occur simultaneously. In other embodiments, some actions may be unnecessary, or other actions may be included. For clarity, the flowchart is described with respect to the various components of Figures 1 and 5.

[0033] Flowchart 600 begins in block 602, where a trigger event is detected on the first device to launch a user interface for an ap application in the app store 100. For example, the user interface may be an app information page about a specific app in the app store. The trigger event may be, for example, a user selecting a link to a URL that navigates to one of the presented versions of the app information page. As another example, the trigger event may include a search query whose results include a specific app.

[0034] Flowchart 600 continues to block 604, where one or more contextual parameters are identified in relation to the interaction. Contextual parameters may include, for example, that when a download request is received, the simultaneously presented content may be considered. As an example, returning to Figure 5, if a first user 502A navigates from a page about climbing in California to the app information page for the Mountain Climber app, a first presentation version 510A highlighting climbing in California is presented. In contrast, if a second user 502B navigates from a page about climbing in Texas to the app information page for the Mountain Climber app, a second presentation version 510B highlighting climbing in Texas is presented. Furthermore, in some embodiments, as shown in 606, each presentation version may be associated with a unique URL. The app store can identify a specific URL for a presentation version of the app information page. Then, in block 608, the presentation version of the information page is determined for a first application. The presentation version may be determined from among several versions of the app information page. For example, an app store may host a default app information page for a particular app, and / or one or more variations of that app information page.

[0035] The flowchart continues to block 610, where an information page for a first application is displayed by, for example, the app store 100, based on a determined presentation version. In some embodiments, the various presentation versions may include different variations of app preview presentation, screenshot presentation, text presentation, etc. In one or more embodiments, a particular presentation version may be accessed from the app store 100 and provided to a client device such as client device 107 or 109.

[0036] In block 612, a download request is received for the application via a presented version on a specific client device. For example, as described above, the app information page may include user interface components that, when selected, cause the app to be downloaded to the client device. Flowchart 600 ends in block 614, where the first application is made available for download in accordance with the download request. According to one or more embodiments, the download package may be the same regardless of the presented version on which the download request was received. Furthermore, the installed application may be consistent across user devices regardless of the presented version on which the download request was received.

[0037] Referring here to Figure 7, a simplified functional block diagram of an exemplary programmable electronic device 700 for providing access to an app store according to one embodiment is shown. The electronic device 700 may be, for example, a mobile phone, a personal media device, a portable camera, or a tablet, notebook, or desktop computer system. As shown, the electronic device 700 may include a processor 705, a display 710, a user interface 715, graphics hardware 720, device sensors 725 (e.g., proximity sensor / ambient light sensor, accelerometer, and / or gyroscope), a microphone 730, an audio codec 735, a speaker 740, a communication circuit 745, an image capture circuit or unit 750 (which may include, for example, multiple camera units / optical sensors having different characteristics, as well as a camera unit that is housed outside the device 700 but electronically communicates with the device), a video codec 755, memory 760, storage device 765, and a communication bus 770.

[0038] The processor 705 can execute instructions necessary to perform or control the operation of numerous functions performed by the device 700 (e.g., the generation and / or processing of DA according to the various embodiments described herein). The processor 705 can, for example, drive the display 710 and receive user input from the user interface 715. The user interface 715 can take various forms such as buttons, keypads, dials, click wheels, keyboards, display screens and / or touchscreens. The user interface 715 can, for example, be a conduit from which the user can view a captured video stream and / or which the user can indicate a specific image that they wish to capture or share (e.g., by clicking a physical or virtual button at the moment the desired image appears on the device's display screen).

[0039] In one embodiment, the display 710 can display a captured video stream while the processor 705 and / or graphics hardware 720 and / or image capture circuit simultaneously store the video stream (or individual image frames from the video stream) in memory 760 and / or storage device 765. The processor 705 may be a system-on-a-chip, for example, as found in mobile devices, and may include one or more dedicated graphics processing units (GPUs). The processor 705 may be based on a reduced instruction-set computer (RISC) or complex instruction-set computer (CISC) architecture, or any other preferred architecture, and may include one or more processing cores. The graphics hardware 720 may be dedicated computing hardware for processing graphics and / or for assisting the processor 705 in performing computational tasks. In one embodiment, the graphics hardware 720 may include one or more programmable graphics processing units (GPUs).

[0040] The image capture circuit 750 may include, for example, one or more camera units configured to capture images in accordance with this disclosure. The output from the image capture circuit 750 may be processed at least in part by a video codec(s) 755 and / or a processor 705 and / or graphics hardware 720, and / or a dedicated image processing unit incorporated within the circuit 750. Images thus captured may be stored in memory 760 and / or storage device 765. Memory 760 may include one or more different types of media used by the processor 705, graphics hardware 720 and image capture circuit 750 to perform the functions of the device. For example, memory 760 may include a memory cache, read-only memory (ROM), and / or random access memory (RAM). Storage device 765 may store media (e.g., audio files, image files, and video files), computer program instructions or software, preference information, device profile information, and any other suitable data. The storage device 765 may include one or more persistent storage media, including, for example, magnetic disks and tapes (fixed, floppy, and removable), optical media such as CD-ROMs and digital video discs (DVDs), and semiconductor memory devices such as electrically programmable read-on rememory (EPROMs) and electrically erasable programmable read-on rememory (EEPROMs). The memory 760 and storage device 765 can be used to hold computer program instructions or code organized into one or more modules and written in any desired computer programming language. For example, when executed by the processor 705, such computer program code can perform one or more of the methods described herein. The power supply 775 may include a rechargeable battery (e.g., a lithium-ion battery) or other electrical connection to a power supply, such as a mains power supply, used to manage and / or provide power to the electronic components and associated circuits of the electronic device 700.

[0041] The above description includes numerous specific details, such as particular configurations, characteristics, and processes, in order to provide a thorough understanding of the embodiments. In other examples, well-known processes and manufacturing techniques are not described in particular detail to avoid unnecessarily obscuring the embodiments. Throughout this specification, references to “one embodiment,” “another embodiment,” “other embodiments,” “several embodiments,” and their variations mean that the particular features, structures, or characteristics described in relation to that embodiment are included in at least one embodiment. Therefore, the appearance of the phrases “about one embodiment,” “about one embodiment,” “about another embodiment,” “in other embodiments,” “in several embodiments,” or their variations in various parts of this specification does not necessarily refer to the same embodiment. Furthermore, particular features, structures, configurations, or characteristics may be optionally combined in one or more embodiments.

[0042] In the following descriptions and claims, the terms “joined” and “connected” may be used together with their derivatives. It should be understood that these terms are not intended to be synonymous with one another. “Joined” is used herein to indicate that two or more elements or components, which may or may not be in direct physical or electrical contact with each other, work together or interact with each other. “Connected” is used to indicate the establishment of communication between two or more elements or components that are joined together.

[0043] Some parts of the above “Modes for Carrying Out the Invention” have been presented in terms of algorithms and symbolic representations of operations on data bits within computer memory. These descriptions and representations of algorithms are methods used by those skilled in the art to most effectively convey the essence of the work to others skilled in the art. An algorithm, as used herein, is also generally understood to be a self-consistent sequence of operations that produces a desired result. These operations require the physical manipulation of physical quantities. However, it should be kept in mind that all these and similar terms should be associated with appropriate physical quantities and are merely convenient labels applied to those quantities. Unless otherwise specifically stated, as will be evident from the above discussion, throughout this discussion, when terms such as those set forth in the following claims are used, it will be understood to refer to the operations and processes of a computer system or similar electronic computing system that manipulates data represented as physical (electronic) quantities in the registers or memory of a computer system to convert it into other data similarly represented as physical quantities in the computer system memory or registers, or other such information storage devices, transmission devices, or display devices.

[0044] Embodiments described herein may relate to apparatus for executing computer programs (e.g., operations described herein). Such computer programs may be stored in non-temporary computer-readable media. Machine-readable media include any means of storing information in a form readable by a machine (e.g., a computer). For example, machine-readable (e.g., computer-readable) media include machine-readable (e.g., computer)-readable storage media (e.g., read-only memory ("ROM"), random-access memory ("RAM"), magnetic disk storage media, optical storage media, flash memory devices).

[0045] While the above describes the operation or method in terms of several sequential operations, it should be recognized that some of the operations described can be performed in a different order. Furthermore, some operations can be performed in parallel rather than sequentially. The embodiments described herein are not described with reference to any particular programming language. It will be understood that various programming languages ​​may be used to carry out various embodiments of the disclosed subject matter. When utilizing various aspects of the embodiments described herein, it will be apparent to those skilled in the art that combinations, modifications, or variations of the above embodiments are possible to control the components of the processing system and to improve the power and performance of at least one of those components. Thus, it will be apparent that various changes may be made to them without departing from at least one broader spirit and scope of the disclosed concepts as expressed in the following claims. Accordingly, this specification and the drawings should be considered in an illustrative rather than restrictive sense.

[0046] In developing any practical implementation of one or more of the disclosed concepts (e.g., software and / or hardware development projects), numerous decisions must be made to achieve the developer's specific objectives (e.g., compliance with system-related and / or business-related constraints). These objectives may differ from implementation to implementation, and this variation may affect the practical implementation of one or more of the disclosed concepts described in the embodiments described herein. Such development efforts may be complex and time-consuming, but may be routine work for those skilled in the art in designing and / or implementing one or more of the inventive concepts described in the embodiments described herein.

[0047] As described above, one aspect of this technology is to improve the delivery of apps to users in app stores by collecting and using data available from various sources. This disclosure considers that in some cases, such collected data may include personal information data that uniquely identifies a particular person, or personal information data that can be used to contact a particular person or to locate them. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, addresses, data or records relating to a user's health or fitness level (e.g., vital signs measurements, medication information, exercise information), birth dates, or any other identifying or personal information.

[0048] This disclosure acknowledges that the use of such personal data in this technology may be in the user's best interest. For example, personal data can be used to determine the most useful version of an app information page for an app store user. Thus, by using such personal data, users can have more rational and meaningful control over their experience in app stores and apps hosted by app stores. Furthermore, other uses of personal data that benefit users are also intended by this disclosure.

[0049] This disclosure assumes that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal data will adhere to a robust privacy policy and / or privacy practice. Specifically, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for the strict confidentiality of personal data. Such policies should be readily accessible to users and should be updated as data collection and / or use changes. Personal data from users should be collected for the lawful and legitimate use of the entity and should not be shared or sold for any other purpose. Furthermore, such collection / sharing should be carried out only after informing and obtaining the user's consent. In addition, such entities should consider taking all necessary steps to protect and secure access to such personal data and to ensure that others with access to personal data faithfully adhere to those privacy policies and procedures. Furthermore, such entities may undergo third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal data collected and / or accessed, and should comply with applicable laws and standards, including jurisdiction-specific considerations.

[0050] Notwithstanding the foregoing, the Disclosure also envisions embodiments that allow users to selectively prevent the use of or access to personal data. Specifically, the Disclosure intends that hardware and / or software elements may be provided to prevent or prevent access to such personal data. For example, in the case of a personalized app information page, the technology may be configured to allow users to choose to “opt in” or “opt out” of participating in the collection of personal data during or at any time thereafter when registering for the service. In another example, a user may choose not to provide content and other personal data for an improved content sharing suggestion service. In yet another example, a user may choose to limit the length of time their personal data is maintained by third parties, limit the length of time in the past from which content sharing suggestions can be derived, and / or completely prohibit the development of a knowledge graph or other metadata profile. In addition to providing “opt-in” and “opt-out” options, the Disclosure intends to provide notices regarding access to or use of personal data. For example, a user may be notified when downloading an app that will access their personal data, and then again immediately before the app accesses their personal data.

[0051] Furthermore, the intent of this disclosure is that personal data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data when it is no longer needed. In addition, where applicable, including in certain health-related applications, data anonymization can be used to protect user privacy. De-identification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth), controlling the amount or specificity of data stored (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data across users), and / or by other means.

[0052] Therefore, while this disclosure broadly covers the use of personal data to implement one or more different disclosed embodiments, it is conceivable that the disclosure may also enable the implementation of those different embodiments without requiring access to such personal data. That is, the different embodiments of the technology are not rendered inoperable by the absence of all or part of such personal data. For example, content may be suggested to a user for sharing by inferring preferences based on non-personal data or a minimal amount of personal information, such as the quality level of the content (e.g., focus, exposure level), or the fact that certain content is requested by a device associated with the user's contacts, other non-personal information available in the app store, or publicly available information.

[0053] Where used in the above description and in the following claims, the phrases "at least one of A, B, or C" and "one or more of A, B, or C" include A alone, B alone, C alone, a combination of A and B, a combination of B and C, a combination of A and C, and a combination of A, B, and C. That is, the phrases "at least one of A, B, or C" and "one or more of A, B, or C" mean A, B, C, or any combination thereof, and therefore, one or more of the group of elements consisting of A, B, and C should not be interpreted as requiring at least one of each of the enumerated elements A, B, and C, regardless of whether A, B, and C are related as categories. Furthermore, the use of the article "a" or "the" when introducing elements should not be interpreted as excluding multiple elements. Also, the statement "A, B, and / or C" is equivalent to "at least one of A, B, or C." Also, the use of "a" in this disclosure refers to "one or more." For example, "a DA" refers to "one DA" or "a group of DAs".

Claims

1. A method performed by a system, The method involves detecting a first access to an app store by a client device, wherein the first access is associated with a first user identifier. Presenting a first representation of the app in the app store to be displayed on the screen of the client device, wherein the first representation of the app corresponds to a first presentation version of the app selected for the first user identifier from among a plurality of presentation versions associated with different visual appearances of the app's components. In response to detecting an input corresponding to the selection of the first expression of the aforementioned application, Selecting a first presentation version of the first application relating to the first user identifier, wherein the first application is associated with a plurality of presentation versions, The information page of the aforementioned application is displayed on the screen of the client device in the app store, wherein the information page is compatible with the first presented version of the application. Upon receiving a download request for the application from the client device, The download package for the aforementioned application is downloaded to the client device, wherein the download package includes data for each of the multiple presented versions. Includes, The application is configured, upon launch, to be presented using the first presentation version, in accordance with the fact that the application is launched in association with the first user identifier. method.

2. The method according to claim 1, wherein the first user identifier is at least one of a device identifier and a user account identifier.

3. The method according to claim 1, further comprising updating the viewing time metric associated with the first presented version in accordance with the detection of a selection of the first application for download from the app store.

4. The method according to claim 3, wherein the updated viewing time metric is provided in the user interface for presentation to the developer associated with the application.

5. The method according to claim 1, wherein access to the app store associated with a second user identifier causes the representation of the application in the app store to be presented according to a second presentation version among the plurality of presentation versions.

6. The method according to claim 5, wherein the download package associated with the first presented version is the same as the download package associated with the second presented version.

7. The method according to claim 6, wherein when the application is launched by the second user identifier, the application is presented according to the second presentation version.

8. In accordance with the detection of an updated default presentation version among the plurality of presentation versions, the application is made to present the representation. The method according to claim 1, further comprising:

9. The method according to claim 1, wherein the first presented version is selected using a randomized selection process.

10. The method according to claim 1, wherein the first presentation version is selected based on a predefined association between the user identifier and the first presentation version.

11. A non-temporary computer-readable medium containing computer-readable code, wherein the computer-readable code is The process involves detecting a first access to an app store by a client device, wherein the first access is associated with a first user identifier. To present a first representation of the app in the app store, which is to be displayed on the screen of the client device, wherein the first representation of the app corresponds to a first presentation version of the app selected for the first user identifier from among a plurality of presentation versions associated with different visual appearances of the app's components. In response to detecting an input corresponding to the selection of the first expression of the aforementioned application, Selecting a first presentation version of the first application with respect to the first user identifier, wherein the first application is associated with a plurality of presentation versions, The process involves displaying the information page of the aforementioned application on the screen of the client device in the app store, wherein the information page conforms to the first presented version of the aforementioned application. Upon receiving a download request for the application from the client device, The process involves downloading the aforementioned application download package to the client device, wherein the download package includes data for each of the multiple presented versions. Therefore, it is executable by one or more processors, The application is configured, upon launch, to be presented using the first presentation version, in accordance with the fact that the application is launched in association with the first user identifier. Non-temporary computer-readable media.

12. The non-temporary computer-readable medium according to claim 11, wherein the first user identifier is at least one of a device identifier and a user account identifier.

13. The non-temporary computer-readable medium according to claim 11, further comprising computer-readable code for updating the viewing time metric associated with the first presented version in accordance with the detection of the selection of the first application for download from the app store.

14. The updated viewing time metric is provided in a user interface for presentation to the developer associated with the application, according to claim 13, in a non-temporary computer-readable medium.

15. The non-temporary computer-readable medium according to claim 11, wherein access to the app store associated with a second user identifier causes a representation of the application within the app store to be presented according to a second presentation version of the plurality of presentation versions.

16. It is a system, One or more processors, A computer-readable medium comprising one or more computer-readable media containing computer-readable code, wherein the computer-readable code is The process involves detecting a first access to an app store by a client device, wherein the first access is associated with a first user identifier. To present a first representation of the app in the app store, which is to be displayed on the screen of the client device, wherein the first representation of the app corresponds to a first presentation version of the app selected for the first user identifier from among a plurality of presentation versions associated with different visual appearances of the app's components. In response to detecting an input corresponding to the selection of the first expression of the aforementioned application, Selecting a first presentation version of the first application with respect to the first user identifier, wherein the first application is associated with a plurality of presentation versions, The process involves displaying the information page of the aforementioned application on the screen of the client device in the app store, wherein the information page conforms to the first presented version of the aforementioned application. Upon receiving a download request for the application from the client device, The process involves downloading the aforementioned application download package to the client device, wherein the download package includes data for each of the multiple presented versions. Therefore, it is executable by one or more processors, The application is configured, upon launch, to be presented using the first presentation version, in accordance with the fact that the application is launched in association with the first user identifier. system.

17. The system according to claim 16, wherein access to the app store associated with a second user identifier results in the representation of the application within the app store being presented according to a second presentation version among the plurality of presentation versions.

18. The system according to claim 17, wherein the download package associated with the first presented version is the same as the download package associated with the second presented version.

19. The system according to claim 17, wherein when the application is launched by the second user identifier, the application is presented according to the second presentation version.

20. The system according to claim 16, further comprising a computer-readable code for causing the representation of the application to be presented in accordance with the detection of an updated default presentation version among the plurality of presentation versions.

Images