Project Info
This project did not submit a demo video on Devpost.
Inspiration
Seeing that our state of California received record rainfall in the year 2022, we were inspired to analyze the effect this had on the "boom & bust" cycles that our state had been experiencing. This means that in the years following 2022, it was more likely that we would experience statistically lower levels of rainfall. To mitigate the effects of these cycles, researched methods like rainwater harvesting and wanted to promote them throughout the community.
What it does
The user is first directed to a website which provides information about rain water harvesting and techniques and overall data. There is also information about how to use the app and its functionalities. It is mainly used as a promotional tool for the actual application, which can be downloaded in the form of a zip file from the app. Upon launching the app, the user is prompted to enter their home's roof size and their current position in the form of latitude and longitude. These two data entries can also automatically be filled if location privacy settings are enabled. The app then presents a bar chart of rainfall by month for that location and metrics on how much they can save.
How we built it
We primarily used flutter SDK which was coded in google's Dart language. This made it easy to code the functionalities of the app along with the design elements. We also used HTML to create the website and Figma for the presentation + prototyping.
Challenges we ran into
We initially found difficulty in implementing the flutter SDK app launcher in the HTML code for the website and ultimately decided on having the user download the app and run it themselves in the form of a zip file. We also faced issues relating to the development of our app in general including limited scope and design elements.
Accomplishments we're proud of
We were proudly able to make use of and integrate climate data API's from the NOAA and successfully code an app in Dart, which is an app primarily used for google, while also being able to show up in IOS simulator, an apple product)
What we learned
We learned that using languages which are compatible with languages used to develop applications are important to use when coding websites. We also learned that developing programs in languages which are used primarily for applications will create problems when trying to integrate them on cross-platforms interfaces.
What's next
We want to make RainSaver an organization that is globally affected rather than only being affected by places in America. Another thing is that we want to see more plants growing, causing less floods and providing them efficient water. Collecting rain water should benefit both humans and plants.
This repository has no readme, or GitHub could not be reached.
Analysis
View
Metric
- 1
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- JavaIn code
- KotlinIn code
- CSSClaimed
- DartClaimed
- Node.jsClaimed
- PythonClaimed
2 of 6 appear in the indexed code. 4 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
8.2 KB
Source files
10
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
Arhi045/rainSaver
28 files · 79 KB · @ 16cd0b9
Structure
Interface
10 files · 36%Screens, components and styles rendered to the user.
Application logic
8 files · 29%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- XML63%
- Java18%
- YAML17%
- Kotlin2%
Share of indexed source by file size. Binary and vendored files are excluded.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.