A real estate messaging framework
Budget: $1,500 – $3,000 USD
A messaging framework on mobile platforms (Android & iOS) to connect real estate identities, each of which with its own role based access control as follows:
Seller
• Data producer and main API builder with ability to list, view, edit, delete a property – schema needs to have all relevant fields as per standard property features
• Entity relationship to Realtor: There needs to be a field in schema giving the option to work with a Realtor
• Entity relationship to Buyer: Once any buyer has reached out to set an appointment to view the property and the Seller is sharing contact information and property location, we should have a Boolean field to detect this.
Realtor
• The middleman between the seller and buyer and will have access to read only specific listings
• As implied above, only the listings for which the Seller has allowed for them to be viewed by a Realtor
• This is a credits-based identity – meaning the Realtor should pay for credits to be able to message a Seller about a property and provide services to Seller, such as pricing their home, holding open houses, coordinating showings with Buyers.
Buyer
• Consumer with ability to view all listings and message the owners at will
• Its credits model need not be activated unless the Seller is sharing the property location and Seller’s contact with Buyer through a message – a Boolean field sets this up as hinted above.
• If the Buyer has enough credits, then all related information will be shared with him/her.
MVP: Looking for a robust solution including a customer identity and access management (CIAM) - for example, a duplicate identity that attempts to cut through the roles above should be detected and avoided creation. Each identity needs to have its own specific dashboard, e.g., for a Realtor, the names of the Sellers worked with in the past month. Sleek design wire-frames and nice graphics can be helpful.
Preference to cross-platform backend engines, such as React Native, Flutter or Xamarin, ideally turning in a single codebase. If you’re interested in making this app, go head and draft a brief proposal including tooling and delivery timeline you’d pick for it.
Thanks and I'm looking forward to working with you!
Seller
• Data producer and main API builder with ability to list, view, edit, delete a property – schema needs to have all relevant fields as per standard property features
• Entity relationship to Realtor: There needs to be a field in schema giving the option to work with a Realtor
• Entity relationship to Buyer: Once any buyer has reached out to set an appointment to view the property and the Seller is sharing contact information and property location, we should have a Boolean field to detect this.
Realtor
• The middleman between the seller and buyer and will have access to read only specific listings
• As implied above, only the listings for which the Seller has allowed for them to be viewed by a Realtor
• This is a credits-based identity – meaning the Realtor should pay for credits to be able to message a Seller about a property and provide services to Seller, such as pricing their home, holding open houses, coordinating showings with Buyers.
Buyer
• Consumer with ability to view all listings and message the owners at will
• Its credits model need not be activated unless the Seller is sharing the property location and Seller’s contact with Buyer through a message – a Boolean field sets this up as hinted above.
• If the Buyer has enough credits, then all related information will be shared with him/her.
MVP: Looking for a robust solution including a customer identity and access management (CIAM) - for example, a duplicate identity that attempts to cut through the roles above should be detected and avoided creation. Each identity needs to have its own specific dashboard, e.g., for a Realtor, the names of the Sellers worked with in the past month. Sleek design wire-frames and nice graphics can be helpful.
Preference to cross-platform backend engines, such as React Native, Flutter or Xamarin, ideally turning in a single codebase. If you’re interested in making this app, go head and draft a brief proposal including tooling and delivery timeline you’d pick for it.
Thanks and I'm looking forward to working with you!