A system, method, and user interface for organizing wish lists in online marketplaces.

Abstract

A method is provided for organizing a wishlist on an online marketplace. The method includes displaying category affordances corresponding to properties available on the online marketplace on a wishlist management graphical user interface. The method includes displaying property cards in response to detection of user input for selecting a category affordance. Each property card corresponds to a property in the category corresponding to the category affordance. The method also includes displaying wishlist icons. Each wishlist icon corresponds to its respective property card. The method includes generating a wishlist for the category and associating the property corresponding to the wishlist icon with the wishlist for the category in response to detection of a wishlist icon selection. The method includes displaying one or more properties in the wishlist in response to detection of the user selecting an option to view the wishlist.

Description

Technical Field

[0001] Related Applications This application claims priority to U.S. Provisional Application No. 63 / 499,648, filed May 2, 2023, entitled “Systems, Methods and User Interfaces for Organizing Wish Lists in Online Marketplaces,” which is hereby incorporated by reference in its entirety.

[0002] Technical Field This application generally relates to dedicated machines for managing interfaces and data processing, as well as improvements to such variations, and techniques for improving such dedicated machines compared to other dedicated machines for online marketplaces.

Background Art

[0003] Background Web or cloud-based systems can assist users in performing various tasks, and a common one is an e-commerce website that enables users to purchase, rent, or reserve products and / or services. Typically, customer users of such sites use the website as a tool to facilitate transactions and perform such tasks (e.g., purchase, rental) themselves. Before a user rents a property, the user may perform various searches. Narrowing down the search can be a cumbersome process that may involve multiple searches and different modalities. In this process, the user needs to track their progress and compile the search results.

Summary of the Invention

Problems to be Solved by the Invention

[0004] Summary Therefore, there is a general demand for technological solutions for more personalized, dynamic, accurate, and timely management of wish lists in online marketplaces. [Means for solving the problem]

[0005] The disclosed implementation provides a method for organizing a wishlist in an online marketplace. The method includes retrieving a wishlist for a user. The wishlist includes one or more properties. The method also includes displaying one or more property cards on a wishlist management graphical user interface. Each property card corresponds to one or more properties in the wishlist. The method also includes displaying one or more note-adding affordances on the wishlist management graphical user interface for adding notes to one or more properties. Each note-adding affordance is associated with its respective property. The method also includes displaying a first note-adding overlay on the wishlist management graphical user interface in response to detecting a first input from the user for selecting a first note-adding affordance from one or more affordances, for adding a first note to a first property from one or more properties. The method also includes associating a first text with a first property in response to detecting a second user input in the first note-adding overlay for entering a first text on the wishlist management graphical user interface. The method also includes stopping the display of the first note-adding overlay and resuming the display of one or more property cards and one or more note-adding affordances. The method also includes displaying the first text on the wishlist management graphical user interface along with the first property card from among the one or more property cards. The first property card corresponds to the first property.

[0006] Some embodiments allow a user to update a note. The method further includes displaying a second note-adding overlay for adding a second note to a first property in response to detecting a third input from the user for selecting a first note-adding affordance on the wishlist management graphical user interface. The method also includes associating the second text with the first property in response to detecting a fourth user input in the second note-adding overlay for entering the second text on the wishlist management graphical user interface. The method also includes stopping the display of the second note-adding overlay and resuming the display of one or more property cards and one or more note-adding affordances. The method also includes displaying the second text in place of the first text along with a first property card among one or more property cards on the wishlist management graphical user interface, where the first property card corresponds to the first property.

[0007] Some embodiments allow a user to sort cards and / or property listings in a wishlist based on notes. In some embodiments, the method further includes sorting one or more property cards based on notes corresponding to each of the one or more properties in order to obtain a sorted list of one or more property cards. The method also includes displaying one or more property cards on a wishlist management graphical user interface according to the sorted list of property cards.

[0008] In some embodiments, each of the one or more additional note affordances is shown adjacent to the respective property card of the property corresponding to each additional note affordance.

[0009] Some embodiments allow users to share wishlists and / or notes. In some embodiments, the method further includes providing sharing affordances on a wishlist management graphical user interface. The method also includes, in response to a user selecting a sharing affordance, (i) displaying a wishlist sharing overlay on the wishlist management graphical user interface for the user to select a sharing option for sharing the wishlist, and (ii) on the wishlist management graphical user interface, in response to the user selecting a sharing option, associating one or more other users of an online marketplace to share the wishlist, and / or displaying the wishlist for one or more other users. In some embodiments, associating one or more other users of an online marketplace is done in response to a user, via the wishlist management graphical user interface, (i) providing information relating to one or more other users, and / or (ii) selecting a mechanism for sharing the wishlist with one or more other users.

[0010] In some embodiments, a map is displayed alongside the wishlist. In some embodiments, the method further includes dividing the wishlist management graphical user interface into multiple areas. The method also includes displaying one or more property cards in a first area of ​​the wishlist management graphical user interface. The method also includes displaying a map in a second area of ​​the wishlist management graphical user interface. The method also includes displaying multiple icons on the map, each icon corresponding to one or more properties. Each icon is displayed approximately at the geographical location on the map corresponding to each property. In some embodiments, the first and second areas are displayed simultaneously and adjacent to each other. In some embodiments, the first and second areas are displayed simultaneously, with the first area displayed above the second area. In some embodiments, the first and second areas have different areas. In some embodiments, the first and second areas have similar areas. In some embodiments, the map corresponds to geographical regions corresponding to the locations of one or more properties in the wishlist. In some embodiments, the method further includes displaying a subset of one or more property cards in a first area, containing fewer property cards than all of one or more property cards. The method also includes displaying a portion of a map smaller than the entire map in a second area, based on the area of ​​the second area. In some embodiments, the method further includes selecting a portion of the map to indicate the locations corresponding to a subset of properties corresponding to a subset of one or more property cards. In some embodiments, the method further includes selecting a subset of one or more property cards based on the relative importance of the properties to the user. In some embodiments, the sum of the areas of the multiple areas corresponds to the screen size of the device used by the user.

[0011] Some embodiments enable filtering a wishlist based on a date selected by the user and / or displaying thumbnail images for properties available during the selected date. Some embodiments provide a method for organizing a wishlist on an online marketplace. The method includes retrieving a wishlist for a user, the wishlist containing one or more properties. The method also includes displaying one or more property cards on a wishlist management graphical user interface, each property card corresponding to a property from one or more properties in the wishlist. The method also includes displaying filter options on the wishlist management graphical user interface for filtering the wishlist based on a date. The method also includes displaying a calendar overlay on the wishlist management graphical user interface showing a calendar with date affordances for selecting a date, in response to detecting a first input from the user for selecting a filter option. The method also includes displaying thumbnail images in an area of ​​the calendar overlay corresponding to properties available during the selected date, from one or more properties, in response to the user selecting a date affordance for selecting a date, while maintaining the display of the calendar overlay on the wishlist management graphical user interface before confirming the date from the user.

[0012] In some embodiments, the thumbnail image is shown below the calendar. In some embodiments, the area is shown below the calendar.

[0013] Some embodiments filter the date after it has been selected by the user. In some embodiments, the method further includes stopping the display of the calendar overlay after receiving confirmation of the date from the user, and displaying only the properties available during the selected date from one or more properties on the wishlist management graphical user interface.

[0014] In some embodiments, the thumbnail image is updated in real time. In some embodiments, the thumbnail image is updated in real time in response to a change in date.

[0015] In some embodiments, the wishlist displays unavailable properties after available properties. In some embodiments, the method further includes stopping the display of a calendar overlay and sorting and displaying, on the wishlist management graphical user interface, the properties available during the selected date from one or more properties, followed by other properties that are unavailable during the selected date from one or more properties.

[0016] Some embodiments indicate the number of available properties. In some embodiments, the method further includes displaying the number of available properties for a selected date in a region adjacent to the thumbnail image.

[0017] Some embodiments allow a user to select an exact date and / or a date with a tolerance (e.g., ±1, ±2, etc.) for a wish list. In some embodiments, the method further includes displaying one or more affordances in a region for selecting an exact date or a date with a tolerance.

[0018] In some embodiments, the method further includes updating a region with an updated set of thumbnail images corresponding to an updated set of properties available during the tolerant date among one or more properties, in response to the user selecting an affordance corresponding to a tolerant date.

[0019] Some embodiments allow users to save properties to a known wishlist. According to some embodiments, a method is provided for organizing a wishlist on an online marketplace. The method includes displaying one or more category affordances on a wishlist management graphical user interface, each category affordance corresponding to each of one or more categories of properties available on the online marketplace. The method also includes displaying one or more first property cards on the wishlist management graphical user interface in response to detecting a first input from the user to select a first category affordance from one or more category affordances. Each property card in the first one or more property cards corresponds to each of one or more first properties for a first category corresponding to the first category affordance. The method also includes displaying one or more first wishlist icons on the wishlist management graphical user interface, each wishlist icon corresponding to each of the first one or more property cards. The method also includes, in response to detecting a user selection of a first wishlist icon from one or more first wishlist icons on the wishlist management graphical user interface, generating a first wishlist for a first category and associating the first property corresponding to the first wishlist icon with the first wishlist for the first category. The method also includes displaying an option on the wishlist management graphical user interface for viewing user-created wishlists.The method also includes displaying a set of wishlist affordances on the wishlist management graphical user interface in response to detecting that the user has selected an option to view lists, with each wishlist affordance corresponding to a specific wishlist created by the user. The method also includes displaying a first property card on the wishlist management graphical user interface corresponding to a first property associated with a first wishlist in response to detecting that the user has selected a first wishlist affordance corresponding to a first wishlist.

