Inspiration
Current disaster warning systems only work with active cell service, this may not work in a disaster scenario.
What it does
Given the worsening environmental disasters, we developed a warning app. However, we were keen on creating something special that could genuinely provide assistance in emergency situations.
Our solution is a Peer-to-Peer app designed to reliably relay important messages even in the face of potential network failures. We achieved this by implementing Wi-Fi Direct. Instead of relying solely on conventional network connections, Wi-Fi Direct allows direct communication between devices, even when conventional mobile networks or the internet are unavailable.
How we built it
We developed an Android app that leverages Wi-Fi Direct to relay warnings, with an initial distribution of warnings. For this project, we opted for Jetpack Compose with Kotlin, as we chose Wi-Fi Direct over Bluetooth. The decision was primarily driven by the extended range that Wi-Fi Direct offers, a crucial factor in emergency situations. By opting for Wi-Fi Direct, we aimed to ensure that our app could cover larger areas, enhancing its effectiveness in transmitting critical warnings where conventional network infrastructure might be compromised. This decision aligns with our commitment to providing a reliable and robust solution for communication during environmental emergencies.
Challenges we ran into
Choosing a Peer-to-Peer Technology: Selecting the right peer-to-peer technology was a pivotal decision that demanded careful consideration. With various options available, each with its strengths and weaknesses, reaching a consensus on the most suitable technology was a challenge in itself. The diverse preferences and expertise within the team added complexity to the decision-making process.
Implementing in an almost Unfamiliar Language: What also added an extra layer of complexity, we decided to implement our solution in a language that none of us were particularly familiar with. While this choice introduced a learning curve for the entire team, it also provided an exciting opportunity to broaden our skill set. Navigating through the intricacies of a less-familiar language required collaborative problem-solving and a shared commitment to learning on the fly.
Accomplishments that we're proud of
Our alternative approach
What we learned
Android Development, Diffrence between peer to peer technolagies
What's next for PeerGuard
As we envision the future of PeerGuard, several exciting developments are on the horizon, aimed at enhancing its functionality and effectiveness:
Integration of Map Services and Offline Maps: Our next step involves incorporating map services into PeerGuard, providing users with a visual representation of emergency situations. Additionally, we plan to enable the download of offline maps, ensuring that crucial information remains accessible even in areas with limited connectivity.
Weather API Integration: To offer more comprehensive alerts, we intend to integrate weather APIs into PeerGuard. This enhancement will empower users with real-time weather information, enabling them to make informed decisions during emergencies.
Certificates for Authorized Personnel: Recognizing the importance of reliable information distribution, we plan to implement a certificate system. Authorized personnel will be granted certificates, allowing them to send out alerts. This ensures that the information disseminated through PeerGuard comes from verified and trusted sources.
Further Development of Peer-to-Peer Connection: To bolster the stability and resilience of PeerGuard, our focus will remain on the continuous improvement of the peer-to-peer connection. We aim to refine and optimize this feature to ensure seamless communication even in challenging network conditions.
Built With
- jetpackcompose
- kotlin
- wifi-direct
Log in or sign up for Devpost to join the conversation.