Customize your app store information page
By offering customizable app presentations in app stores based on user context, the system optimizes user engagement and app store performance through varied representations and consistent user experience.
Patent Information
- Application Number
- JP2024531176
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-12-06
- Filing Date
- 2022-12-06
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-12-06
AI Technical Summary
Existing app stores provide uniform representations of software applications, failing to account for user-specific contexts and preferences, which limits developers' ability to optimize app presentation and user engagement.
Implementing systems and methods to provide multiple variations of app presentations in app stores, selecting these variations based on contextual information and user interactions, ensuring consistent user experience across devices and after installation.
Enhances user engagement by allowing developers to test and optimize app representations, tracks user responses, and maintains consistent app experience from store to device, improving download and sharing rates.
Smart Images

Figure 2024543906000001_ABST
Abstract
Description
[Technical field]
[0001] FIELD OF THE DISCLOSURE
[0002] The embodiments described herein relate to presenting software applications. More particularly, the embodiments described herein relate to providing custom visual representations of software applications. [Background technology]
[0002] In recent years, downloading software applications (or "apps") from online app stores has become a common way to obtain software applications. Online app stores allow users to download software applications onto their devices, such as desktop or laptop computers, smartphones, or other mobile devices, and then install the apps on the user's devices. Before downloading an app, a user often finds the app in an 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 illustrated by way of example, and not by way of limitation, in the accompanying drawings, in which like references indicate like features, and in which some conventional details have been omitted so as not to obscure the inventive concepts described herein.
[0004] [Figure 1] 1 illustrates, in block diagram form, a network through which an app store is accessed by a client device, in accordance with one or more embodiments.
[0005] [Diagram 2] 1 illustrates an example of product page variations provided to different users in accordance with one or more embodiments.
[0006] [Diagram 3] 1 illustrates an example of app installation from different variations of a product page, according to one or more embodiments.
[0007] [Figure 4] 1 illustrates, in flowchart form, a technique for providing variations on a product page to different users, according to one or more embodiments.
[0008] [Diagram 5] 1 illustrates, in flow diagram form, a technique for providing a custom product page in an app store, in accordance with one or more embodiments.
[0009] [Figure 6] 1 illustrates, in flow chart form, a technique for providing a custom product page in an app store, according to one or more embodiments.
[0010] [Figure 7] 1 illustrates a simplified functional block diagram of an exemplary programmable electronic device, according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] The present disclosure relates to systems, methods, and computer-readable media for providing multiple variations of the presentation of an app in an app store, according to one or more embodiments. In particular, the embodiments described herein relate to techniques for providing multiple treatments of an app in an app store such that a subsequently downloaded app is presented in the app store consistent with the treatment from which the app was originally downloaded.
[0012] The present disclosure also relates to systems, methods, and computer-readable media for providing multiple variations of a presentation of an app in an app store, according to one or more embodiments. In particular, the embodiments described herein relate to techniques for providing custom variations to a product page for a particular app. In particular, 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] The embodiments described herein may operate within and interface with the environment and context of an app store, where one or more users may use client devices to search for and download one or more applications (also referred to as apps). App store 100 may include one or more servers, such as servers 101, 102, and 103, that may provide the functionality described herein. For example, server(s) 101 may interface with client devices to implement the methods of FIGS. 4 and 6 to generate and / or provide custom app information pages and / or customized app content for presentation on one or more client devices, such as client devices 107 and 109, which may take a variety of different forms (e.g., tablet computers such as iPads, smartphones such as iPhones, laptop computers, desktop computers, network media players such as Apple TVs, gaming / entertainment systems, or other consumer electronic devices). Client devices 107 and 109 can be coupled to app store 100 by one or more networks 105, such as the Internet, that provide data communication between the client devices and the app store such that the client devices can submit search queries to the app store, receive search results, submit requests to download one or more apps, and then receive downloads of one or more apps. Server(s) 101, in one embodiment, can create data structures used in providing custom app information pages and / or custom representations of apps to particular subsets of users (e.g., associating app representations with particular user or device identifiers) and can store those data structures in storage 104 for later use by server 102, which can be configured to receive search queries from client devices and then perform searches of the one or more data structures to provide a consistent view of representations of apps in the app store.
[0014] An app store, such as the app store shown in FIG. 1, can collect information about queries used to search for applications and about downloads resulting from user selections of apps shown in search results generated by the search queries. This information can be collected in a log maintained by the app store that records the queries used and the downloads resulting from those queries. In one embodiment, one or more servers 102 can maintain a record of queries used and selections made from search results for those queries during a user's search session, and can record this record in one or more logs. In one embodiment, in addition to tracking downloads resulting from specific search queries, the app store can track user selections for more information about specific applications without necessarily downloading the application. In another embodiment, the app store can only track downloads resulting from search results to limit the amount of information that may be relevant. In other words, downloads may be considered more relevant and more important information than a user selection for more information about an application that does 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, the client devices 107 and 109 may provide access to the app store 100 where multiple applications may be hosted. The app store 100 may provide a particular user with a particular treatment for an app information page in the app store for a particular app. That is, a view of the app information page from the client device 107 may differ from a view of the app information page from the client device 109. In some embodiments, the client devices 107 and 109 may obtain the same binary download package, and the app store 100 may send metadata indicating a particular treatment to use for the application such that the user experience remains consistent from the app information page presented to the user in the app store 100.
[0016] FIG. 2 shows an example diagram of the variation of a representation of an application as it is presented to different users. In some embodiments, an app developer may want to provide multiple representations of the app for download by different users. For example, the developer may want to provide different treatments for the application to different users. As a result, according to some embodiments, the developer can track which treatments in the app store attract more users. In some embodiments, the different treatments may be encoded into 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 manner that is consistent with the visual treatment with which the user obtained the app in the app store.
[0017] According to one or more embodiments, an app store may provide different users 200 with different treatments 202 and 204 of an app within the app store. For example, as shown in FIG. 2, if a first user searches for a game called "The Coast" within the app store, they may see an app information page 202 that includes a first icon 206 and description 208. In some embodiments, the treatments include multiple presentation versions of the app's information page. Thus, while treatment 202 is presented to some users of the app store, other users 200 may be provided with a second treatment 204. To illustrate, the app store information page of the second treatment 204 includes a second icon 220 and a second description 222 that differ from the icon 206 and description 208 provided in the first treatment of the app information page 202.
[0018] The multiple presentation versions may include a default presentation version and one or more updated variants. In some embodiments, the other information may be specific to a particular treatment, such as screenshots, media items (video content, graphic content, etc.). The treatments provided to a particular user may be randomly selected or predefined. Furthermore, in some embodiments, a predefined share of users 200 may be provided with a particular treatment, for example, based on traffic allocation. As an example, 80% of users 200 may see a default treatment and 20% of users 200 may see one of one or more additional variants of the app information page. For example, treatment 202 may be a default treatment provided to users in the app store, while treatment 204 is a new treatment that the developer wants to offer to a subset of users to test the appeal or response rate of treatment variations. Thus, a developer may offer multiple treatments of the same pp in the app store to different users. Furthermore, by doing so, the app store may track the response rates to the different treatments. For example, the app store may track download rates among users who landed on each of the variations of the app information page, the time spent on the app information page for each treatment, the share rate for each treatment, etc. As an example, a developer may be able to track that over a particular period of time, a first treatment 202 in the app store resulted in a 1.9% download rate of the app, while a second treatment 204 in the app store resulted in a 2.5% download rate of the app. For purposes of this disclosure, download rate refers to the percentage of views of a particular treatment 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 in the app information page in the app store.
[0019] As another example, a developer may track the share rate of an app to determine, for example, how "viral" a particular presentation version of the app in an app store becomes. For example, a user 200 presented with a first treatment of the app may "share" the app information page 202 at a rate of 0.5% over a particular period of time, and a user 200 presented with a second treatment of the app may "share" the app information page 204 at a rate of 1.2%. For purposes of this disclosure, the share rate refers to the percentage of views of a particular treatment of a presentation version of an app information page that resulted in a user sharing the app by sending a link to the app information page to another user, such as through a share icon 212 or 226 in the app information page in an app store. According to some embodiments, additional users who are recipients of the share may be directed to the same presentation version as the presentation version in which the information page was shared. For example, metadata may be embedded in the share link to indicate the particular presentation version. Alternatively, different presentation versions may be provided, either randomly or through a predefined set of rules. In some embodiments, the app store may provide developers with a user interface that presents information about performance regarding various treatments, such as download and share rates for various treatments. Additionally or alternatively, the user interface may include other statistics, such as referral traffic (e.g., visits to one or more variations of the information page from a shared or direct URL), confidence values that a particular treatment "performs" better (i.e., meets a predefined threshold performance rate based on download rates, share rates, referral traffic, etc.), an estimated lift rate indicating the predicted rate at which a particular treatment improves the performance of a default treatment, and / or one or more confidence values associated with the various predicted rates.
[0020] According to some embodiments, the user experience with the app should remain consistent from within the app store to the actual experience of the app once the app is downloaded and / or launched on the user device. Figure 3 shows an example flow diagram of how the presentation process remains consistent outside of the app store after the application is downloaded and / or launched.
[0021] In FIG. 3, a first user may be presented with a first action 302A of an app's information page, and a second user may be presented with a second action 302B of the same app's information page. As shown in the example of FIG. 3, the first action 302A presented on the first user device shows a first version 304A of an icon of a game called "The Coast," as well as a first version 306A of a description. At the same time, the second action 302B presented on the second user device shows a second version 304B of an icon of the same game, as well as a second version 306B of a description. According to some embodiments, downloading the game from either presented version downloads the same binary download package. For example, the download package associated with either app's information page may be the same as the various presentation elements embedded therein.
[0022] In some embodiments, a user experience with a 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 in the app information page 302A where the app was downloaded. Similarly, desktop 310B is presented with an icon 312B that maintains consistency with the icon 304B presented in the app information page 302B where the app was downloaded. For example, the same icon presented to a user to represent an app information page in an app store may be configured to be presented on the user's desktop upon download and installation of the app to the user device. Other app information may be presented consistently from the information pages in the app store and the installed application, such as screenshots, text, and other media.
[0023] FIG. 4 illustrates a flowchart of a technique for providing variations on a product page to different users, according to one or more embodiments. Although various actions are shown in a particular order, in some embodiments, various actions may be performed in a different order. In still other embodiments, two or more actions may occur simultaneously. According to still 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, various actions may be taken by alternative components.
[0024] Flowchart 400 begins at block 402, where access to an app store is detected from a first user identifier. In some embodiments, the app store access may be detected at a client device, such as a user device, or from a server, e.g., from an app store. The first user identifier may be associated with a user account identifier, a device identifier, etc. In some embodiments, the access may be detected when a user links directly to an application information page for a particular application in the store, as a result of a search query in the store resulting in a listing for the application in the app store, etc.
[0025] Flowchart 400 continues at block 404, where a representation version of a first application is selected for a first user identifier. As explained above, a particular presentation version may be selected randomly from among multiple presentation versions or may be selected according to a set of rules. For example, it may be determined that a certain percentage of users are presented with a certain operation of a particular application. As another example, characteristics of a particular user may be tied to rules to provide a particular operation to that user. In some embodiments, operations provided to various users may be tracked in a data structure by the app store such that the same operation is presented if another access to the same application by the same user and / or device is detected. Additionally, by tracking the association of operations to user identifiers, statistics may be collected and provided to developers.
[0026] At block 406, a representation of the first application is displayed within the app store based on the selected presentation version. The presentation version may be associated with a particular action and may include particular icons, descriptions, and / or media items that are presented within the information page of the application. Thus, a view of the app information page for one user may differ from a view of the app information page for another user.
[0027] The flowchart continues at block 408, where a selection of a first application is detected from the app store via a representation. The selection of the application may include, for example, a request to download the application, a request to share the application, etc. In some embodiments, the selection may be made within an app information page for the app from an interface that includes a list of multiple apps along with a representation of the apps (i.e., a search query result in which the apps are presented within a query result page according to a particular visual representation of the transaction associated with the particular user). At block 410, the application is downloaded. The application may be downloaded in response to, for example, detecting a selection of a download request from within the app store. According to some embodiments, a download package including a binary file is transmitted from the app store 100 to the requesting client device in response to the download request. Further, according to one or more embodiments, the binary file may be the same for two users requesting to download the same app from different transactions of 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 device. Thus, the variant of the app presented on the app information page in the app store is maintained for the user when the user launches the application on a local device. In some embodiments, the specific processing of the app for a particular user is tracked by the app store 100, for example in storage 104, and the app store can communicate to the client device the specific processing components that propagate throughout the app, such as icons, descriptions, color schemes, media items, etc.
[0029] According to some embodiments, techniques are provided for custom information pages for apps. Different app information pages may be provided to different users. According to some embodiments, the app store 100 may have the ability to generate and / or present multiple information pages for a single application. In some embodiments, the particular product page provided for a particular product may be selected according to some contextual information about a request for the product page by a client device. For example, the particular medium or layout provided may be selected according to characteristics of the request, such as the location (on the Internet and / or a physical location) from which the request is received. In some embodiments, each of the custom app information pages may be associated with a unique URL such that an app information page reached from a first website link may be presented differently than a second app information page reached from a second website link. According to some 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 from a download request from either the first app information page or the second app information page.
[0030] FIG. 5 illustrates in flow diagram form a technique for providing custom app information pages to various users. The flow diagram 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 of the users can request access to the Mountain Climber information page with different contextual information. For example, a first user 502A can access the app store 100 from a first Internet location and a 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 on a URL for a first app information page 504 of the Mountain Climber app and the second user 502B can click on a different URL for a second app information page 506 of the same Mountain Climber app. Thus, the app store 100 may be configured to manage multiple app information pages for a single app. Thus, a first user 502A may view a first presentation version 510A of the Mountain Climber app in a first device 508A, and a second user 502B may view a second presentation version 510B of the Mountain Climber app in 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, the media items in the first presentation version 510A are different from the 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. in the app information pages.
[0031] In particular, the first app information page 510A and the second app information page 510B may each include a user-selectable option 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, the download selection of each of the app information page variants causes the download of the same download package. Thus, as shown at 516, the first devices 508A and 508B may download and deploy the same app. Furthermore, in some embodiments, the launched app may look the same on either device.
[0032] 6 illustrates, in flowchart form, a technique for providing multiple app information pages for a particular app in an app store, according to one or more embodiments. Although various actions are shown in a particular order, in some embodiments, various actions may be performed in a different order. In still other embodiments, two or more actions may occur simultaneously. According to still other embodiments, some of the actions may not be required, or other actions may be included. For clarity, the flowchart will be described with reference to the various components of FIGS. 1 and 5.
[0033] Flowchart 600 begins at block 602, where a trigger event is detected at a first device to launch a user interface for an ap application in app store 100. For example, the user interface may be an app information page for a particular app in the app store. The trigger event may be, for example, a user may select a URL link 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 the particular app.
[0034] The flowchart 600 continues at block 604 where one or more context parameters are identified in association with the interaction. The context parameters may include, for example, that contemporaneously presented content may be considered when a download request is received. As an example, returning to FIG. 5, if a first user 502A navigates to an app information page for the Mountain Climber app from a page about climbing in California, a first presentation version 510A highlighting the climbing in California is presented. In contrast, if a second user 502B navigates to an app information page for the Mountain Climber app from a page about climbing in Texas, a second presentation version 510B highlighting the climbing in Texas is presented. Further, in some embodiments, as shown at 606, each presentation version may be associated with a unique URL. The app store may identify the particular URL of the presentation version of the app information page. Then, at block 608, a presentation version of the information page is determined for the first application. The presentation version may be determined from among multiple versions of the app information page. For example, an app store may host a default app information page for a particular app and / or may host one or more variants of an app information page for a particular app.
[0035] The flowchart continues at block 610, where an information page for the first application is displayed based on the determined presentation version, for example, by app store 100. In some embodiments, the various presentation versions may include different variations on the app preview presentation, screenshot presentation, text presentation, etc. In one or more embodiments, a particular presentation version may be accessed from app store 100 and provided to a client device, such as client device 107 or 109.
[0036] At block 612, a download request is received for the application via the presentation version at a particular client device. For example, as described above, the app information page may include a user interface component that, when selected, causes the app to be downloaded to the client device. Flowchart 600 ends at block 614 where the first application is offered for download according to the download request. According to one or more embodiments, the download package may be the same regardless of the presentation version for which the download request is received. Furthermore, the installed application may be consistent across user devices regardless of the presentation version for which the download request is received.
[0037] 7, a simplified functional block diagram of an exemplary programmable electronic device 700 for providing access to an app store is shown, according to one embodiment. The electronic device 700 can 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 can 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, communication circuitry 745, an image capture circuitry or unit 750, which may include, for example, multiple camera units / optical sensors with different characteristics (as well as a camera unit housed outside the device 700 but in electronic communication with the device), a video codec 755, a memory 760, a storage device 765, and a communication bus 770.
[0038] The processor 705 can execute instructions necessary to perform or control the operation of the numerous functions performed by the device 700 (e.g., generating and / or processing DA according to various embodiments described herein). The processor 705 can, for example, drive the display 710 and receive user input from a user interface 715. The user interface 715 can take a variety of forms, such as buttons, a keypad, a dial, a click wheel, a keyboard, a display screen, and / or a touch screen. The user interface 715 can, for example, be a conduit through which a user can view a captured video stream and / or can indicate a particular image that the user would like to capture or share (e.g., by clicking a physical or virtual button the moment the desired image appears on the device's display screen).
[0039] In one embodiment, display 710 can display the captured video stream while processor 705 and / or graphics hardware 720 and / or image capture circuitry simultaneously stores the video stream (or individual image frames from the video stream) in memory 760 and / or storage 765. Processor 705 may be a system-on-chip, such as found in mobile devices, and may include one or more dedicated graphics processing units (GPUs). Processor 705 may be based on reduced instruction-set computer (RISC) or complex instruction-set computer (CISC) architectures, or any other suitable architecture, and may include one or more processing cores. Graphics hardware 720 can be dedicated computing hardware for processing graphics and / or for assisting processor 705 in performing computational tasks. In one embodiment, graphics hardware 720 may include one or more programmable graphics processing units (GPUs).
[0040] Image capture circuitry 750 may comprise one or more camera units configured to capture images, for example, in accordance with the present disclosure. Output from image capture circuitry 750 may be processed, at least in part, by video codec(s) 755 and / or processor 705 and / or graphics hardware 720, and / or a dedicated image processing unit incorporated within circuitry 750. Images so captured may be stored in memory 760 and / or storage 765. Memory 760 may include one or more different types of media used by processor 705, graphics hardware 720, and image capture circuitry 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 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 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 disks (DVDs), and semiconductor memory devices such as Electrically Programmable Read-Only Memory (EPROM) and Electrically Erasable Programmable Read-Only Memory (EEPROM). The memory 760 and storage 765 may 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, such computer program code when executed by the processor 705 may perform one or more of the methods described herein. The power source 775 may comprise a rechargeable battery (e.g., a lithium ion battery, etc.) or other electrical connection to a power source, e.g., a mains power source, used to manage and / or provide power to the electronic components and associated circuitry of the electronic device 700.
[0041] In the above description, numerous specific details are set forth, such as specific configurations, features, and processes, to provide a thorough understanding of the embodiments. In other instances, well-known processes and manufacturing techniques have not been described in particular detail to avoid unnecessarily obscuring the embodiments. Throughout this specification, references to "one embodiment," "one embodiment," "another embodiment," "other embodiments," "some embodiments," and variations thereof mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearance of the phrases "for one embodiment," "for one embodiment," "for another embodiment," "in other embodiments," "in some embodiments," or variations thereof in various places throughout this specification do not necessarily refer to the same embodiment. Furthermore, particular features, structures, features, or characteristics may be combined in any suitable manner in one or more embodiments.
[0042] In the following description and claims, the terms "coupled" and "connected" may be used, along with their derivatives. It should be understood that these terms are not intended as synonyms for each other. "Coupled" 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, co-operate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements or components that are coupled to each other.
[0043] Some portions of the above Detailed Description have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations require physical manipulations of physical quantities. It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, as will be apparent from the above discussion, throughout the description, discussion utilizing such terms as set forth in the claims below will be understood to refer to operations and processes of a computer system or similar electronic computing system that manipulates and converts data represented as physical (electronic) quantities in the computer system's registers or memory to other data similarly represented as physical quantities in the computer system's memory or registers, or other such information storage, transmission, or display device.
[0044] The embodiments described herein may relate to an apparatus for executing a computer program (e.g., operations described herein, etc.). Such a computer program may be stored on a non-transitory computer-readable medium. A machine-readable medium includes any scheme for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., computer) readable storage medium (e.g., read-only memory ("ROM"), random access memory ("RAM"), magnetic disk storage media, optical storage media, flash memory devices).
[0045] Although the operations or methods described above are described in terms of several sequential operations, it should be appreciated that some of the operations described can be performed in different orders. 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 appreciated that a variety of programming languages may be used to implement various embodiments of the disclosed subject matter. It will be apparent to those skilled in the art that combinations, modifications, or variations of the above embodiments are possible when utilizing various aspects of the embodiments described herein to manage components of a processing system to improve the power and performance of at least one of those components. It will thus be apparent that various changes may be made thereto without departing from the broader spirit and scope of at least one of the disclosed concepts as set forth in the following claims. Accordingly, the specification and drawings are to be considered in an illustrative and not restrictive sense.
[0046] In developing any actual implementation of one or more of the disclosed concepts (e.g., a software and / or hardware development project, etc.), numerous decisions must be made to achieve the developer's particular goals (e.g., adherence to system-related and / or business-related constraints). These goals may vary from implementation to implementation, and this variation may affect the actual implementation of one or more of the disclosed concepts described in the embodiments described herein. While such a development effort may be complex and time-consuming, it may be a routine undertaking for one of ordinary skill in the art in the design and / or implementation of one or more of the inventive concepts described in the embodiments described herein.
[0047] As mentioned above, one aspect of the present technology is to collect and use data available from various sources to improve the delivery of apps in an app store to users. This disclosure contemplates that in some cases, this collected data may include personal information data that uniquely identifies a particular person or that can be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, addresses, data or records regarding a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth date, or any other identifying or personal information.
[0048] This disclosure recognizes that such uses of personal information data in the present technology may be used to the benefit of users. For example, personal information data may be used to determine the most useful version of an app information page for an app store user. Thus, the use of such personal information data allows users to have more streamlined and meaningful control over their experience with the app store and apps hosted by the app store. Additionally, other uses of personal information data that benefit users are also contemplated by this disclosure.
[0049] This disclosure contemplates that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will adhere to robust privacy policies and / or privacy practices. 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 keeping personal information data confidential and secure. Such policies should be easily accessible by users and should be updated as data collection and / or use changes. Personal information from users should be collected for the entity's lawful and legitimate use and should not be shared or sold except for those lawful uses. Furthermore, such collection / sharing should be carried out after informing and obtaining consent from the user. Moreover, such entities should consider taking all necessary measures to protect and secure access to such personal information data and ensure that others who have access to the personal information data adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to attest to their adherence to widely accepted privacy policies and practices. Moreover, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and should comply with applicable laws and standards, including jurisdiction-specific considerations.
[0050] Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which a user selectively blocks use of or access to personal information data. That is, the present disclosure contemplates that hardware and / or software elements may be provided to prevent or block access to such personal information data. For example, in the case of a personalized app information page, the present technology may be configured to allow a user to select to "opt-in" or "opt-out" of participating in the collection of personal information data during registration for the service or at any time thereafter. In another example, a user may choose not to provide content and other personal information data for an improved content sharing suggestion service. In yet another example, a user may choose to limit the amount of time their personal information data is maintained by third parties, limit the amount of time in the past from which content sharing suggestions may be drawn, 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 present disclosure contemplates providing notifications regarding access or use of personal information. For example, a user may be notified upon download of an app that will access the user's personal information data, and then again immediately before the personal information data is accessed by the app.
[0051] Moreover, it is the intent of this disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintended or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data when it is no longer needed. Additionally, anonymization of data can be used to protect user privacy where applicable, including in certain health-related applications. De-identification can be facilitated by removing certain identifiers (e.g., date of birth, etc.) where appropriate, controlling the amount or specificity of data stored (e.g., collecting location data at a city level rather than an address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods.
[0052] Thus, while this disclosure broadly encompasses the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure also contemplates that the various embodiments may be implemented without requiring access to such personal information data. That is, the various embodiments of the technology are not rendered inoperable by the absence of all or a portion of such personal information data. For example, content may be suggested to a user for sharing by inferring preferences based on non-personal information data or a minimal amount of personal information, such as the quality level of the content (e.g., focus, exposure level, etc.) or the fact that a piece of content is requested by a device associated with the user's contacts, other non-personal information available in an app store, or publicly available information.
[0053] As used in the above description and in the claims that follow, 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, the combination of A and B, the combination of B and C, the combination of A and C, and the 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 thus one or more of the group of elements A, B, and C should not be construed as requiring at least one of each of the listed elements A, B, and C, regardless of whether A, B, and C are categorically related. Furthermore, the use of the article "a" or "the" in introducing an element should not be construed as excluding a plurality of 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" refers to "one or more" in this disclosure. For example, "a DA" refers to "one DA" or "a group of DAs."
Claims
1. 1. A method comprising: Detecting a first access to an app store, the first access being associated with a first user identifier; selecting a first presentation version of a first application for the first user identifier, the first application being associated with multiple presentation versions; causing the app store to display a representation of the first application in accordance with the selected first representation; Detecting a selection of the first application for download from the app store; downloading the first application; When the application is launched, the application is presented according to the first presentation version.
2. The method of claim 1 , wherein the first user identifier is at least one of a device identifier and a user account identifier.
3. 3. The method of claim 1 or 2, further comprising updating a watch time metric associated with the first presentation version in accordance with detecting a selection of the first application for download from the app store.
4. The method of claim 3 , wherein the updated watch time metrics are provided in a user interface for presentation to a developer associated with the application.
5. 5. The method of 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 of the plurality of presentation versions.
6. The method of claim 5 , wherein a download package associated with the first presentation version is the same as a download package associated with the second presentation version.
7. The method of claim 6 , wherein upon launching the application with the second user identifier, the application is presented according to the second presentation version.
8. presenting the representation of the application in accordance with detecting an updated default presentation version among the plurality of presentation versions. The method of claim 1 , further comprising:
9. The method of claim 1 , wherein the first presentation version is selected using a randomized selection process.
10. The method of 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-transitory computer readable medium comprising computer readable code, the computer readable code comprising: Detecting a first access to an app store, the first access being associated with a first user identifier; Selecting a first presentation version of a first application for the first user identifier, the first application being associated with multiple presentation versions; causing a representation of the first application to be displayed in the app store in accordance with the selected first representation; Detecting a selection of the first application for download from the app store; executable by one or more processors to cause the first application to be downloaded; A non-transitory computer-readable medium, wherein upon launching the application, the application is presented according to the first presentation version.
12. The non-transitory computer-readable medium of claim 11 , wherein the first user identifier is at least one of a device identifier and a user account identifier.
13. 13. The non-transitory computer-readable medium of claim 11 or 12, further comprising computer-readable code for updating a watch time metric associated with the first presentation version in accordance with detecting a selection of the first application for download from the app store.
14. 14. The non-transitory computer-readable medium of claim 13, wherein the updated watch time metrics are provided in a user interface for presentation to a developer associated with the application.
15. 15. The non-transitory computer-readable medium of claim 11, wherein access to the app store associated with a second user identifier causes a representation of the application in the app store to be presented according to a second presentation version of the plurality of presentation versions.
16. 16. The non-transitory computer-readable medium of claim 15, wherein a download package associated with the first presentation version is the same as a download package associated with the second presentation version.
17. 17. The non-transitory computer-readable medium of claim 16, wherein launching the application with the second user identifier causes the application to be presented according to the second presentation version.
18. 18. The non-transitory computer-readable medium of claim 11, further comprising computer readable code for causing the representation of the application to be presented according to detection of an updated default presentation version among the plurality of presentation versions.
19. 19. The non-transitory computer-readable medium of claim 11, wherein the first presentation version is selected using a randomized selection process.
20. 19. The non-transitory computer-readable medium of claim 11, wherein the first presentation version is selected based on a predefined association between the user identifier and the first presentation version.
21. 1. A system comprising: one or more processors; and one or more computer readable media containing computer readable code, the computer readable code comprising: Detecting a first access to an app store, the first access being associated with a first user identifier; Selecting a first presentation version of a first application for the first user identifier, the first application being associated with multiple presentation versions; causing a representation of the first application to be displayed in the app store in accordance with the selected first representation; Detecting a selection of the first application for download from the app store; a first application executable by the one or more processors to download the first application; When the application is launched, the application is presented according to the first presentation version.
22. 22. The system of claim 21, wherein the first user identifier is at least one of a device identifier and a user account identifier.
23. 23. The system of claim 21 or 22, further comprising computer readable code for updating watch time metrics associated with the first presentation version in accordance with detecting a selection of the first application for download from the app store.
24. 24. The system of claim 23, wherein the updated watch time metrics are provided in a user interface for presentation to a developer associated with the application.
25. 25. The system of claim 21, 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 of the plurality of presentation versions.
26. 26. The system of claim 25, wherein a download package associated with the first presentation version is the same as a download package associated with the second presentation version.
27. 27. The system of claim 26, wherein launching the application with the second user identifier causes the application to be presented according to the second presentation version.
28. 28. The system of claim 21, further comprising computer readable code for causing the representation of the application to be presented according to detection of an updated default presentation version of the plurality of presentation versions.
29. 29. The system of any one of claims 21 to 28, wherein the first presentation version is selected using a randomized selection process.
30. 19. The non-transitory computer-readable medium of claim 11, wherein the first presentation version is selected based on a predefined association between the user identifier and the first presentation version.
31. 1. A method comprising: Detecting a first user interaction with a first device, the first user interaction being a trigger event for launching a user interface for a first application in an app store; identifying one or more first context parameters associated with the user interaction; a first presentation version of an information page for the first application according to the one or more first context parameters, causing a first presentation version of an information page to be presented at the first device, the first presentation version of the information page being selected from a plurality of presentation versions for the first application; receiving a download request for the first application from the first presentation version of the information page; providing the first application for download to the first device in accordance with the download request.
32. Detecting a second user interaction with a second device, the second user interaction being a second trigger event for launching an information page about the first application in the app store; identifying one or more second context parameters associated with the second user interaction; causing a second presentation version of the information page for the first application to be presented at the second device according to the one or more second context parameters; 32. The method of claim 31 further comprising:
33. 33. The method of claim 32, wherein the first presentation version and the second presentation version comprise at least one different variant selected from the group consisting of an app preview presentation, a screenshot presentation, and a text presentation.
34. receiving, by the second device, a request to download the first application from the second presentation version of the information page; providing the first application for download to the second device in accordance with the download request; 33. The method of claim 32, further comprising:
35. 35. The method of claim 34, wherein the download package associated with the first download request is the same as the download package associated with the second download request.
36. 36. The method of claim 31, wherein the first context information comprises presentation content at the first device when the first user interaction is detected.
37. 36. The method of claim 31, wherein the first contextual information includes a first URL of a plurality of URLs each associated with one of the plurality of presentation versions.
38. 38. The method of claim 37, wherein the first triggering event comprises a selection of the first URL.
39. A non-transitory computer readable medium comprising computer readable code, the computer readable code comprising: Detecting a first user interaction with a first device, the first user interaction being a trigger event for launching a user interface for a first application in an app store; Identifying one or more first context parameters associated with the user interaction; a first presentation version of an information page for the first application according to the one or more first context parameters, causing a first presentation version of an information page to be presented at the first device, the first presentation version of the information page being selected from a plurality of presentation versions for the first application; receiving a download request for the first application from the first presentation version of the information page; A non-transitory computer-readable medium executable by one or more processors to provide the first application for download to the first device in accordance with the download request.
40. detecting a second user interaction with a second device, the second user interaction being a second trigger event for launching an information page about the first application in the app store; identifying one or more second context parameters associated with the second user interaction; causing a second presentation version of the information page for the first application to be presented at the second device according to the one or more second context parameters.
40. The non-transitory computer readable medium of claim 39, further comprising computer readable code for:
41. 41. The non-transitory computer-readable medium of claim 40, wherein the first presentation version and the second presentation version include at least one different variant selected from the group consisting of an app preview presentation, a screenshot presentation, and a text presentation.
42. receiving, by the second device, a request to download the first application from the second presentation version of the information page; providing the first application for download to the second device in accordance with the download request; 41. The non-transitory computer readable medium of claim 40, further comprising computer readable code for:
43. 43. The non-transitory computer-readable medium of claim 42, wherein a download package associated with the first download request is the same as a download package associated with the second download request.
44. 44. The non-transitory computer-readable medium of claim 41, wherein the first contextual information comprises presentation content at the first device when the first user interaction is detected.
45. 44. The non-transitory computer-readable medium of claim 41, wherein the first contextual information includes a first URL of a plurality of URLs each associated with one of the plurality of presentation versions.
46. 46. The non-transitory computer-readable medium of claim 45, wherein the first trigger event comprises a selection of the first URL.
47. 1. A system comprising: one or more processors; and one or more computer readable media containing computer readable code, the computer readable code comprising: Detecting a first user interaction with a first device, the first user interaction being a trigger event for launching a user interface for a first application in an app store; Identifying one or more first context parameters associated with the user interaction; a first presentation version of an information page for the first application according to the one or more first context parameters, causing a first presentation version of an information page to be presented at the first device, the first presentation version of the information page being selected from a plurality of presentation versions for the first application; receiving a download request for the first application from the first presentation version of the information page; A system executable by one or more processors to provide the first application for download to the first device in accordance with the download request.
48. detecting a second user interaction with a second device, the second user interaction being a second trigger event for launching an information page about the first application in the app store; identifying one or more second context parameters associated with the second user interaction; causing a second presentation version of the information page for the first application to be presented at the second device according to the one or more second context parameters.
48. The system of claim 47, further comprising computer readable code for:
49. 49. The system of claim 48, wherein the first presentation version and the second presentation version comprise at least one different variant selected from the group consisting of an app preview presentation, a screenshot presentation, and a text presentation.
50. receiving, by the second device, a request to download the first application from the second presentation version of the information page; providing the first application for download to the second device in accordance with the download request; 49. The system of claim 48, further comprising computer readable code for:
51. 51. The system of claim 50, wherein the download package associated with the first download request is the same as the download package associated with the second download request.
52. 52. The system of claim 47, wherein the first context information comprises presentation content at the first device when the first user interaction is detected.
53. 52. The system of any one of claims 47 to 51, wherein the first contextual information includes a first URL of a plurality of URLs each associated with one of the plurality of presentation versions.
54. 54. The system of claim 53, wherein the first trigger event comprises a selection of the first URL.
Citation Information
Patent Citations
Application download servicing method, application provision servicing method, and user terminal to which the same is applied
JP2011044147A
Evaluation support system and program
JP2015036919A
Analysis device, analysis method, and program
JP2018156472A
Personal mobile internet
US20030174683A1
Bundled mobile / desktop application package
US8832681B1