[0020] Some embodiments allow a user to switch wishlists. In some embodiments, the method includes displaying a second set of one or more property cards on the wishlist management graphical user interface in response to detecting a second input from the user for selecting a second category affordance from one or more category affordances, where each property card corresponds to each property from the second set of one or more properties for the second category corresponding to the second category affordance. The method also includes displaying a second set of one or more icons on the wishlist management graphical user interface, where each icon corresponds to each property card from the second set of one or more property cards. The method also includes associating a third property corresponding to a third icon with the second category in the second wishlist in response to detecting that the user has selected a third icon from the second set of one or more icons on the wishlist management graphical user interface. The method also includes, in response to detecting that the user has selected a fourth icon from one or more second icons on the wishlist management graphical user interface, associating the fourth item corresponding to the fourth icon with the second wishlist for the first category. The method also includes, in response to detecting that the user has selected an option to browse the list on the wishlist management graphical user interface, displaying a set of wishlist availability including the first and second wishlists.

[0021] Some embodiments enable a user to add to a wish list for a category. In some embodiments, the method further includes associating a second property corresponding to the second icon with a first wish list for a first category in response to detecting that the user has selected the second icon out of the first one or more wish list icons on a wish list management graphical user interface.

[0022] In another aspect, an electronic device includes one or more processors, memory, a display, and one or more programs stored in the memory. The programs are configured for execution by the one or more processors and configured to perform any of the methods described herein.

[0023] In another aspect, a non-transitory computer-readable storage medium stores one or more programs configured for execution by a computing device having one or more processors, memory, and a display. The one or more programs are configured to perform any of the methods described herein.

[0024] Brief Description of the Drawings To better understand the various described implementations, reference should be made to the following detailed description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the drawings.

Brief Description of the Drawings

[0025] [Figure 1] FIG. 1 is a block diagram showing an exemplary wish list management system implemented in a network environment according to some embodiments. [Figure 2] FIG. 2 is a block diagram showing the software architecture used to implement a wish list management system according to some embodiments. [Figure 3]A diagram showing a machine as an exemplary computer system having instructions to implement a wish list management system on the machine, according to some embodiments. [Figure 4] A diagram showing an exemplary user interface for viewing and / or managing a wish list of a property, according to some embodiments. [Figure 5A] A diagram showing an exemplary user interface for viewing and / or managing a wish list of a property for adding notes to the wish list, according to some embodiments. [Figure 5B] A diagram showing another view of the exemplary user interface shown in FIG. 5A, according to some embodiments. [Figure 6A] A diagram showing an exemplary user interface for adding notes to a property in a wish list, according to some embodiments. [Figure 6B] A diagram showing another view of the exemplary user interface shown in FIG. 6A after the user has started typing text to add a note to a property listing, according to some embodiments. [Figure 6C] A diagram showing another view of the exemplary user interface shown in FIG. 6A after the user has selected a different image or view for a property listing, according to some embodiments. [Figure 6D] A diagram showing another view of the exemplary user interface shown in FIG. 6A after the user has selected a different image or view for a property listing, according to some embodiments. [Figure 6E] A diagram showing another view of the exemplary user interface shown in FIG. 6A after the user has saved a note for a property listing in the wish list, according to some embodiments. [Figure 6F] A diagram showing another view of the exemplary user interface shown in FIG. 6A for a property listing in the wish list, according to some embodiments. [Figure 6G] This figure shows another view of the exemplary user interface shown in Figure 6A for property listings in a wishlist, according to several embodiments. [Figure 6H] This figure shows another exemplary view of the user interface shown in Figure 6A, after the user has saved additional notes to a property listing in their wishlist, according to several embodiments. [Figure 6I] This figure shows another view of the exemplary user interface shown in Figure 6A, after the user has entered additional text for notes regarding a property listing in their wishlist, according to several embodiments. [Figure 7A] This figure shows exemplary user interfaces for sharing wish lists, according to several embodiments. [Figure 7B] This figure shows another view of the exemplary user interface shown in Figure 7A, after the user has chosen to share a link to their wishlist, according to several embodiments. [Figure 8A] This figure shows exemplary user interfaces for selecting dates for items in a wishlist and / or filtering items in a wishlist by date, according to several embodiments. [Figure 8B] This figure shows another view of the exemplary user interface shown in Figure 8A, after the user has selected a different start date according to several embodiments. [Figure 8C] This figure shows another view of the exemplary user interface shown in Figure 8A for flexible date settings, according to several embodiments. [Figure 8D] This figure shows another view of the exemplary user interface shown in Figure 8A, after the user has selected a different date, according to several embodiments. [Figure 8E] This figure shows another view of the exemplary user interface shown in Figure 8A, after the user has selected a date for the wish list, according to several embodiments. [Figure 8F] This figure shows another exemplary view of the user interface shown in Figure 8A, illustrating unavailable items in the wishlist according to several embodiments. [Figure 9A] This figure shows an exemplary user interface for easy saving to a wishlist, according to several embodiments. [Figure 9B] This figure shows another view of the exemplary user interface shown in Figure 9A, illustrating properties in the luxury home category according to several embodiments. [Figure 9C] This figure shows another view of the exemplary user interface shown in Figure 9A, after the user has chosen to browse the wishlist, according to several embodiments. [Figure 9D] This figure shows another view of the exemplary user interface shown in Figure 9A, after the user has chosen to create a new wish list, according to several embodiments. [Figure 9E] This figure shows another view of the exemplary user interface shown in Figure 9A, after the user has chosen to browse the wishlist, according to several embodiments. [Figure 9F] This figure shows another view of the exemplary user interface shown in Figure 9A, after the user has chosen to browse the wishlist, according to several embodiments. [Figure 9G] This figure shows another view of the exemplary user interface shown in Figure 9A, after the user has selected a different category, according to several embodiments. [Figure 9H] This figure shows another view of the exemplary user interface shown in Figure 9A, after the user has selected an affordance to add a property to their wish list, according to several embodiments. [Figure 9I] This figure shows another view of the exemplary user interface shown in Figure 9A, in several embodiments, when a user selects a category. [Figure 10]This is a flowchart illustrating a method for organizing a wish list on an online marketplace, based on several embodiments. [Figure 11] This is a flowchart illustrating a method for organizing a wish list on an online marketplace, based on several embodiments. [Figure 12A] This is a flowchart illustrating a method for organizing a wish list on an online marketplace, based on several embodiments. [Figure 12B] This is a flowchart illustrating a method for organizing a wish list on an online marketplace, based on several embodiments. [Modes for carrying out the invention]

[0026] Detailed explanation Herein, the implementation configurations are referred to in detail, with examples shown in the attached drawings. The following detailed description includes numerous specific details to provide a complete understanding of the various described implementation configurations. However, it will be apparent to those skilled in the art that the various described implementation configurations can be carried out without these specific details. In other examples, well-known methods, procedures, components, circuits, and networks are not described in detail so as not to unnecessarily obscure the aspects of the implementation configurations.

[0027] As will be apparent to those skilled in the art, many modifications and variations of this disclosure can be made without departing from the spirit and scope of this disclosure. The specific implementations described herein are provided for illustrative purposes only, and this disclosure should be limited only by the terms of the appended claims, together with the entire scope of equivalents to which such claims are entitled.

[0028] Figure 1 shows a block diagram of a network architecture 100 for an optimized search system according to several embodiments. Figure 1 shows, for example, a web client 112 (e.g., a browser), a client application 114, and a programmatic client 116 running on a client device 130. The client device 130 includes the web client 112, the client application 114, and the programmatic client 116 individually, together, or in any appropriate combination. Although Figure 1 shows one client device 130, in some embodiments the network architecture 100 comprises multiple client devices.

[0029] In some embodiments, the client device 130 comprises a computing device that includes at least a display and a communication function that provides access to a networked system 102 via a network 104. The client device 130 includes, but is not limited to, remote devices, workstations, computers, general-purpose computers, internet appliances, handheld devices, wireless devices, portable devices, wearable computers, cellular phones or mobile phones, personal digital assistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops, desktops, multiprocessor systems, microprocessor-based or programmable home electronic devices, game consoles, set-top boxes (STBs), network personal computers (PCs), minicomputers, and the like. In some embodiments, the client device 130 comprises one or more of the following: a touchscreen, an accelerometer, a gyroscope, a biometric sensor, a camera, a microphone, a Global Positioning System (GPS) device, and the like.

[0030] The client device 130 communicates with network 104 via a wired or wireless connection. For example, one or more parts of network 104 may include an ad-hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a WAN, a wireless WAN (WWAN), a metropolitan area network (MAN), part of the internet, part of a public switched telephone network (PSTN), a mobile phone network, a wireless network, a Wireless Fidelity (Wi-Fi®) network, a Worldwide Interoperability for Microwave Access (WiMAX) network, another type of network, or any appropriate combination thereof.

[0031] In some embodiments, the client device 130 includes one or more applications ("apps") from among those managed by other end users (e.g., posting end users who own a house and rent out an entire house or room) such as a web browser, a book reader app (capable of operating to read ebooks), a media app (capable of operating to present various media formats including audio and video), a health app, a biometric monitoring app, a messaging app, an email app, an e-commerce site app (also called a "marketplace app"), and a booking application for temporary stays at hotels, motels, or residences managed by other end users (e.g., posting end users who own a house and rent out an entire house or room). In some embodiments, the client application 114 includes various components capable of presenting information to the user and communicating with the networked system 102. In some embodiments, if the e-commerce site app is included in the client device 130, this app is configured to provide a user interface and at least some functionality locally, along with applications configured to communicate with the networked system 102 as needed for data or processing capabilities not available locally (e.g., access to a database of goods for sale, user authentication, verification of payment methods). Conversely, if the client device 130 does not include an e-commerce site application, the client device 130 can use its web browser to access an e-commerce site (or a variation thereof) hosted on the networked system 102.

