## Inspiration

This was inspired from an article we read about the impact mobile devices were making in third world countries, such as Africa. Mobile development in these countries are increasing by the second and we wanted to take part in that development.

## What it does

This app allows users to get answers to a large variety of questions at almost any time. This is achieved through the use of the Twilio and Wolfram API. A user can text the application a question such as; integrate x^2, 2+4, plot(logx), what time is it, etc. Users can also ask for some dictionary definitions such as economics, ball, and H2O for example. This is all done by making a request to Wolfram and parsing the data into a readable sms or mms message.

## How I built it

This was built by running a server with node.js/express and having it listen for a POST request done by Twilio. The server will use the query given in the body of the text to make a request to the Wolfram API and it will then parse the data and send it back as a sms message. Depending on if there is an image it may send a mms message instead.

## Challenges I ran into

Twilio was a little difficult to get running, although the initial messaging was not too hard it was difficult to have a message sent back with authentication because it required many things to be setup. Parsing the data and displaying it in a proper format for the response also took some time because Wolfram can send back a lot of data that may not be relevant.

## Accomplishments that I'm proud of

I am pretty proud that we were able to get this application running because offline services is something that I've never worked with before and I always thought was pretty cool. In fact just getting Twilio to work with the server and being able to have it send pictures was pretty amazing.

## What I learned

Wolfram actually knows everything. The wolfram request can be amazingly broad, initially we thought we would need to tap into multiple APIs to get a broader range of data, but after further investigation we realized that Wolfram actually covers a pretty large variety of topics. I also learned a lot about the Twilio API and how to connect Twilio services with server.

## What's next for AnswerMeThis

Increase the amount of data that is being sent and further improve the response speed, as well as improving visualization of the data. We also want tap into other APIs to give users a broader range of topics to choose from.
## Inspiration

With the effects of climate change becoming more and more apparent, we wanted to make a tool that allows users to stay informed on current climate events and stay safe by being warned of nearby climate warnings.

## What it does

Our web app has two functions. One of the functions is to show a map of the entire world that displays markers on locations of current climate events like hurricanes, wildfires, etc. The other function allows users to submit their phone numbers to us, which subscribes the user to regular SMS updates through Twilio if there are any dangerous climate events in their vicinity. This SMS update is sent regardless of whether the user has the app open or not, allowing users to be sure that they will get the latest updates in case of any severe or dangerous weather patterns.

## How we built it

We used Angular to build our frontend. With that, we used the Google Maps API to show the world map along with markers, with information we got from our server. The server gets this climate data from the NASA EONET API. The server also uses Twilio along with Google Firebase to allow users to sign up and receive text message updates about severe climate events in their vicinity (within 50km).

## Challenges we ran into

For the front end, one of the biggest challenges was the markers on the map. Not only, did we need to place markers on many different climate event locations, but we wanted the markers to have different icons based on weather events. We also wanted to be able to filter the marker types for a better user experience. For the back end, we had challenges to figure out Twilio to be able to text users, Google firebase for user sign-in, and MongoDB for database operation. Using these tools was a challenge at first because this was our first time using these tools. We also ran into problems trying to accurately calculate a user's vicinity to current events due to the complex nature of geographical math, but after a lot of number crunching, and the use of a helpful library, we were accurately able to determine if any given event is within 50km of a users position based solely on the coordiantes.

## Accomplishments that we're proud of

We are really proud to make an app that not only informs users but can also help them in dangerous situations. We are also proud of ourselves for finding solutions to the tough technical challenges we ran into.

## What we learned

We learned how to use all the different tools that we used for the first time while making this project. We also refined our front-end and back-end experience and knowledge.

## What's next for Natural Event Tracker

We want to perhaps make the map run faster and have more features for the user, like more information, etc. We also are interested in finding more ways to help our users stay safer during future climate events that they may experience.
## Inspiration

Billmastr was inspired by the team's quarantine hobbies. We were brainstorming and realized we had one quarantine activity in common. This is the high usage of streaming subscription services. We want to build an app to manage all the subscription services for users so that we can continue this activity while making wiser financial decisions.

## What it does

Billmastr assists users in better managing their subscription services. It has three features.
The first is to provide an overview of spending for the user - such as total spending on subscription services per month, spending in each category of subscriptions, and how the spending compares to past months.
The second feature is to provide easy access to manage all the subscriptions at once. Users can view all their subscriptions on this tab and spending for each specific subscription. There is a link to each app should the user wish to alter their subscription.
The last feature is notifying users when subscription bills are coming due. In the notification tab, the app also sends out a personal finance tip of the day every day to inform users of best budgeting practices.

## How we built it

This app was built with Angular. Heather put together prototype screens in Figma and researched the business question on hand, while Erika developed the logic and styling.

## Challenges we ran into

Our biggest challenge was to distinguish this app from similar apps that already exist. Although we were not able to implement it in the timespan of the hackathon, we decided that we would like to add household bill-type expenses to the app, so users can track their usage of their utilities, as well as more commonly regarded subscription services. This way, users can track all their consistent monthly costs in one app, whether they are essential or a luxury.

## Accomplishments that we're proud of

This was our first time building an app from scratch and we're happy that we were able to put together a presentable product for this hackathon.

## What we learned

From a technical perspective, we learned a lot about the features of Angular such as routing and navigation, as well as styling in HTML and SCSS. From a business perspective, we looked at many similar apps and their designs to get a better idea of how to create a user-friendly end product.

## What's next for Billmastr

Currently, our application has a high focus on billing and spending, but we want to get into user usage patterns.
We may get into other subscription-like bills, such as variable monthly bills (e.g. hydro, wifi, phone bills).
We also do not have a designer on the team, so we'd love to make Billmastr easier to use and easier on the eyes.