Nearly 1.5 Million Views, Zero AI or Code: 5 Lessons from Building the Wildfire Map

During Israel’s Memorial and Independence Day in 2025, a wave of wildfires broke out — especially around the Jerusalem hills — forcing evacuations, road closures, and widespread concern.

With no official real-time map available, I built one .

Nearly 1.5 Million Views, Zero AI or Code: 5 Lessons from Building the Wildfire Map

In an era where every project boasts algorithms and artificial intelligence, it was surprising to see how something so simple — without a single line of code or any AI — managed to generate massive interest, cross a million views, and make headlines on major news sites (Mako, Ynet).

The goal was clear:
To provide an up-to-date geographic snapshot of all the wildfires raging across Israel on the eve of Independence Day.

Why?
Because as a concerned citizen, you want a clear picture of what’s going on — but I couldn’t find a single official or government website that offered this.

How?
By consistently scanning the web and receiving updates from people on the ground. That’s it.

It was intense and fast-paced — but I managed to learn 5 key lessons from this wild experience:

1. Create Without a “Title”

I’m not an expert in disaster management, crisis response, or mapping. But that didn’t stop the project. See a problem or challenge? Don’t let a lack of experience or an official “title” stop you. Take initiative and learn as you go.

2. Pre-Built Distribution Channels Make All the Difference

Without accessible, strong distribution channels, the map wouldn’t have reached so many people. My Telegram channel (with over 15,000 subscribers) was the immediate force that launched and spread it. If you’re building something — think about distribution.

💡 Pro tip: Start building your distribution channels today — for the project you’ll launch tomorrow.

3. Community Is a Superpower

The true strength of the map came from the community — both physical and digital. People sent me direct reports of wildfires, and I was constantly searching for updates online. It demanded total attention, but that’s what kept the map alive and accurate.

4. Listen — and Respond Fast

I’m no UX expert, so I simply listened. Colors? Icons? A legend? Every piece of feedback was implemented in real time. A key lesson: if you’re building something dynamic, your ability to adapt quickly is critical.

5. Real Value Isn’t About Features

The most meaningful feedback I got was from people who said the map helped them avoid danger or better understand what was going on. That meant more than any feature ever could.

💡 Pro tip: Don’t try to impress — try to help.

This post is a simple reminder:
Even without AI, code, budget, or infrastructure — if you see something missing, something that can meet a real need — just build it.

[image error]