[0032] The web client 112 accesses various systems of the networked system 102 via a web interface supported by the web server 122. Similarly, the programmatic client 116 and client application 114 access various services and functions provided by the networked system 102 via a programmatic interface provided by the Application Program Interface (API) server 120.

[0033] A user (e.g., user 106) includes a person, machine, or other means that interacts with the client device 130. In some embodiments, user 106 interacts with the network architecture 100 not as part of the network architecture 100 itself, but through the client device 130 or other means. For example, user 106 provides input (e.g., touchscreen input or alphanumeric input) to the client device 130, and the input is communicated to a networked system 102 via the network 104. In this case, the networked system 102, in response to receiving input from user 106, communicates information to the client device 130 via the network 104 and presents it to user 106. In this way, user 106 can interact with the networked system 102 using the client device 130.

[0034] The API server 120 and web server 122 are coupled to one or more application servers 140, providing programmatic and web interfaces, respectively. The application server 140 is configured to manage wishlists in response to input from client devices 130. Client devices 130 may be used by users of the online marketplace. Wishlists may include properties listed on the online marketplace. A wishlist may also be a collection of data stored in a database containing listings of one or more unique identifiers associated with products and / or services offered for sale on the online marketplace. A wishlist may include properties selected by the user for prioritization purposes. For example, a user planning a short trip, vacation, or holiday may go through a prioritization or final selection process before selecting properties for purchase and / or rental. In this process, the user may create several wishlists, add notes, and share these notes and / or wishlists with other users. Wishlists may be organized based on categories or attributes of properties listed on the online marketplace. When a user selects a property, it may be automatically added to a wishlist corresponding to the property's current focus or category. When the focus shifts, the property selected by the user may be automatically saved to a new wishlist corresponding to the new category or attribute.

[0035] The application server 140 includes a wishlist management module 150 for organizing wishlists for users on an online marketplace. The application server 140 also includes a visualization module 142 for generating and / or displaying visualizations in a graphical user interface. Property listings, wishlists, property categories or attributes, visualizations, associated parameters, and / or user preferences may be stored as part of the wishlist management module 150 and / or the visualization module 142. These modules may comprise one or more modules or applications, each which can be embodied as hardware, software, firmware, or any combination thereof, to facilitate the optimization of search results for the client device 130. The application server 140 is then shown to be coupled with one or more database servers 124 to facilitate access to one or more information storage repositories or databases 126. In some embodiments, the database 126 is a storage device that stores information posted to the visualization module 142 and / or the wishlist management module 150 (e.g., inventory, image data, catalog data, feature vectors). Database 126 also stores digital product information according to several embodiments. The wishlist management module 150 can manage, store and / or retrieve wishlists, property listings, notes on properties, user preferences, usage history data, property categories and / or attributes (e.g., location, name, rating), and property availability.The visualization module 142 may manage, store, and / or retrieve user interface properties (e.g., mobile phones have different screen sizes, dimensions, and / or form factors compared to desktops) and / or parameters, property cards, and process user input received via the graphical user interface, overlays on properties, icons, and / or affordances, images and / or thumbnail images, maps, and / or user preferences, online marketplace user preferences, and usage history data for visualization and display. The operation of the module is described below with reference to Figures 4 to 12B, according to one or more embodiments.

[0036] The network architecture 100 shown in Figure 1 uses a client-server architecture, but the subject matter of the present invention is, of course, not limited to such architectures and can be equally implemented in, for example, distributed or peer-to-peer architecture systems. Various components of the application server 140 (e.g., the visualization module 142 and / or the wishlist management module 150) may also be implemented as standalone software programs that do not necessarily have networking capabilities.

[0037] Although the modules are shown in Figure 1 as components of the networked system 102, it will be understood that in alternative embodiments, each may be a component of a separate web service distinct from the networked system 102. The visualization module 142 and / or the wishlist management module 150 may each be hosted on dedicated or shared server machines that are communicatively coupled to enable communication between server machines. The components themselves are communicatively coupled (e.g., via appropriate interfaces) to each other and to various data sources to enable the passing of information between applications or to enable applications to share and access common data. The components also access one or more databases 126 via the database server 124.

[0038] Figure 2 is a block diagram 200 showing the architecture of software 202 which can be installed on any one or more of the devices described above. Figure 2 is only a non-limiting example of the software architecture, and it will be understood that many other architectures can be implemented to facilitate the functions described herein. In various embodiments, software 202 is implemented by hardware such as machine 300 (further described in Figure 3), which includes a processor 310, memory 330, and input / output (I / O) components 350. In this exemplary architecture, software 202 can be conceptualized as a stack of layers, each of which may provide a specific function. For example, software 202 includes layers such as an operating system 204, a library 206, a framework 208, and an application 210. Operationally, application 210, consistent with some embodiments, invokes API calls 212 through the software stack and receives messages 214 in response to API calls 212.

[0039] In various implementations, the operating system 204 manages hardware resources and provides common services. The operating system 204 includes, for example, a kernel 220, services 222, and drivers 224. The kernel 120, consistent with several embodiments, functions as an abstraction layer between the hardware layer and other software layers. For example, the kernel 220 provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functions. Services 222 can provide other common services to other software layers. According to several embodiments, the drivers 224 are responsible for controlling or interfaced with the underlying hardware. For example, the drivers 224 may include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and the like.

[0040] In some embodiments, library 206 provides a low-level common infrastructure used by application 210. Library 206 may include a system library 230 (e.g., the C standard library) that can provide functions such as memory allocation, string manipulation, and mathematical functions. Furthermore, Library 206 may include API libraries 232 such as a media library (e.g., a library that supports the presentation and manipulation of various media formats such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codecs, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)); a graphics library (e.g., the OpenGL framework used for rendering graphic content on a display in two dimensions (2D) and three dimensions (3D)); a database library (e.g., SQLite for providing various relational database functions); and a web library (e.g., WebKit for providing web browsing functions). Library 206 can also include a wide variety of other libraries 234 to provide many other APIs to application 210.

[0041] According to some embodiments, the framework 208 provides a high-level common infrastructure that can be utilized by the application 210. For example, the framework 208 provides various graphical user interface (GUI) functions, high-level resource management, high-level location services, and so on. The framework 208 can also provide a wide range of other APIs that can be utilized by the application 210, some of which may be specific to a particular operating system or platform.

[0042] In some embodiments, application 210 includes a wide range of other applications such as a home application 250, a contacts application 252, a browser application 254, a book reader application 256, a location application 258, a media application 260, a messaging application 262, a game application 264, and / or a third-party application 266. According to some embodiments, application 210 is a program that performs programmatically defined functions. Using various programming languages, one or more of applications 210 can be created that are structured in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C or assembly language). In specific examples, a third-party application 266 (e.g., an application developed by an entity other than the vendor of a particular platform using an ANDROID® or IOS® software development kit (SDK)) may be mobile software that runs on a mobile operating system such as IOS®, ANDROID®, WINDOWS® Phone, or another mobile operating system. In this example, the third-party application 266 can invoke API calls 212 provided by the operating system 204 to facilitate the functionality described herein.

[0043] Figure 3 shows a schematic diagram of machine 300 in the form of a computer system in which a set of instructions for causing the machine to perform any one or more of the methods discussed herein may be executed in several embodiments. Specifically, Figure 3 shows a schematic diagram of machine 300 in an exemplary form of a computer system in which instructions 316 (e.g., software, programs, applications, applets, apps, or other executable code) for causing machine 300 to perform any one or more of the methodologies described herein may be executed. Instructions 316 transform a general, unprogrammed machine 300 into a specific machine 300 programmed to perform the functions described and illustrated in the manner described. In alternative embodiments, machine 300 may operate as a standalone device or be coupled to other machines (e.g., networked). In a networked deployment, machine 300 may operate as a server machine or client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 300 may include, but is not limited to, a server computer, a client computer, a PC, a tablet computer, a laptop computer, a netbook, an STB, a PDA, an entertainment media system, a mobile phone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), a smart home device (e.g., a smart appliance), another smart device, a web appliance, a network router, a network switch, a network bridge, or any other machine capable of sequentially or otherwise executing instructions 316 that specify the actions to be performed by Machine 300. Furthermore, although only a single Machine 300 is shown, the term “machine” should also be interpreted to include a set of Machines 300 that individually or collectively execute instructions 316 to perform any one or more of the methodologies described herein.

[0044] Machine 300 may include a processor 310, memory 330, and I / O components 350, which may be configured to communicate with each other via a bus 302 or the like. In some embodiments, the processor 310 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an ASIC, a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processors 312 and 314 capable of executing instruction 316. The term “processor” is intended to include multicore processors that may have two or more independent processors (sometimes called “cores”) capable of executing instructions simultaneously. Although Figure 3 shows multiple processors 310, machine 300 may include a single processor having a single core, a single processor having multiple cores (e.g., a multi-core processor), multiple processors having single cores, multiple processors having multiple cores, or any combination thereof.

