jackilex / property_managment_communication_app

This repo is to showcase my progress while creating the app/service that will focus on Increasing better communication between property managers (community, apartments) and the clients they serve

Property_managment_communication_App

This repo is to showcase my progress while creating the app/service that will focus on Increasing better communication between property managers (community, apartments) and the clients they serve.

FYI: this repo doesn't include actual codes, please contact me if you would like to see my progress.

Overview

The PROPERTY MANAGER is totally accountable for all community operations. The purpose of the PROPERTY MANAGER is to effectively manage and coordinate persons, activates,and available resources in order to accomplish community objectives as set forth by the Regional Property Manager and property owner.

Issue

As a current person living in a community managed by a property managers, I realized that often the emails from my property managers were often unread or they were been read often too late. That is because most people prioritized work emails and other expected emails. Emails are a greate way to communicate; however it is a very crowded channel to communicate, and emails can get lost very easily

Solution

The solution is to bring all users/resident in one channel were they are expected to only get notification about their property, community or apartment complex

Key features (Mobile App and Website Dashboard)

Property Managers will be able to:

• create a project
• invite their residents and staff to subscribe to the project's channel
• send Announcements notifications
• send Events notifications:
  • events will have a calendar date which will automatically add the date to users Mobile calendar
• create details informations about the Ammenities.

Residents will be able to:

• read and save Announcments and Events
• write post on the communty channel to communicate to neighbors (Example: Lost dog)
• set remnders
• send maintenance request etc.

Architecture

• the architecture will use:
  • Gcloud serverless Functions (Node.js)
  • the mobile app (Android + IOS) is being built using Flutter
  • the dashboard (for managers only) website will be constructed either with React or Flutter
  • Database : MongoDb and Firestore

UserFlow

1. What/who is a user? a user using this app can either be a Manager or Resident, overall both users will have the smae userflow.

• A User manager will have extra permissions and multiple projects/residence to manage (RBAC + ABAC).
• A user resident will typically have one project/resident and limited perrmissions.

2. User(s) objectives?

• select a project (if user have more than one)
• view project details and contact info
• read announcments or events from project(s) channel
• view and read Amenities details
• submit maintenance request form or view request updates
• view or set reminders

Userflow - Diagram phase 1

Data Flow