52065b - Laravel Messaging / Mail Component
Budget: $30 – $250 CAD
We have a Laravel PHP application for booking office space rentals. The application has four types of users, which are the Hosts, Guests, Site Administrators, and Public (non-registered site visitors)
The current staging url for the desktop version is: http://myoffice.mybackpocket.co/
Objectives
The objective of this project is develop a feature which will allow users to directly communicate with each other, the general public. This project will be divided into three phases.
• Phase 1: Create a feature that will enable registered users (Host and Guests) to communicate with each
other, and the Site Administrator through direct messaging.
o Users should be able to manage their messages through their Inbox.
o Messages, should only have a set amount of Default Categories, which users cannot edit. These
are:
▪ General
▪ Bookings
▪ Billing
▪ Support
▪ Feedback
o Users should be able to search and filter messages by:
▪ Username
▪ Booking ID
▪ Category
▪ Date Range
o There should be two message types:
▪ Active and Archived
• Phase 2: Add Email Service functionality to the Messaging system. With this feature, Users will be able to
send/receive email to external sources.
o Users will have their own unique email address in our domain
o Outgoing mail will be managed through our own Laravel Mail Service application, called PostOffice
o Emails will have the same Message Types, Categories, and Message Management functions.
• Phase 3: Create a Chat Messaging function.
o Depending on the page within our application, the chat will be monitored by either the Site
Administrator or the Host. An example of Host monitored pages would be:
▪ Listing Details Page
▪ Host Profile Page
▪ Checkout Page
Development Guidelines
• Each Phase must be completed within SEVEN (7) Days, including bug fixes.
• The highest priority is ensuring speedy development. This project does NOT have to be custom
developed. We would prefer using stable pre-built scripts or components that can accomplish our
required features.
• The total project time is three weeks, including full bug fixes.
• Developer must have his/her own server for local development, and then provide a URL or online platform
that will enable our QA team to test the deliverables
• There are approximately XXX screens to be created for this project and a list is attached for review. The
screens are organized into each section of the application and milestones will be organized and submitted
per section.
• Each section must be delivered within one week, and any bug fixes must be completed within 48 hours
after receipt of Feedback. For larger sections, we may break this up into two or more milestones which are
deliverable on a weekly basis
• Efficient coding and thorough QA testing by the developer prior to submission is expected.
• It is critical to deliver assigned projects in a timely manner.
Project Password
• ‘SUPERNOVA'
The current staging url for the desktop version is: http://myoffice.mybackpocket.co/
Objectives
The objective of this project is develop a feature which will allow users to directly communicate with each other, the general public. This project will be divided into three phases.
• Phase 1: Create a feature that will enable registered users (Host and Guests) to communicate with each
other, and the Site Administrator through direct messaging.
o Users should be able to manage their messages through their Inbox.
o Messages, should only have a set amount of Default Categories, which users cannot edit. These
are:
▪ General
▪ Bookings
▪ Billing
▪ Support
▪ Feedback
o Users should be able to search and filter messages by:
▪ Username
▪ Booking ID
▪ Category
▪ Date Range
o There should be two message types:
▪ Active and Archived
• Phase 2: Add Email Service functionality to the Messaging system. With this feature, Users will be able to
send/receive email to external sources.
o Users will have their own unique email address in our domain
o Outgoing mail will be managed through our own Laravel Mail Service application, called PostOffice
o Emails will have the same Message Types, Categories, and Message Management functions.
• Phase 3: Create a Chat Messaging function.
o Depending on the page within our application, the chat will be monitored by either the Site
Administrator or the Host. An example of Host monitored pages would be:
▪ Listing Details Page
▪ Host Profile Page
▪ Checkout Page
Development Guidelines
• Each Phase must be completed within SEVEN (7) Days, including bug fixes.
• The highest priority is ensuring speedy development. This project does NOT have to be custom
developed. We would prefer using stable pre-built scripts or components that can accomplish our
required features.
• The total project time is three weeks, including full bug fixes.
• Developer must have his/her own server for local development, and then provide a URL or online platform
that will enable our QA team to test the deliverables
• There are approximately XXX screens to be created for this project and a list is attached for review. The
screens are organized into each section of the application and milestones will be organized and submitted
per section.
• Each section must be delivered within one week, and any bug fixes must be completed within 48 hours
after receipt of Feedback. For larger sections, we may break this up into two or more milestones which are
deliverable on a weekly basis
• Efficient coding and thorough QA testing by the developer prior to submission is expected.
• It is critical to deliver assigned projects in a timely manner.
Project Password
• ‘SUPERNOVA'