[0045] Memory 330 may include main memory 332, static memory 334, and storage unit 336, all of which are accessible to the processor 310 via a bus 302 or the like. Main memory 332, static memory 334, and storage unit 336 store instructions 316 that embody any one or more of the methodologies or functions described herein. Instructions 316 may also reside, all or in part, in main memory 332, static memory 334, storage unit 336, at least one of the processor 310 (e.g., in the processor's cache memory), or any suitable combination thereof during their execution by machine 300.

[0046] The I / O component 350 may include a wide variety of components for receiving inputs, providing outputs, generating outputs, transmitting information, exchanging information, capturing measurements, and so on. The specific I / O component 350 included in a particular machine depends on the type of machine. For example, a portable machine such as a mobile phone is likely to include a touch input device or other such input mechanism, while a headless server machine is unlikely to include such a touch input device. It will be understood that the I / O component 350 may include many other components not shown in Figure 3. The I / O component 350 is grouped according to function simply to simplify the following description, and the grouping is by no means limiting. In various embodiments, the I / O component 350 may include an output component 352 and an input component 354. The output component 352 may include visual components (e.g., displays such as plasma display panels (PDPs), light-emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistors), and other signal generators. The input component 354 may include alphanumeric input components (e.g., keyboards, touchscreens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing devices), tactile input components (e.g., physical buttons, touchscreens that provide the position and / or force of touch or touch gestures, or other tactile input components), and audio input components (e.g., microphones).

[0047] In some embodiments, the I / O component 350 may include, among various other components, a biometric component 356, a motion component 358, an environmental component 360, or a positioning component 362. For example, the biometric component 356 may include components for performing facial expression detection (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measurement of biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or electroencephalography), and person identification (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalography-based recognition). Biometric data collected by the biometric component is taken up and stored only with the user's consent and deleted upon the user's request. Furthermore, such biometric data may be used for limited purposes such as identity verification. To ensure the limited and authorized use of biometric information and other personally identifiable information (PII), access to this data is restricted to authorized personnel only, if any. The use of biometric data may be strictly limited to identification and verification purposes, and the data will not be shared or sold to any third party without the user's explicit consent. Furthermore, appropriate technical and organizational measures will be implemented to ensure the security and confidentiality of this sensitive information. The motion component 358 may include acceleration sensor components (e.g., accelerometers), gravity sensor components, rotation sensor components (e.g., gyroscopes), and the like.The environmental component 360 may include, for example, an illuminance sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers for detecting ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones for detecting background noise), a proximity sensor component (e.g., an infrared sensor for detecting nearby objects), a gas sensor (e.g., a gas detection sensor for detecting the concentration of harmful gases for safety or for measuring airborne pollutants), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment. The positioning component 362 may include, for example, a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer for detecting air pressure from which altitude can be derived), a compass sensor component (e.g., a magnetometer), and the like.

[0048] Communication can be implemented using a wide variety of technologies. The I / O component 350 may include a communication component 364 capable of operating to connect machine 300 to network 380 or device 370 via couplings 382 and 372, respectively. For example, the communication component 364 may include a network interface component or another suitable device for interface with network 380. In further examples, the communication component 364 may include a wired communication component, a wireless communication component, a cellular communication component, a Near Field Communication (NFC) component, a Bluetooth® component (e.g., Bluetooth® Low Energy), a Wi-Fi® component, and other communication components for providing communication via other modalities. Device 370 may be another machine or a wide variety of peripheral devices (e.g., peripheral devices coupled via USB).

[0049] Furthermore, the communication component 364 may detect identifiers or include components capable of operating to detect identifiers. For example, the communication component 364 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, Quick Response (QR) codes, Aztec codes, Data Matrix, Data Glyphs, MaxiCode, PDF417, Ultra Code, UCCRSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying tagged audio signals). In addition, various types of information may be derived via the communication component 364, such as location via Internet Protocol (IP) geolocation information, location via Wi-Fi® signal triangulation, and location via detection of NFC beacon signals that can indicate a specific location.

[0050] Various memories (i.e., 330, 332, 334, and / or the memory of processor 310) and / or storage unit 336 may store one or more sets of instructions and data structures (e.g., software) that embody or utilize one or more of the methods or functions described herein. When these instructions (e.g., instruction 316) are executed by processor 310, they trigger a variety of actions for carrying out the disclosed embodiments.

[0051] As used herein, the terms “machine storage medium,” “device storage medium,” and “computer storage medium” mean the same thing and may be used interchangeably in this disclosure. These terms refer to one or more storage devices and / or media (e.g., centralized or distributed databases, and / or associated caches and servers) that store executable instructions and / or data. Thus, these terms should be interpreted to include, but are not limited to, solid-state memory, as well as optical and magnetic media, including memory inside or outside a processor. Specific examples of machine storage medium, computer storage medium, and / or device storage medium include non-volatile memory, such as semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGAs, and flash memory devices, as well as magnetic disks, such as internal hard disks and removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The terms “machine storage medium,” “computer storage medium,” and “device storage medium” specifically exclude carrier waves, modulated data signals, and other such mediums, at least some of which are included in the term “signaling medium,” as described below.

[0052] In various embodiments, one or more parts of network 380 may be an ad-hoc network, intranet, extranet, VPN, LAN, WLAN, WAN, WWAN, MAN, Internet, part of the Internet, part of the PSTN, plain old telephone service (POTS) network, mobile phone network, wireless network, Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, network 380 or part of network 380 may include a wireless or cellular network, and coupling 382 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM®) connection, or another type of cellular or wireless coupling.In this example, Coupling 382 includes Single Carrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, the third-generation partnership project (3GPP®), including 3G, fourth-generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), and Long-Term Evolution (LTE). Any of the various types of data transfer technologies may be implemented, such as the Evolution standard, other standards defined by various standards-setting organizations, other long-distance protocols, or other data transfer technologies.

[0053] Instruction 316 may be transmitted or received over network 380 using a transmission medium via a network interface device (e.g., a network interface component included in communication component 364) and utilizing one of several well-known transfer protocols (e.g., the hypertext transfer protocol (HTTP)). Similarly, instruction 316 may be transmitted or received to device 370 using a transmission medium via coupling 372 (e.g., peer-to-peer coupling). The terms “transmission medium” and “signaling medium” mean the same thing and may be used interchangeably in this disclosure. The terms “transmission medium” and “signaling medium” should be interpreted as including any intangible medium capable of storing, encoding, or carrying instruction 316 for execution by machine 300, including digital or analog communication signals or other intangible mediums to facilitate communication of such software. Accordingly, the terms “transmission medium” and “signaling medium” shall include any form of modulated data signal, carrier wave, etc. The term “modulated data signal” means a signal having one or more of its properties set or modified to encode information in the signal.

[0054] The terms “machine-readable medium,” “computer-readable medium,” and “device-readable medium” mean the same thing and may be used interchangeably in this disclosure. These terms are defined to include both machine storage media and transmission media. Therefore, these terms include both storage devices / mediums and carrier / modulated data signals.

[0055] Figure 4 shows exemplary user interfaces 400 (e.g., a mobile application user interface, a web browser user interface) for viewing and / or managing property wish lists in several embodiments. In this example, the user is shown a preview of property wish lists in an online marketplace. This example shows previews of wish lists including a wish list 402 for a trip to LA, a wish list 404 for Seattle, Washington, USA, a wish list 406 for Yosemite National Park, California, USA, a wish list 408 for Los Angeles, a wish list 410 for HI (Hawaii), a wish list 412 for Puglia, Italy, a wish list 414 for Rome, Italy in 2023, a wish list 416 for Chemuil, Mexico, and a wish list 418 for Washington, USA.

[0056] A wishlist may be created during a previous use of the online marketplace. A user may use the online marketplace over several sessions and / or using different modalities. For example, a user may use the website on their mobile phone in the morning and create a wishlist during that session. Later, in another session, the user may continue the prioritization process using the website on their desktop. During subsequent sessions, the user may continue adding to and / or updating the wishlist. The wishlist management module 150 may include session management for handling sessions and / or device management for handling input from different types of devices. The visualization module 142 may generate types of wishlist visualizations depending on which device the user is using and / or user preferences, other users' preferences, and / or usage history information.

[0057] Various users may create such wish lists. For example, a couple planning a short trip may initially create separate wish lists of their trip destinations, exchange initial lists, and then collaborate during the subsequent prioritization of their destinations. Wish lists may be merged when exchanged, and / or different copies may be stored by the wish list management module 150 with appropriate annotations (e.g., wish list 1 was created by the current user, wish list 2 was received from another user, and wish list 3 was merged with another wish list). Furthermore, wish lists may be created at different time zones, and / or between different devices and / or modalities. The wish list management module 150 may automatically adjust the wish lists (e.g., date, time zone, device identifier) ​​according to the origin of the wish lists and the history of the wish lists. Recently created wish lists may be displayed in the interface as previews. After a user creates a different wish list, the more recent wish list may be prioritized and displayed to the user as a preview. Some wishlists may be previewed (for example, properties, property images, and / or property cards from some wishlists may be shown), while others may be hidden. Wishlists do not have to be limited to geographical location or area, and / or multiple wishlists may be created for the same area. For example, wishlists may be based on property attributes or characteristics such as size, number of bedrooms, accessibility, cost, and similar factors. A user may create several wishlists for a given area. Wishlists may be similarly named, and property previews (e.g., thumbnail images) may help distinguish properties within a wishlist even if the wishlists are similarly named.

[0058] The order of wishlists displayed in the interface may be determined based on a variety of factors, including user preferences, user behavior (e.g., interactions with online marketplaces), and / or the preferences of other similar users. This example also shows that each wishlist may be previewed using a collage of images of the items in the wishlist. For each collage, the system may use a variety of methods for selecting images, including thumbnail images, enlarged views, and / or cropped views. In this example, a main image is shown along with two other images. For example, wishlist 402 for a trip to LA is previewed using a main image 420 along with two smaller images 422 and 424. The main image is larger than the other two images. Various other configurations are possible, including different numbers of images for wishlist previews and / or different image configurations for different wishlists.

