Technical

<aside> 🚧 After doing technical research, return here to fill out the technical frameworks, platforms and other architectural decisions you resolve.

</aside>

Platforms

Web Browser
- Desktop
- Mobile

We believe most users will want to use a native iOS app. Without an iOS developer, however, the web team will likely start with a "mobile-first" approach to the web app. This might be difficult because this project is a build-on, but we will attempt to design with a mobile view in mind.

Back-end

Building the backend with NodeJS & Express framework
- Production Database
  - PostgreSQL - use best practices to ensure scalability and DRYness
- Development Database
  - SQLite3 - we will consider Postgres as an alternative in order to emulate a production environment and avoid issues when migrating from development to production
  - Docker - we will consider creating Postgres Docker containers to run queries against it to avoid issues with setting up Postgres locally (permission errors, etc.)
- Testing Frameworks
  - Jest
  - Supertest
  <aside> 💡 Do we need a special API request for how iOS deals with geo-location?
  
  </aside>

Dependencies

API Integrations

Needs some research on how to best achieve this.
- Not recommended — Building two separate API's. One for NodeJS backend and one for DS
- Flask API - create a Python web server and interact with the server with URLs.
- Using "child_process" package to call a Python function from node.js
API - FEATURES
- Getting a distance radius from user location to local fire
  - lat / long coords
  - distance radius
- Getting forest fire risk data for an area.

Front-end

<aside> 🚧 See the guide for more info on this section.

</aside>

Progressive Web App

ReactJS
- Hooks (functional instead of class components)
- Managing some state (e.g. user information and logged in status) with Context API
  - We agreed not to refactor using Redux because this would unnecessarily complicate our application