Amina didn’t think about global goals or digital transformation when her online class stopped loading. She just stared at her phone, watching the screen freeze again and again, until she finally closed the app.

On the other side of the world—or maybe just in a different part of the same country—someone like Rahim was working on that very app. Fixing bugs. Shipping updates. Meeting deadlines.

He wasn’t thinking about Amina either.

And that’s the strange thing about software development: the people writing the code and the people living with it rarely meet. But their lives are still connected.

When Code Reaches Beyond the Screen

We like to think of software as something technical. Clean architecture, efficient logic, good UI. But the truth is, software quietly decides who gets access and who doesn’t.

A fast internet connection? The app works great.
An older phone? Maybe not.
Limited data? Good luck.

None of those decisions are accidental. They come from priorities—what gets optimized, what gets ignored.

Rahim started noticing something off in the analytics dashboard. Users from certain regions were dropping out almost immediately. At first, it looked like a typical metric problem. Low engagement. Poor retention.

But it wasn’t that simple.

The Moment Things Shift

Instead of brushing it aside, Rahim asked a basic question: What if the problem isn’t the users?

That question changed the direction of the conversation.

The app was heavy. It needed constant internet. It wasn’t built for unstable connections. In short, it worked perfectly—for people who didn’t struggle with access.

So the team tried something different. They stripped the app down. Made it lighter. Allowed some features to work offline. It wasn’t flashy, and it didn’t win any design awards.

But it worked better for people like Amina.

This Is What SDGs Look Like in Real Life

You won’t always see labels like “SDG 4” or “SDG 10” inside a codebase. No one writes comments saying // reducing inequality here.

But that’s exactly what’s happening in moments like this.

• When an app works on low-end devices, it quietly supports education.
• When a platform is accessible to people with disabilities, it reduces exclusion.
• When systems are optimized to use less energy, they contribute—however slightly—to climate action.

Not in a dramatic, world-saving way. Just in small, steady improvements.

The Part We Don’t Talk About Enough

A lot of development is driven by pressure—deadlines, features, business goals. It’s easy to focus only on what’s measurable: clicks, time spent, conversions.

What’s harder to measure is who got left out.

Rahim’s suggestion didn’t immediately excite everyone. It sounded like extra work for users who weren’t even the “main market.” But over time, something interesting happened. More people started using the app. Places that were previously silent on the map began to show activity.

Turns out, inclusion isn’t just ethical. It’s practical.