[0059] Figure 5A shows exemplary user interfaces 500 (e.g., mobile application user interface, web browser user interface) for viewing and / or managing a wishlist of properties, for adding notes to the wishlist, according to several embodiments. This example shows a wishlist for a trip to LA. When a user selects a wishlist (e.g., the wishlist shown in the example above with reference to Figure 4), the graphical user interface updates to show a list of property cards for the properties in the wishlist. In this example, four property cards 502, 504, 506, and 508 for the wishlist are previewed. Each property card may include an image or thumbnail of the property view and / or information about the property (e.g., name, notes, cost). Views may be selected based on various factors, including the appeal of the view, user preferences, other users' preferences, and / or usage history. Due to the limited screen size or form factor of the device (e.g., mobile devices may have a smaller screen area compared to desktop applications), only a subset of properties in the wishlist may be previewed. The number of properties previewed may be based on a variety of factors, including user preferences, other users' preferences, usage history, and / or data recency. An overview and / or various features of each property listing may be shown as part of each property card. For example, preview 502 includes title 518 ("Los Angeles Residential"), number of beds 516 ("2 beds"), cost 520 ("$249"), total cost 522 ("Total $2,206"), and rating 526. A subset or superset of these features may be shown on each property card. In addition, a different number of features may be shown or highlighted on each property card. The total cost may be based on selected dates for the wishlist. Users may select and / or adjust dates for the wishlist using affordance 512. Users may also add guests to the wishlist using another affordance 514.

[0060] Each property card may also include an affordance for adding notes to the property. For example, Figure 5 shows an affordance 524 for adding notes. If notes have been previously added by the user, such notes may be displayed and / or previewed on each property card. Some embodiments display a map (e.g., map 510) along with a preview of the properties. The map may be selected based on the area or location of properties in the wishlist. The map may use pins to indicate the approximate location of all or a subset of properties in the wishlist (e.g., properties previewed in another area 528 of the user interface). In the example shown, properties in the LA excursion wishlist are indicated by marker 530. The marker may include cost information and / or an icon to indicate that the property is part of the wishlist.

[0061] Figure 5B shows another view of the exemplary user interface 500 according to several embodiments. Area 528 is updated after the user scrolls down the wish list. New property cards (e.g., property cards 532, 534, 536, and 538) may be displayed. Map 510 may also be updated accordingly. For example, the map may be adjusted to show the property on the new property card.

[0062] Figure 6A shows exemplary user interfaces 600 (e.g., mobile application user interface, web browser user interface) for adding notes to a wishlist property, according to several embodiments. After the user selects an affordance (e.g., affordance 524 in Figure 5A) to add a note to a property in the wishlist, a wishlist popup (e.g., overlap popup 602 in Figure 6A) may be displayed. The popup allows the user to add a note to the property. The popup may provide noteworthy information about the property, along with a text box (e.g., box 604) for entering the note (e.g., information shown on the property card for the property may be shown enlarged). Some embodiments allow a maximum number of characters (or words) (e.g., 250 characters) for the note to the property. Area 606 within the popup may display a thumbnail image of the property view.

[0063] Figure 6B shows another view of the exemplary user interface 600 after the user has begun typing text to add a note to a property listing, according to several embodiments. In this example, the user types "Boho interior" into text box 604. Some embodiments update the character count 608 (e.g., 12 / 250 characters) to indicate the amount of text entered by the user and how close they are to the limit.

[0064] Figure 6C shows another view of the exemplary user interface 600 after the user has selected different images or views for a property listing, according to several embodiments. In some embodiments, the user can interact with the images (for example, by selecting other images or views of the property to preview in area 606). The user may view different views of the property while adding notes to the property to characterize the selections for notes.

[0065] Figure 6D shows another view of the exemplary user interface 600 after the user has selected different images or views for a property listing, according to several embodiments. The user can save notes in the popup overlay 602 (for example, by clicking on an affordance 610).

[0066] Figure 6E shows another exemplary view of the user interface 600 after a user has saved a note to a property listing in their wishlist, according to several embodiments. In this example, assume that the user has saved the text “Boho interior” to a house in Los Angeles. The text may appear as note 612 on the property card. The note may be associated with the corresponding property in the user’s wishlist.

[0067] Figure 6F shows another view of the exemplary user interface 600 for a wishlist property listing, according to several embodiments. The user may select affordance 524 and further edit, modify, and / or delete notes added to the property listing.

[0068] Figure 6G shows another view of the exemplary user interface 600 for a wishlist property listing, according to several embodiments. The user may add further text as a note to the property listing in the text box 604. In this example, the user adds the text ",big enough" as a note.

[0069] Figure 6H shows another exemplary view of the user interface 600 after a user has saved additional notes to a property listing in their wishlist, according to several embodiments. The updated text may be shown as note 612 on the property card for the property listing. The updated notes may be associated with the corresponding property in the user's wishlist.

[0070] Figure 6I shows another exemplary view of the user interface 600 after the user has entered additional text for notes on a property listing in the wishlist, according to several embodiments. In some embodiments, the entered text may be duplicated (for example, notes entered in area 604 are duplicated on the property card for the property listing). In some embodiments, a summary of the text entered by the user may be shown on the property card. If the text is repeated, a single instance of the text may be shown. Displaying notes alongside properties allows the user to quickly notice previous comments about a property, which helps in more rapid prioritization of properties.

[0071] Figure 7A shows exemplary user interfaces 700 for sharing a wishlist (e.g., a mobile application user interface, a web browser user interface) according to several embodiments. In some embodiments, the system may show a shared wishlist overlay (e.g., a popup overlay 702) for sharing a wishlist. Users may be provided with an option to share a link. For example, affordance 704 may allow a user to send a link to their wishlist to any other user, who may then view the user's wishlist. Another affordance 706 may allow a user to invite others, who may then add and / or edit properties, including notes added to such properties.

[0072] Figure 7B shows another view of the exemplary user interface 700 after a user has chosen to share a link to their wishlist, according to several embodiments. In some embodiments, the system may update the shared wishlist overlay 702 with various options for sending the link (e.g., copy the link, email the link, send a message using a messaging application, post a note on a social network).

[0073] Figure 8A shows exemplary user interfaces 800 (e.g., mobile application user interface, web browser user interface) for selecting dates for properties in a wishlist and / or filtering properties in a wishlist by date, according to several embodiments. This example shows an overlay 802 that allows the user to select dates 806 using a calendar. In this example, the user has selected a start date 810 of June 11, 2023 and an end date 812 of June 20, 2023. Affordances for exact dates 816 and dates 814 with tolerances (e.g., ±1 day, ±2 days, ±3 days, and ±7 days) are also shown. The user may also choose another option 808 if they have flexibility with dates. Area 804 within the overlay 802 may show previews (e.g., thumbnail images) of properties available during the selected dates.

[0074] Figure 8B shows another exemplary view of the user interface 800 after the user has selected a different start date 816, according to several embodiments. The preview 804 shown in Figure 8A may be updated when a new date is selected or thereafter.

[0075] Figure 8C shows another view of the exemplary user interface 800 for flexible dates according to several embodiments. When a user selects an option 808 for flexible dates, the overlay 802 may update to show options for stay durations (e.g., weekends 818, weeks 820, months 822) and ranges of months 824 that can be visited at any time. In some embodiments, the user may select a different set of months by selecting an affordance 826. The area 804 may be updated in real time accordingly. For example, new thumbnail images may be generated and / or stacked with older thumbnail images. Updating the area 804 in real time helps with faster prioritization. For example, as a user shifts the date, the user is immediately notified of which properties are available during that date. The thumbnail images may provide previews of the images, and therefore the stack of thumbnail images may show preferred properties on top of the stack so that the user can quickly see properties of interest for the selected date. In some embodiments, the wishlist management interface and / or map may be updated in real time.

[0076] Figure 8D shows another exemplary view of the user interface 800 after the user has selected different dates, according to several embodiments. This example shows that the user has selected a new start date 828 (June 17) and a new end date 830 (June 23), and area 804 is automatically updated for the new dates.

[0077] Figure 8E shows another view of the exemplary user interface 800 after the user has selected a date for the wish list, according to several embodiments. The interface displays the selected date 832, followed by the properties available during the selected date.

[0078] Figure 8F shows another view of the exemplary user interface 800 showing unavailable items in the wishlist, according to several embodiments. In some embodiments, unavailable items may be shown in different areas or different parts 834 of the user interface. In some embodiments, unavailable listings follow available listings. The user may scroll down to view the listings.

[0079] Figure 9A shows exemplary user interfaces 900 (e.g., a mobile application user interface, a web browser user interface) for easy saving to a wishlist, according to several embodiments. This example shows properties of various categories (or properties with different attributes). In this example, the categories shown are OMG!, Country, Off the Grid, Surfing, Play, Mansion, Scenic View, Beach, Luxury, Log Cabin, Trendy, Farm, Tree Cabin, and Private Room. Suppose the user selects the Mansion category 902. The user interface may be updated to show mansions available on the online marketplace. Some embodiments provide an option 904 for the user to select to show a map of properties within the category. The wishlist may be a collection of data stored in a database (e.g., the memory of the application server 140) containing listings of one or more unique identifiers associated with products and / or services offered for sale on the online marketplace.

[0080] Figure 9B shows another exemplary view of the user interface 900, which displays properties corresponding to the luxury home category 902 in response to a user selection of the luxury home category 902 as shown in Figure 9A, according to several embodiments. The user may view these properties by scrolling down the category listings.

[0081] Figure 9C shows another view of the exemplary user interface 900 after the user has chosen to browse their wish list, according to several embodiments. An overlay 906 displays the user's wish list. The overlay may include an option 908 for creating a new wish list.

[0082] Figure 9D shows another view of the exemplary user interface 900 after the user has chosen to create a new wishlist, according to several embodiments. The overlay 910 may provide a text box 912 for naming the wishlist. The name may be pre-filled with the name of the category (in this case, mansion). The user can override or provide a new name for the wishlist.

