Inside Mage’s Developer Experience Strategy: Competing Against Airflow Through Better UX

In infrastructure software, conventional wisdom suggests that reliability and feature completeness trump user experience. But in a recent episode of Category Visionaries, Tommy Dang revealed how Mage is challenging this assumption by making developer experience their primary differentiator against established players like Airflow.

The UX Gap

“As many people that use Airflow, I haven’t met one person that said they love working in Airflow,” Tommy observes. This insight revealed a crucial opportunity: while Airflow had proven the market for data pipeline tools, it had left the door open for a solution that developers would actually enjoy using.

Rethinking Data Pipeline UX

Mage’s approach to developer experience goes beyond surface-level improvements. “We take some of the best parts and then we revolutionize all the worst parts,” Tommy explains. Their strategy focuses on four key pillars:

1. Easy Developer Experience: Rather than accepting complexity as inevitable, Mage prioritizes intuitive interfaces and workflows.
2. Engineering Best Practices Built-In: “How that plays out is we actually enforce more of a modular pipeline,” Tommy shares. “As you build out your data pipeline, every step in your pipeline is an individual file.” This architectural choice makes pipelines more maintainable and testable.
3. Data as a First-Class Citizen: “All we do is data, movement of data, transformation of data,” Tommy explains. This focus allows them to build features specifically for data workflows, like versioning, partitioning, and backfilling.
4. Simplified Scaling: “We make it really simple for even one data engineer to manage thousands of pipelines,” Tommy notes, emphasizing their focus on operational efficiency.

Building Trust Through Design

For Mage, developer experience extends beyond the user interface. “Design is how things work and how things feel,” Tommy explains. “This can come from coding. How do you feel when you write code this way? Or how do you feel when you have to click a bunch of buttons to do something very simple?”

This holistic approach to design considers the entire developer journey, including what Tommy calls the “off-product” experience: “How do you feel when after you launch a data pipeline and you have to go to sleep and walk or go to lunch? Do you feel secure? Do you feel like you know that if something goes down, you’ll be notified?”

The Community Impact

Their focus on developer experience has catalyzed community growth. Since launching their open-source version, they’ve gathered over 2,000 GitHub stars and built a community of 400-500 Slack members. More importantly, developers are choosing to put Mage into production – the ultimate vote of confidence in infrastructure software.

Looking Forward

Mage’s vision extends beyond just being easier to use than Airflow. “We want to get to a place where everything is so easy, so smooth and so transparent that you even forget that we’re here,” Tommy shares. “We’re just in the behind the scenes doing all the plumbing for you and this just runs very smoothly.”

For B2B infrastructure founders, Mage’s approach offers a valuable lesson: even in technical markets where functionality is crucial, user experience can be a powerful differentiator. By making developer experience a core part of their product strategy rather than an afterthought, they’re proving that infrastructure software doesn’t have to be painful to use to be powerful.

This strategy suggests a broader shift in how we think about developer tools: perhaps the next wave of infrastructure companies won’t win just by having better technology, but by making that technology more accessible and enjoyable to use.