# US 2020/0404054 A1 · Computerized system, method and computer program product, facilitating real estate transactions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0404054 A1
- Document ID: US20200404054A1
- Status: Published application
- Kind: A1
- Application number: 16/905,159
- Filed: 2020-06-18
- Published: 2020-12-24
- Earliest claimed: 2019-06-19
- Applicants: Reali Inc.
- Inventors: Ami Amiel Shai AVRAHAMI; Amit HALLER; Stacy Kirsten HOOVER
- Web page: https://patentgrep.com/patent/US20200404054A1

## CPC

- H04L 67/1091: {Interfacing with client-server systems or between P2P systems}
- G06Q 50/16: Real estate
- H04L 12/1859: {adapted to provide push services, e.g. data channels}
- H04L 51/06: Message adaptation to terminal or network requirements
- H04L 65/4015: {where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference}
- H04L 65/611: for multicast or broadcast (systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06)
- H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
- H04L 67/1044: {Group management mechanisms (management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425)}
- H04L 67/133: Protocols for remote procedure calls [RPC]
- H04L 67/55: Push-based network services
- H04L 65/1073: Registration or de-registration
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A software system comprising a mobile app having a backend including a processor, whose logic supports plural functionalities used by end-users/clients of the mobile app; logic presenting, to each of a population of end users of the mobile app, a linear list of the functionalities, thereby defining an ordering of the functionalities; logic presenting an indication (aka journey status change aka journey status update), to each individual end-user, in at least near-real time, of how far along the list s/he has progressed in using the functionalities, wherein the mobile app logic allows at least one individual end user to use the functionalities repeatedly and in a sequence other than defined by the ordering, at least once the individual end-user has used all of the functionalities at least once.

## Claims

### Claim 1

A software system comprising:
a mobile app having a backend including a processor, whose logic supports plural functionalities used by end-users/clients of the mobile app;
logic presenting, to each of a population of end users of the mobile app, a linear list of said functionalities, thereby defining an ordering of said functionalities;
logic presenting an indication (aka journey status change aka journey status update), to each individual end-user, in at least near-real time, of how far along said list s/he has progressed in using said functionalities,
wherein the mobile app logic allows at least one individual end user to use said functionalities repeatedly and in a sequence other than defined by said ordering, at least once said individual end-user has used all of said functionalities at least once.

### Claim 2 (depends on 1)