[0083] Figure 9E shows another view of the exemplary user interface 900 after the user has chosen to browse the wishlist, according to several embodiments. The overlay 906 shows the wishlist for the user, including a new wishlist for a mansion 916. The system may select representative images for the wishlist depending on various factors, including the user's preferences, the preferences of other users, and / or the user's history of interactions with the online marketplace.

[0084] Figure 9F shows another view of the exemplary user interface 900 after the user has chosen to browse the wish list, according to several embodiments. In this example, we assume that the user has selected the mansion wish list. The interface may display property cards for properties within a category for the user to choose. The interface may also display affordances (e.g., affordance 916) for each property card for the user to choose to add to the current wish list. Properties selected by the user (e.g., by clicking the affordance) are added to the wish list. In some embodiments, property cards may be displayed for a specific category. When the user selects a property card, the properties corresponding to that property card are automatically added to the wish list for that category. This may continue until the user selects a different category.

[0085] Figure 9G shows another exemplary view of the user interface 900 when the user selects a different category, according to several embodiments. In this example, we assume the user has selected category 918. Different properties or property cards may be displayed in the property listing.

[0086] Figure 9H shows another view of the exemplary user interface 900 in several embodiments, when the user selects an affordance to add a property to their wish list. Since the last wish list (for the mansion category) is different from the current category (the log cabin category), the overlay 906 is shown to allow the user to select a wish list from the current wish list or create a new wish list.

[0087] Figure 9I shows another view of the exemplary user interface 900 when the user selects a category, according to several embodiments. The system may automatically switch to one corresponding to the wish list that corresponds to the category, where the user selects items corresponding to affordances 920, 922, and 924. Some embodiments may show a notification 926 (e.g., a banner pop-up notification sometimes called a toast) each time an item is added to the wish list.

[0088] Figure 10 is a flowchart of Method 1000 for organizing a wishlist on an online marketplace, according to several embodiments. In some embodiments, the steps of Method 1000 may be performed by a computer (e.g., Application Server 140). In some embodiments, the steps of Method 1000 may be performed by a system (e.g., Networked System 102). In some embodiments, Figure 10 may correspond to instructions stored in computer memory or a computer-readable storage medium (e.g., the memory of Application Server 140). The memory may store one or more programs configured for execution by one or more processors. For example, the operation of Method 1000 may be performed at least in part by a Wishlist Management Module 150 and / or a Visualization Module 142. In some embodiments, the steps of Method 1000 may be performed by an API Server 120, a web server 122, an application server 140, and / or a database server 124.

[0089] The method may include obtaining a wishlist for a user (1002). The wishlist may contain one or more properties. The wishlist may be a collection of data stored in a database (e.g., memory of application server 140) containing listings of one or more unique identifiers associated with products and / or services offered for sale on an online marketplace. The method may also include displaying one or more property cards (e.g., property cards 502, 504, 506, 508) on a wishlist management graphical user interface (e.g., exemplary user interfaces 400, 500, 600, 700, 800, and / or 900) (1004). Each property card may correspond to each of the one or more properties in the wishlist. The method may also include displaying one or more note-adding affordances (e.g., affordance 524) on the wishlist management graphical user interface for adding notes to one or more properties (1006). Each note-adding affordance is associated with its respective property. The method may also include, in response to detecting a first input from the user on the wishlist management graphical user interface for selecting a first note-adding affordance from one or more affordances, displaying a first note-adding overlay (e.g., overlay 602) for adding a first note to a first property from one or more properties (1008). The method may also include, in response to detecting a second user input in the first note-adding overlay on the wishlist management graphical user interface for entering first text (e.g., entering text in text box 604 and clicking save affordance 610), associating the first text with the first property (1010).The method may also, according to some embodiments, include stopping the display of the first note addition overlay and restarting the display of one or more property cards and one or more note addition affordances (1012), examples of which are described above with reference to Figures 6D and 6E. The method may also include displaying first text on the wishlist management graphical user interface along with a first property card from among one or more property cards (1014). The first property card corresponds to a first property. According to some embodiments, an example of displaying updated notes is described above with reference to Figure 6E.

[0090] Some embodiments allow a user to update notes, examples of which are described above with reference to Figures 6G, 6H, and 6I according to some embodiments. The method may further include displaying a second note-adding overlay (e.g., overlay 604 shown in Figure 6G) for adding a second note to a first property in response to detection of a third input from the user for selecting a first note-adding affordance on the wishlist management graphical user interface. The method may also include associating the second text with the first property in response to detection of a fourth user input in the second note-adding overlay for entering the second text on the wishlist management graphical user interface. The method may also include stopping the display of the second note-adding overlay and resuming the display of one or more property cards and one or more note-adding affordances. The method may also include displaying the second text in place of the first text along with a first property card among one or more property cards on the wishlist management graphical user interface. The first property card may correspond to a first property.

[0091] Some embodiments allow a user to sort cards and / or property listings in a wishlist based on notes. In some embodiments, the method may further include sorting one or more property cards based on notes corresponding to each of the one or more properties in order to obtain a sorted list of one or more property cards. The method may also include displaying one or more property cards on a wishlist management graphical user interface according to the sorted list of property cards. Although this embodiment is not shown in the exemplary user interface, the wishlist management module 150 may include a note sort module for sorting property cards based on added notes. Optionally, the user may search for notes through the user interface.

[0092] In some embodiments, each of the one or more additional note affordances may be shown adjacent to the respective property card of the property corresponding to each additional note affordance. For example, additional note affordance 524 may be shown adjacent to or as part of property card 502.

[0093] Some embodiments allow users to share wishlists and / or notes, examples of which are described above with reference to Figures 7A and 7B according to some embodiments. In some embodiments, the method may also include providing a sharing affordance on the wishlist management graphical user interface. The method may also include, in response to a user selecting a sharing affordance, (i) displaying a wishlist sharing overlay (e.g., overlay 702) on the wishlist management graphical user interface for the user to select a sharing option for sharing the wishlist, and (ii) on the wishlist management graphical user interface, in response to a user selecting a sharing option, associating one or more other users of an online marketplace to share the wishlist, and / or displaying the wishlist for one or more other users. In some embodiments, associating one or more other users of the online marketplace may occur in response to a user, via a wishlist management graphical user interface, (i) providing information relating to one or more other users, and / or (ii) selecting a mechanism for sharing a wishlist with one or more other users (e.g., selecting between options 704 and 706, or selecting the option shown in Figure 7B for sending a link to the wishlist).

[0094] Some embodiments show a map alongside a wishlist, an example of which is described below with reference to Figure 5A. In some embodiments, the method may further include dividing the wishlist management graphical user interface into several areas (e.g., areas 528 and 510). The method may also include displaying one or more property cards in the first area of ​​the wishlist management graphical user interface. The method may also include displaying a map (e.g., a map in area 510) in the second area of ​​the wishlist management graphical user interface. The method may also include displaying several icons (e.g., icon 530) on the map, each icon corresponding to one or more properties. Each icon is displayed approximately at the geographical location on the map corresponding to each property. In some embodiments, the first and second areas may be displayed simultaneously and adjacent to each other. In some embodiments, the first and second regions may be displayed simultaneously, or the first region may be displayed on top of the second region (examples of which are not shown, but may be useful, for example, when the map has a particular shape or when the user prefers to see the listings at the top of the map). In some embodiments, the first and second regions may have different areas. In some embodiments, the first and second regions may have similar areas. In some embodiments, the map may correspond to geographical areas corresponding to the locations of one or more properties in the wishlist. For example, since the property listings are in or near LA, the area near LA is shown in Figure 5A. In some embodiments, the method may further include displaying a subset of one or more property cards in the first region, containing fewer property cards than all of one or more property cards. For example, Figure 5A shows a subset of properties in the LA excursion wishlist. The method may also include displaying a portion of the map smaller than the whole map in the second region, based on the area of ​​the second region.In some embodiments, the method may further include selecting a portion of a map (for example, an approximate portion of the area near LA is shown on the map in Figure 5A) to indicate the location of a subset of properties corresponding to a subset of one or more property cards. In some embodiments, the method may further include selecting a subset of one or more property cards based on the relative importance of the properties to the user. For example, property cards 502 and 504 may be above property cards 506 and 508 because the user prefers them when prioritizing properties, or has clicked on them more than other properties, or because other users prefer them more than other properties, or because the property is the most popular, the most affordable, etc. In some embodiments, the sum of the areas of multiple regions may correspond to the screen size of the device used by the user. For example, fewer property cards may be shown on a mobile screen with a smaller screen budget compared to the desktop version.

[0095] Figure 11 is a flowchart of Method 1100 for organizing a wishlist on an online marketplace, according to several embodiments. In some embodiments, the steps of Method 1100 may be performed by a computer (e.g., application server 140). In some embodiments, the steps of Method 1100 may be performed by a system (e.g., networked system 102). In some embodiments, Figure 11 may correspond to instructions stored in computer memory or a computer-readable storage medium (e.g., the memory of application server 140). The memory may store one or more programs configured for execution by one or more processors. For example, the operation of Method 1100 may be performed at least in part by a wishlist management module 150 and / or a visualization module 142. In some embodiments, the steps of Method 1100 may be performed by an API server 120, a web server 122, an application server 140, and / or a database server 124. Some embodiments allow the user to filter the wishlist based on a selected date and / or display thumbnail images of properties available during the selected date, examples of which are described above with reference to Figures 8A–8F, according to some embodiments.

