Butterfly

• 

  all the slides of the web app

Inspiration

The idea behind BUTTERFLY is that a small change in a project can have a much bigger impact than expected . A delay in one task can affect other tasks, shift deadlines, and create problems elsewhere in the plan. I wanted to explore how this process could be made easier to understand. Instead of just tracking tasks and deadlines, I wanted to create something that helps users see the possible consequences of a change , compare different scenarios , and figure out what they could do next. Also because I believe that, EVERY CHANGE MATTERS.

What it does

BUTTERFLY is a project change- impact and recovery assistant that helps users understand how changes can affect their plans. Users can explore project tasks, deadlines, dependencies, resources ,and budget ,stimulate changes and review their potential impact. The app also offers recovery suggestions and allows users to compare different scenarios to explore possible ways forward. The goal is to help users see how one change can affect an entire project and make more informed decisions about what to do next.

How we built it

I built butterfly as a web application, focusing on making project planning and change analysis easier to understand and navigate I bought together features, including a project dashboard task, independency views, changed, stimulator, impact analysis, recovery suggestions, scenario, comparison, and reports. I also used a sample project to demonstrate how these features work together. I developed distinct visual identity for the website, using a burgundy and coral colour palette and tagline. Every change matters. My aim was to make a potentially complicated planning tool feel clear, organise, and approachable

Challenges we ran into

Since I used lovable to build butterfly, a lot of challenges was figuring out how to get the features I wanted to work properly. I struggled with setting up the login functionality, getting the sample project working as intended and connecting my GitHub repository . I even had to restart the project around three times because I kept running into issues with the repository connection and set up that was a lot of trial and error, but the experience taught me to troubleshoot problems ,adapt when things didn't work ,and make the most of time I had during the hackathon.

Accomplishments that we're proud of

I am most proud of turning butterfly from an idea into an interactive prototype, especially the scenario, comparison feature which let's use compare different possible changes to a project. I also put a lot into the dashboard and the overall visual identity because I wanted to feel like a proper product, getting the website published and the demo ready after struggling with the project reset and GitHub connections made the final results especially rewarding.

What we learned

Before this hackathon, I thought building a website with AI would be relatively easy. I assume that once I had a clear idea and a prototype, I would take care of most of the work. I quickly realised how wrong I was. AI made it possible for me to build butterfly with getting it to work the way I envisioned required much more than simply giving it prompt. I had to review changes. Go through code. Identify issues. Revise things that didn't work and keep trying when the results weren't , what I expected. Moments when the frustration of trying to fix the same problem again and again was very real. This experience changed how I see AI. It's an incredibly useful tool, but it isn't a substitute for thinking, problem-solving or paying attention to the details. AI can help you build something, but you still need to understand what Building recognise something is wrong and keep working until you get closer to the result you want. I learned that I can make Building easier, but it doesn't make the process effort less.

What's next for Butterfly

I don't want butterfly to remain just a project. I want to keep developing it into something. People can genuinely use. My next step is to make the application organised and accessible and get feedback from people who try it so I can understand what works what doesn't and what needs to change. I want to use that feedback to make its impact analysis more precise, improve its intelligence and make its recommendations, more useful and real situations. There is still a lot. I want to improve and ,I see this as the beginning of a long project rather than the end of one.

Built With

• lovable
• react
• typescript
• webapp