A system according to claim 1 wherein the backend provides at least one p2p (peer to peer notification, including a journey status change of an end-user, to a p2p processor aka p2p subsystem aka p2p logic which gets messages indicating journey status changes, and stores them.

### Claim 3 (depends on 2)

A system according to claim 2 wherein said p2p subsystem comprises a pubnub server which gets pubnub messages indicating journey status changes, and stores them.

### Claim 4 (depends on 2)

A system according to claim 2 wherein said indication comprises a graphic indication e.g. checkmark associated with each of said functionalities on said linear list, which the individual end-user has already used and wherein no graphic indication is associated with functionalities on said linear list, which the individual end-user has not yet used.

### Claim 5 (depends on 2)

A system according to claim 2 wherein said p2p notification includes a journey data flat map storing a user journey steps and/or tasks, and wherein at least one client uses a journey payload to update at least one journey task on each p2p notification.

### Claim 6 (depends on 1)

A system according to claim 1 wherein when a client receives a journey status update, the update may be represented in a flat (not relational) map which includes a representation of the user journey including, in a single list, steps and/or tasks included in said journey, and wherein the update also includes a step/task key and/or a display name.

### Claim 7 (depends on 2)

A system according to claim 2 wherein a single p2p channel and infrastructure is used to pass, as p2p messages,
chat messages including text for the end-user to view; and
journey status update.

### Claim 8 (depends on 7)

A system according to claim 7 wherein at least one chat message includes metadata which includes an identification of the chat message's sender and/or a media download key and/or a timestamp.

### Claim 9 (depends on 2)

A system according to claim 2 wherein the p2p processor uses sockets rather than API polling to receive a real time indication of journey status changes.

### Claim 10 (depends on 8)

A system according to claim 8 wherein said metadata is stored in the p2p side, in association with messages history.

### Claim 11 (depends on 8)

A system according to claim 8 wherein said metadata is stored locally, on the end user's smartphone's local storage.

### Claim 12 (depends on 1)

A system according to claim 1 wherein at least one mobile client saves at least some properties in order to subsequently display said properties later including retrieving said properties from the local storage rather than requesting said properties from the p2p service.

### Claim 13 (depends on 2)

A system according to claim 2 and also comprising at least one ‘get history’ API via which chat and status update messages stored by said p2p subsystem are retrieved.

### Claim 14 (depends on 7)

A system according to claim 7 wherein a server, upon identifying a journey status change relating to a given end-user, sends a message to a dedicated p2p channel extending to that end-user's client and wherein the end-user's client asks the history of said dedicated channel at a subsequent time,
and if the client identifies a status change type message, the client makes a journey status change.

### Claim 15 (depends on 14)

A system according to claim 14 wherein the client includes logic which prioritizes asking the history during client-idle time over asking the history at a time t which is not client-idle time.

### Claim 16 (depends on 14)

A system according to claim 14 wherein the client includes logic which prioritizes asking the history during channel-idle time over asking the history at a time t which is not channel-idle time.

### Claim 17 (depends on 15)

A system according to claim 15 wherein the client includes logic which always asks the history during idle time.

### Claim 18

A method for facilitating use of a mobile app by end-users, the method comprising:
providing a mobile app having a backend including a processor, whose logic supports plural functionalities used by end-users/clients of the mobile app;
presenting, to each of a population of end users of the mobile app, a linear list of said functionalities, thereby defining an ordering of said functionalities;
presenting an indication (aka journey status change aka journey status update), to each individual end-user, in at least near-real time, of how far along said list s/he has progressed in using said functionalities,
wherein the mobile app logic allows at least one individual end user to use said functionalities repeatedly and in a sequence other than defined by said ordering, at least once said individual end-user has used all of said functionalities at least once.

### Claim 19 (depends on 18)

A method according to claim 18 wherein the end-users include buyer end-users and seller end-users and the mobile app supports creation and managing by an individual buyer end-user, of plural draft offers to plural seller end-users wherein said managing comprises defining branching logic for sending said draft offers to said seller end-users thereby to enable a buyer interested in more than one property offered by more than one respective seller end-user, to create a main offer and at least one additional draft offer/s and to define, even before the main offer has been accepted or refused, an actionable backup plan defining, via said branching logic, how said additional draft offers are to be engaged if the main offer is refused.

### Claim 20 (depends on 18)

A method according to claim 18 wherein the end-users include buyer end-users and seller end-users and the mobile app supports creation and managing by an individual buyer end-user, of at least one draft offer to at least one respective seller end-user and wherein said managing includes modifying at least one parameter of a draft offer, responsive to a counter-offer proposed by said seller end-user.

### Claim 21 (depends on 18)

A method according to claim 18 wherein the end-users include buyer end-users and seller end-users and the mobile app supports creation and managing by an individual buyer end-user, of at least one offer to at least one respective seller end-user and wherein a virtual assistant is used to generate said offer.

### Claim 22 (depends on 21)

A method according to claim 21 wherein said offer includes a proposed buyer-seller transaction whose value is generated automatically, thereby to allow buyer end-users to benefit from automatically generated real estate value predictions.

### Claim 23 (depends on 21)

A method according to claim 21 wherein at least one market report is retrieved during creation of at least one offer.

### Claim 24 (depends on 21)

A method according to claim 21 wherein creation of at least one offer is expedited by holding a chat between the buyer end-user of said app and an expert end-user of said app.

### Claim 25

A computer program product, comprising a non-transitory tangible computer readable medium having computer readable program code embodied therein, said computer readable program code adapted to be executed to implement a method for facilitating use of a mobile app by end-users, the method comprising:
providing a mobile app having a backend including a processor, whose logic supports plural functionalities used by end-users/clients of the mobile app;
presenting, to each of a population of end users of the mobile app, a linear list of said functionalities, thereby defining an ordering of said functionalities;
presenting an indication (aka journey status change aka journey status update), to each individual end-user, in at least near-real time, of how far along said list s/he has progressed in using said functionalities,
wherein the mobile app logic allows at least one individual end user to use said functionalities repeatedly and in a sequence other than defined by said ordering, at least once said individual end-user has used all of said functionalities at least once.

### Claim 26 (depends on 16)

A system according to claim 16 wherein the client includes logic which always asks the history during idle time.
