Hackathon Project


HackTPS was a three-day hackathon, hosted by Toronto Police Services (TPS) , in collaboration with the City of Toronto, Equitech, and the Ryerson DMZ. We were challenged to use ground breaking technologies to enhance real-time data and information to empower the community and build solutions for persistent safety issues.

Problem Definition

Our team began by analyzing the core problems that the Toronto Police Services currently face. After speaking with some police officers that were at the event, one clear issue stood out: the sheer amount of 911 requests they receive. Specifically, the TPS receive 70 to 80 low priority calls a day. Examples of such calls include those for loud house parties, or a stray animal wandering in the neighbourhood. Police must still spend time dealing with these situations. Due to a limited amount of human resources, more and more people calling 911 get put on hold -  even those in high priority life or death situations.

The Solution

Our target user was defined as someone who was scared or pissed, and not in life threatening danger (we made the assumption that if the problem was 911 worthy, the user's instant reaction would be calling 911 anyway). We also concluded that in order to make our service as accessible as possible, we would create a mobile app as users would more likely be on their phone than laptop. In the end, we decided to create a mobile application that reduces the number of 911 calls and direct lower priority emergencies to community watchers.

User Flow

Since the purpose of our app is to reduce the amount of non-emergency 911 calls, we thoroughly analyzed how a user would progress through the app.

The landing page lists categories of potential issues that the user could be encountering. Once a category is selected, information will be provided and the user will be informed about whether their issue needs to be escalated. For instance, loud noises/parties should only be escalated if they are occurring after 11pm. At this stage, there is no person needed. Call-to-action buttons were inserted at the end to check if the user's request has been satisfied. If yes, the app would close. 

If not, an automated message gets sent. It prompts the users to provide more details on their situation. Simultaneously, a neighbourhood community watcher gets pinged that there is a potential problem in their area. They hop onto the chat and skim over the details the user provided. The user flow then splits into three possible scenarios:

  1. A report is filed. The community watcher asks the user for more information regarding their situation. The data is compiled into a PDF report and sent to the police to further investigate the issue; user also receives a copy of the report.
  2. Community watcher goes on site. The user will see the community watcher's exact location on their phone as they approach the scene.
  3. 911 is called. A first responder will be in contact with the user as soon as possible.


Our team delegated tasks and continued iterating on the designs while beginning development. The design process started with pen and paper, progressed to low fidelity wireframes, then concluded with high fidelity prototypes that were later translated into code. The prototype for the citizen's portal was built using React Native while the final mockups for the responder/community watcher portal were made using Invision, which can be viewed here.


Overall, this hackathon was an amazing learning experience for me as an aspiring product manager with interests in product design and front end development. There was a large emphasis on the "business case" for the police, and we were encouraged to think through our ideas and iterate multiple times before settling on a final solution. I also got to experience working with front/back end developers and a UI/UX designer in an agile environment, tinkering with the low and high fidelity prototypes, and using React Native to write code for the first time!