## Inspiration

The inspiration for our project stemmed from a mild, first-world frustration with modern weather websites. Sure, one glance at the temperature can tell you a lot about the weather, but there are so many other factors that we commonly ignore which can also affect our day. What if it's unbearably humid? Or, what if there's an on-and-off chance of rain throughout the day and you don't know how to prepare? These questions and more led us to develop a web application that not only provides you with your typical hourly forecast, but also processes that data into more meaningful and digestible information about your day.

## What it does

Our application first retrieves an hourly forecast from OpenWeatherMap's One-Call API. It displays the forecast for the next 12 hours on the left side of the webpage, and it also processes the raw weather data into simpler chunks. Each chunk contains highlights about the weather for a three-hour interval, and dynamically provides advice on how to best prepare for the day.

## How we built it

We used ReactJS and the React-Bootstrap library for the frontend of our application. For the backend, we used Node.js, Axios for API requests, and OpenWeatherMap's APIs.

## Challenges we ran into

The most difficult portion of our project was processing the data from each API call. This was the first time that any of us have worked with APIs, so finding the right data, refining it, using it efficiently, and displaying it was a hurdle in our workload. In addition to this, we had to complete lots of research on how to prepare for different types of severe weather conditions which also occupied a large portion of our time.

## Accomplishments that we're proud of and what we learned

We are very proud that we started this project with little knowledge about APIs, and in the end, we were able to manipulate the API data however we liked. We are also proud of the sleek, single-page design of our application and its overall aesthetic.

## What's next for Smart Day

Given the time constraints, we were not able to fulfill some of our goals. The next steps for our project includes reverse geocoding the user's location to display their city/region, allowing the user to select their location from a database, and displaying a larger variety of tips for different weather conditions.
## Inspiration

* weather.com icons that show up when you google the weather

## What it does

* Calls an API to that returns the weather information for a particular day

## How I built it

* In JS/React

## Challenges I ran into

* There was a lot of React/JS syntax/infrastructure that I was not familiar with that I learned.

## Accomplishments that I'm proud of

* Learned how to use API's

## What I learned

* How to use an API
* Improved React Skills

## What's next for The Weather App

* I can improve the UI
* I can have the images accurately represent the weather
## Inspiration

An article that was published last month by the CBC talked about CRA phone scams.
The article said that “Thousands of Canadians had been scammed over the past several years, at an estimated cost of more than $10 million dollars, falling prey to the dozens of call centers using the same scheme.”
We realized that we had to protect consumers and those not as informed.

## The app

We created a mobile app that warns users about incoming SMS or Phone fraud from scam numbers.
The mobile app as well offers a playback function so users can learn what scam calls sound like.

Alongside the mobile app we built a website that provides information on scamming and allows users to query to see if a number is a scam number.

## How it works

The PBX server gets an incoming phone call or SMS from a scamming bot and records/saves the information. Afterwards the data is fed into a trained classifier so that it can be determined as scam or not scam. If the sender was a scammer, they're entered into the Postgresql database to later be queried over HTTP. The extensions from here are endless. API's, User applications, Blacklisting etc . . .

## Challenges we ran into

At first, we were going to build a react native application. However, Apple does not support the retrieval of incoming call phone numbers so we defaulted to a android application instead. FreePBX runs PHP 5 which is either deprecated or near deprecation. We as well originally tried to use Postgresql for FreePBX but had to use MySQL instead. PBX call recording was not achieved unfortunately.

## Accomplishments that we're proud of

* Setting up FreePBX
* Finished Website
* Finished App
* Broadcast Receiver

## What we learned

* FreePBX
* NGINX
* Android Media Player

## What's next for Tenty

* Full SMS support
* Distributed PBX network to increase data input
* API for Financial Institutions, and or those affiliated with what is being scammed. Allowing them to protect their customers.
* Assisting Governments in catching scammers.