Devlog-2 Why I Want to Create ReliefLink. I live in Kerala.For us, floods and landslides aren’t just things we hear about in the news. They are situations we have seen happen around us. Living in a place that has faced these disasters gave me a reason to think about what technology could do when every second matters.When a disaster happens, everything can become chaotic very quickly.People need information. Families need help. Volunteers want to help but may not know where they are needed. Relief camps need resources. Emergency teams need to coordinate. And all of this is happening at the same time.In that kind of situation, getting the maximum amount of accurate information to the largest number of people as quickly as possible is not easy.Trying to create a structure in the middle of absolute chaos is even harder.But I think it’s worth trying.That is the idea behind ReliefLink.I want to build a system that can bring together emergency requests, volunteers, relief camps, resources, and important information in one place. The goal isn’t to eliminate the chaos of a disaster — because that isn’t realistic.The goal is to make the response to that chaos more organized.A disaster can change from one situation to another. A flood may require completely different resources from a landslide. A relief camp that exists today may not be the right one tomorrow. New requests will appear, priorities will change, and information will constantly need to be updated.That’s why I don’t want ReliefLink to be a static application.I want it to be something that can adapt to each disaster as it happens.I’m building ReliefLink not just to learn how to make an app, but to explore how software can be used to solve a real problem that is close to home.There is still a long way to go.