[0096] The method may include obtaining a wishlist for a user (1102), the wishlist containing one or more items. The wishlist may be a collection of data stored in a database (e.g., the memory of application server 140), containing a listing of one or more unique identifiers associated with products and / or services offered for sale on an online marketplace. The method may also include displaying one or more item cards on a wishlist management graphical user interface (1104), each item card corresponding to one or more items in the wishlist. The method may also include displaying a filter option (e.g., option 836) on the wishlist management graphical user interface for filtering the wishlist based on a date (1106). The method may also include, in response to detecting a first input from the user for selecting a filter option, displaying a calendar overlay (e.g., overlay 802) on the wishlist management graphical user interface showing a calendar with date affordances (e.g., affordance 806) for selecting a date (1108). The method may also include, in response to the user selecting a date affordance for selecting a date (1110), displaying a thumbnail image in an area within the calendar overlay (e.g., an image in area 804) corresponding to one or more properties available during the selected date, while maintaining the display of the calendar overlay on the wishlist management graphical user interface before confirming the date from the user (1112).

[0097] In some embodiments, the thumbnail image may be shown below the calendar. In some embodiments, the area is displayed below the calendar, an example of which is shown in Figure 8A.

[0098] In some embodiments, the date may be filtered after it has been selected by the user. In some embodiments, the method may further include stopping the display of the calendar overlay after receiving confirmation of the date from the user, and displaying only the properties available during the selected date from one or more properties on the wishlist management graphical user interface. According to some embodiments, one example is described above with reference to Figures 8D and 8E.

[0099] In some embodiments, the thumbnail images may be updated in real time. In some embodiments, the thumbnail images may be updated in real time in response to changes in the date. For example, Figures 8A and 8D show different numbers of thumbnail images.

[0100] In some embodiments, available properties may be shown in the wishlist followed by unavailable properties. In some embodiments, the method may further include stopping the display of a calendar overlay and sorting and displaying, on the wishlist management graphical user interface, the properties available during the selected date, followed by the other properties that are unavailable during the selected date, from among one or more properties. Examples of these steps are described above with reference to Figure 8F according to some embodiments.

[0101] Some embodiments may indicate the number of available properties. In some embodiments, the method may further include displaying the number of available properties for a selected date in a region adjacent to the thumbnail image.

[0102] Some embodiments may allow the user to select an exact date and / or a date with a tolerance (e.g., ±1, ±2, etc.) for the wishlist. In some embodiments, the method may further include displaying one or more affordances in the area for selecting an exact date or a date with a tolerance. In some embodiments, the method may further include updating the area with an updated set of thumbnail images corresponding to an updated set of properties available during the date with a tolerance, in response to the user selecting an affordance corresponding to a date with a tolerance. Examples according to some embodiments are described above with reference to Figures 8A–8D.

[0103] Figures 12A and 12B are flowcharts of Method 1200 for organizing a wishlist on an online marketplace, according to several embodiments. In some embodiments, the steps of Method 1200 may be performed by a computer (e.g., Application Server 140). In some embodiments, the steps of Method 1200 may be performed by a system (e.g., Networked System 102). In some embodiments, Figures 12A and 12B correspond to instructions stored in computer memory or a computer-readable storage medium (e.g., the memory of Application Server 140). The memory may store one or more programs configured for execution by one or more processors. For example, the operation of Method 1200 may be performed at least in part by a Wishlist Management Module 150 and / or a Visualization Module 142. In some embodiments, the steps of Method 1200 may be performed by an API Server 120, a web server 122, an application server 140, and / or a database server 124. In some embodiments, users are allowed to save items to their wishlist. The wishlist may be a collection of data stored in a database (for example, in the memory of the application server 140) that includes a listing of one or more unique identifiers associated with products and / or services offered for sale on an online marketplace.

[0104] Referring to Figure 12A, the method may also include displaying one or more category affordances (e.g., affordances for categories in Figure 9A) on the wishlist management graphical user interface (1202). Each category affordance may correspond to each of one or more categories of properties available on the online marketplace. The method may also include displaying one or more first property cards on the wishlist management graphical user interface in response to detecting a first input from the user to select a first category affordance from one or more category affordances (1206). Each of the first one or more property cards may correspond to each of the first one or more first properties for a first category corresponding to the first category affordance. For example, Figure 9A shows properties in the category of luxury homes. The method may also include displaying one or more first wishlist icons (e.g., icons 928-2, ..., 928-14) on the wishlist management graphical user interface (1208), where each wishlist icon corresponds to each of the first one or more property cards. The method may also include, in response to detecting a user selection of one or more first wishlist icons on the wishlist management graphical user interface, generating a first wishlist for a first category and associating the first property corresponding to the first wishlist icon with the first wishlist for the first category (1210). For example, the user selects affordance 916 in Figure 9F.

[0105] Referring now to Figure 12B, the method may also include displaying an option on the wishlist management graphical user interface for viewing wishlists created by the user (1212). The method may also include displaying a set of wishlist affordances (or wishlist cards similar to property cards) on the wishlist management graphical user interface in response to detection that the user has selected the option to view the list (1214), where each wishlist affordance corresponds to each of the wishlists created by the user. The method may also include displaying a first property card on the wishlist management graphical user interface in response to detection that the user has selected a first wishlist affordance corresponding to a first wishlist (1216).

[0106] In some embodiments, the method may allow the user to switch wishlists. In some embodiments, the method may further include displaying a second set of one or more property cards on the wishlist management graphical user interface in response to detecting a second input from the user for selecting a second category affordance from one or more category affordances on the wishlist management graphical user interface. Each of the second set of one or more property cards may correspond to each of the second set of one or more properties for a second category corresponding to the second category affordance. The method may also include displaying a second set of one or more icons on the wishlist management graphical user interface, each of the second set of one or more icons corresponding to each of the second set of property cards. The method may also include associating a third property corresponding to a third icon with the second category in the second wishlist in response to detecting that the user has selected a third icon from the second set of one or more icons on the wishlist management graphical user interface. The method may also include, in response to detection on the wishlist management graphical user interface that the user has selected a fourth icon from one or more second icons, associating the fourth item corresponding to the fourth icon with the second wishlist for the first category. The method may also include, in response to detection on the wishlist management graphical user interface that the user has selected an option to browse the list, displaying a set of wishlist affordances including the first and second wishlists. Examples of switching between wishlists and categories are described above with reference to Figures 9F, 9G, 9H, and 9I according to several embodiments.

[0107] In some embodiments, the method may allow users to add items to a wishlist for a category. In some embodiments, the method may further include, in response to detecting that a user has selected a second icon from one or more first wishlist icons on a wishlist management graphical user interface, associating a second item corresponding to the second icon with the first wishlist for the first category. According to some embodiments, one example is described above with reference to Figures 9H and 9I. In some embodiments, a first wishlist having a first set of items for the first category already exists, and then, in response to a selection in the second category, the method includes automatically creating a wishlist.

[0108] The terms "first," "second," etc., are used herein in some cases to describe various elements, but it will be understood that these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, a first widget can be called a second widget without deviating from the range of various described implementations, and similarly, a second widget can be called a first widget. Both the first and second widgets are widgets, but they are not of the same nature unless explicitly stated so.

[0109] The terms used in the descriptions of the various implementations described herein are intended solely to describe and not to limit any particular implementation. As used in the descriptions of the various implementations and the accompanying claims, the singular forms "a," "an," and "the" are intended to include the plural form unless the context clearly indicates otherwise. The terms "and / or" as used herein will be understood to refer to and include one or any possible combination of the enumerated items relating to the description. The terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of a described feature, integer, step, operation, element, and / or component, but will not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0110] The above description is provided with reference to specific implementations for illustrative purposes. However, the above illustrative description is not intended to be exhaustive or to limit the claims to the exact forms disclosed. Many modifications and variations are possible in light of the above teachings. The implementations are selected to best illustrate the underlying principles of the claims and their practical applications, thereby enabling those skilled in the art to best utilize various modifications suitable for the specific intended applications.

Claims

1. A method for creating a wish list on an online marketplace, wherein the method is: In a computing system having one or more processors and a memory for storing one or more programs configured for execution by the one or more processors, The graphical user interface for wishlist management displays one or more category affordances, each of which corresponds to one or more categories of properties available on the online marketplace. In response to detecting a first input from the user for selecting a first category affordance from the one or more category affordances in the wishlist management graphical user interface, the wishlist management graphical user interface displays one or more first item cards, wherein each of the one or more first item cards corresponds to each of the one or more first items for the first category corresponding to the first category affordance. The graphical user interface for wishlist management displays one or more first wishlist icons, each wishlist icon corresponding to one of the one or more first property cards. In the wishlist management graphical user interface, in response to detecting a user selection of one or more of the first wishlist icons, a first wishlist is generated for the first category, and the first item corresponding to the first wishlist icon is associated with the first wishlist for the first category. The graphical user interface for managing the wishlist will display an option for viewing the wishlist created by the user. In the wishlist management graphical user interface, in response to detecting that the user has selected the option to view the list, a set of wishlist affordances is displayed, wherein each wishlist affordance corresponds to a wishlist among the wishlists created by the user. In response to the detection in the wishlist management graphical user interface that the user has selected a first wishlist affordance corresponding to the first wishlist, The graphical user interface for managing the wishlist displays a first property card corresponding to the first property associated with the first wishlist. Methods that include...

2. In response to detecting a second input from the user for selecting a second category affordance from the one or more category affordances in the wishlist management graphical user interface, the wishlist management graphical user interface displays one or more second item cards, wherein each of the one or more second item cards corresponds to each of the one or more second items for the second category corresponding to the second category affordance. Displaying one or more second icons on the wishlist management graphical user interface, wherein each of the two icons corresponds to each of the two property cards. In the wishlist management graphical user interface, in response to detecting that the user has selected a third icon from the second one or more icons, the third item corresponding to the third icon is associated with the second wishlist for the second category, In the wishlist management graphical user interface, in response to detecting that the user has selected a fourth icon from the second one or more icons, the fourth item corresponding to the fourth icon is associated with the second wishlist for the first category. In the wishlist management graphical user interface, in response to detecting that the user has selected the option to view the list, the set of wishlist affordances including the first wishlist and the second wishlist is displayed. The method according to claim 1, further comprising:

