<aside> ❓ See the Architecture Guide for more information

</aside>

Techical

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

</aside>

• React.js, Next.js, emotionCSS, Prismic (CMS) for FE
• Node.js, Express.js, Postgres, Swagger for documentation
• Stakeholder already has a fully functional API collecting data from well sensors.
• Feature List — in prep for 1st Release Canvas (limited to Cambodia sensors):
  1. Admin tools
  2. Ticketing system
  3. Processing and retrieval of data

Android:

Material design

Data Architecture

<aside> 🚧 Data team members will want to document their data-related architectural decisions here, for reference.

</aside>

Mobile : Kotlin

Android SDK

MVVM pattern [model view viewmodel]

Coroutines [threading and retrofit]

Camera api

Google maps api

Picasso - download pics

Web:

https://dashboard.welldone.org/.netlify/functions/get_momo_status?id=${pump_id}

mapboxApiAccessToken

"https://api.mapbox.com/v4/mapbox.satellite/1/0/[email protected]?access_token=YOUR_MAPBOX_ACCESS_TOKEN"

Enities

I. Super_user ⇒

A. These types of users are well done staff

a. Can delete, add,edit organizations

b. Create organization_admin accounts to login

c. Create sensors

II. Organization_admin ⇒

A. These types of users are well done partners.

a. They can create pumps.

b. They can assign operators to pumps

c. They are able to create new operator accounts

d. They are able to see history of their pumps

e. They can receive alerts from pumps

f. Edit information. Assign operators to different pumps or more than one pump