3. In the wishlist management graphical user interface, in response to the user selecting a second icon from the first one or more wishlist icons, the second item corresponding to the second icon is associated with the first wishlist for the first category. The method according to claim 1 or 2, further comprising:

4. A method for creating a wish list on an online marketplace, wherein the method is: In a computing system having one or more processors and a memory for storing one or more programs configured for execution by the one or more processors, To obtain a wish list for a user, wherein the wish list includes one or more items. The graphical user interface for wishlist management displays one or more property cards, each property card corresponding to one or more properties in the wishlist. The graphical user interface for managing the wishlist displays one or more note-adding affordances for adding notes to one or more properties, where each note-adding affordance is associated with a specific property. In the wishlist management graphical user interface, in response to detecting a first input from the user for selecting a first note-adding affordance from the one or more affordances, a first note-adding overlay is displayed for adding a first note to the first item from the one or more items. In the wishlist management graphical user interface, in response to detecting a second user input within the first note-adding overlay for entering a first text, the first text is associated with the first item. The following steps are taken to stop displaying the first note addition overlay on the wishlist management graphical user interface and to restart displaying the one or more property cards and the one or more note addition affordances: Displaying the first text along with the first property card from among the one or more property cards in the wishlist management graphical user interface, wherein the first property card corresponds to the first property. Methods that include...

5. In the wishlist management graphical user interface, in response to detecting a third input from the user for selecting the first note addition affordance, a second note addition overlay is displayed for adding a second note to the first property. In the wishlist management graphical user interface, in response to detecting a fourth user input within the second note-adding overlay for entering a second text, the second text is associated with the first item. The display of the second note addition overlay is stopped, and the display of the one or more property cards and the one or more note addition affordances is resumed. The graphical user interface for wishlist management displays the second text in place of the first text along with the first property card among the one or more property cards, wherein the first property card corresponds to the first property. The method according to claim 4, further comprising:

6. In order to obtain a sorted list of the one or more property cards, the one or more property cards are sorted based on the note corresponding to each of the one or more properties, The wishlist management graphical user interface displays one or more property cards according to the sorted list of property cards. The method according to any one of claims 4 to 5, further comprising:

7. The method according to any one of claims 4 to 5, wherein each of the one or more note-adding affordances is shown adjacent to the respective property card of the respective property corresponding to each note-adding affordance.

8. To provide shared affordances to the aforementioned wishlist management graphical user interface, In response to the user selecting the shared affordance, The wishlist management graphical user interface displays a wishlist sharing overlay for the user to select sharing options for sharing the wishlist, In the wishlist management graphical user interface, in response to the user selecting the sharing option, associate one or more other users of the online marketplace with the wishlist to share it, and / or display the wishlist for the one or more other users. The method according to any one of claims 4 to 5, further comprising:

9. The method according to claim 8, wherein associating the one or more other users of the online marketplace is done in response to the user (i) providing information relating to the one or more other users, and / or (ii) selecting a mechanism for sharing the wishlist with the one or more other users, via the wishlist management graphical user interface.

10. The aforementioned wishlist management graphical user interface is divided into multiple areas, Displaying one or more property cards in the first area of ​​the wishlist management graphical user interface, Displaying a map in the second area of ​​the aforementioned wishlist management graphical user interface, Displaying multiple icons on the aforementioned map, each icon corresponding to one or more of the aforementioned properties, and each icon being displayed approximately at the geographical location on the map corresponding to each of the aforementioned properties. The method according to any one of claims 4 to 5, further comprising:

11. The method according to claim 10, wherein the first region and the second region are displayed simultaneously and adjacent to each other.

12. The method according to claim 10, wherein the first region and the second region are displayed simultaneously, and the first region is displayed on top of the second region.

13. The method according to claim 10, wherein the first region and the second region have different areas.

14. The method according to claim 10, wherein the first region and the second region have similar areas.

15. The method according to claim 10, wherein the map corresponds to a geographical area corresponding to the location of one or more properties in the wish list.

16. Displaying a subset of the one or more property cards in the first area, which includes fewer property cards than all of the one or more property cards, In the second region, a portion of the map smaller than the entire map is displayed based on the area of ​​the second region. The method according to claim 10, further comprising:

17. Selecting the portion of the map to show the location of the subset of properties corresponding to the subset of the one or more property cards. The method according to claim 16, further comprising:

18. Selecting the subset of one or more property cards based on the relative importance of the user's properties. The method according to claim 16, further comprising:

19. The method according to claim 10, wherein the sum of the areas of the plurality of regions corresponds to the screen size of the device used by the user.

20. A method for creating a wish list on an online marketplace, wherein the method is: In a computing system having one or more processors and a memory for storing one or more programs configured for execution by the one or more processors, To obtain a wish list for a user, wherein the wish list includes one or more items. The graphical user interface for wishlist management displays one or more property cards, each property card corresponding to one or more properties in the wishlist. The graphical user interface for managing the wishlist will display filter options for filtering the wishlist based on the date, In response to detecting a first input from the user for selecting the aforementioned filter option, The aforementioned wishlist management graphical user interface displays a calendar overlay showing a calendar with date affordances for selecting a date, In the wishlist management graphical user interface, in response to the user selecting the date affordance for selecting a date, before confirming the date from the user, While maintaining the display of the calendar overlay of the wishlist management graphical user interface, a thumbnail image corresponding to one or more properties available on a selected date is displayed in an area within the calendar overlay. Methods that include...

21. The method according to claim 20, wherein the area is displayed below the calendar.

22. After receiving confirmation of the date from the user, To stop displaying the aforementioned calendar overlay, The wishlist management graphical user interface displays only the properties that are available during the selected date from among the one or more properties. The method according to any one of claims 20 to 21, further comprising:

23. The method according to any one of claims 20 to 21, wherein the thumbnail image is updated in real time in response to a change in date.

24. To stop displaying the aforementioned calendar overlay, The wishlist management graphical user interface is configured to display, in a sorted manner, the properties available during the selected date from among the one or more properties, followed by the other properties that are unavailable during the selected date from among the one or more properties. The method according to any one of claims 20 to 21, further comprising:

25. In the aforementioned area, adjacent to the thumbnail image, the number of available properties for the selected date is displayed. The method according to any one of claims 20 to 21, further comprising:

26. Display one or more affordances in the area for selecting an exact date or a date with tolerance. The method according to any one of claims 20 to 21, further comprising:

27. In response to the user selecting an affordance corresponding to a tolerable date, the area is updated with an updated set of thumbnail images corresponding to an updated set of properties among the one or more properties that are available during the tolerable date. The method according to claim 26, further comprising:

28. A system comprising a server including one or more processors and memory for storing one or more programs executed by the one or more processors, wherein the one or more programs are A command for displaying one or more category affordances in the wishlist management graphical user interface, wherein each category affordance corresponds to one or more categories of properties available on the online marketplace, and the command is used for this purpose. In response to detecting a first input from the user for selecting a first category affordance from the one or more category affordances in the wishlist management graphical user interface, the wishlist management graphical user interface is given a command to display one or more first item cards, wherein each of the one or more first item cards corresponds to each of the one or more first items for the first category corresponding to the first category affordance. A command for displaying one or more first wishlist icons in the wishlist management graphical user interface, wherein each wishlist icon corresponds to each of the one or more first property cards, and the command The wishlist management graphical user interface, in response to detecting a user selection of a first wishlist icon from the first one or more wishlist icons, generates a first wishlist for the first category and provides a command to associate a first item corresponding to the first wishlist icon with the first wishlist for the first category. The aforementioned wishlist management graphical user interface includes a command for displaying options for viewing the wishlist created by the user, In the said wishlist management graphical user interface, in response to detection that the user has selected the option to view the list, a command for displaying a set of wishlist affordances, wherein each wishlist affordance corresponds to a command for each of the wishlists created by the user. In response to the detection in the wishlist management graphical user interface that the user has selected a first wishlist affordance corresponding to the first wishlist, The wishlist management graphical user interface includes a command for displaying a first property card corresponding to the first property associated with the first wishlist. A system that includes this.

29. A non-temporary computer-readable storage medium for storing one or more programs configured for execution by a computer system having a display, one or more processors, and memory, wherein the one or more programs are A command for displaying one or more category affordances in the wishlist management graphical user interface, wherein each category affordance corresponds to one or more categories of properties available on the online marketplace, and the command is used for this purpose. In response to detecting a first input from the user for selecting a first category affordance from the one or more category affordances in the wishlist management graphical user interface, the wishlist management graphical user interface is given a command to display one or more first item cards, wherein each of the one or more first item cards corresponds to each of the one or more first items for the first category corresponding to the first category affordance. A command for displaying one or more first wishlist icons in the wishlist management graphical user interface, wherein each wishlist icon corresponds to each of the one or more first property cards, and the command The wishlist management graphical user interface, in response to detecting a user selection of a first wishlist icon from the first one or more wishlist icons, generates a first wishlist for the first category and provides a command to associate a first item corresponding to the first wishlist icon with the first wishlist for the first category. The aforementioned wishlist management graphical user interface includes a command for displaying options for viewing the wishlist created by the user, In the said wishlist management graphical user interface, in response to detection that the user has selected the option to view the list, a command for displaying a set of wishlist affordances, wherein each wishlist affordance corresponds to a command for each of the wishlists created by the user. In response to the detection in the wishlist management graphical user interface that the user has selected a first wishlist affordance corresponding to the first wishlist, The wishlist management graphical user interface includes a command for displaying a first property card corresponding to the first property associated with the first wishlist. Non-temporary computer-readable storage media, including [specific type of storage medium].

Images