User Feedback Forced Us to Rethink Everything — Here’s What Changed

Julie Moore — Wed, 29 Jan 2025 03:47:37 +0000

User Feedback Forced Us to Rethink Everything — Here’s What Changed

The first version of Martini was built with a clear purpose: to help developers build APIs, integrate applications, manage data, and automate workflows without unnecessary complexity. We optimized for speed, efficiency, and flexibility, making it a powerful low-code tool for integration.

But the reality is, no matter how much thought you put into your product, real-world feedback will expose its blind spots. And that’s exactly what happened.

When we launched Martini v1, we heard from developers who appreciated the power of low-code services, but we also heard from teams that struggled with the learning curve. Some users felt Martini still had too much of a developer-first approach, making it difficult for non-technical stakeholders to collaborate effectively.

That feedback changed everything. We didn’t just tweak the product—we rethought how integration should work. And that led to Martini v2, with one major shift: Workflows.

Why Martini v1 Worked (But Had Its Limits)

The first iteration of Martini introduced low-code services as the foundation for automation and integration. Each service worked as a self-contained logic unit, defining inputs, applying transformations, and producing outputs. Developers could manage API calls, process data, and execute backend workflows—all within a visual yet structured environment.

For technical teams, this was great. But it wasn’t enough.

Even though Martini was low-code, it still felt like programming. That meant developers had to be involved in everything, which became a bottleneck. Enterprise teams told us they wanted:

A faster way to set up automations.
A tool that business users could understand.
More collaborative features to bridge the gap between developers and stakeholders.

Simply put: Martini needed a more intuitive, visual way to manage integration workflows.

The Shift: From Low-Code Services to Workflows

Enter Martini v2, and with it, Workflows—a completely new way to handle automation, data management, and API orchestration. Instead of requiring users to configure services like functions, Martini v2 lets them build entire processes visually.

Workflows represent real-world business logic as diagrams. Instead of configuring services one by one, users can map out a process from start to finish without writing code. Need to connect APIs? Automate approvals? Transform data between systems? With Workflows, all of that happens visually, making integration accessible to both developers and business teams.

This shift also means that developers don’t have to handle every automation request manually. Teams can work together—stakeholders define the process, while developers refine the logic where needed.

Workflows vs. Services: Do Developers Still Have Full Control?

Absolutely. Martini v2 doesn’t replace services—it enhances them. Services are still there for developers who prefer a more structured approach. But now, you don’t have to rely on them for everything.

Think of it this way:

If you’re building a complex API backend, services give you full control.
If you’re managing an approval process, syncing data between tools, or automating repetitive tasks, Workflows make it effortless.

And if you ever need to mix the two? No problem. You can call services from within a workflow or trigger a workflow from a service. Flexibility is the key.

What We Learned (And Why It Matters for Developers)

Looking back, the biggest lesson was that low-code isn’t just about writing less code—it’s about removing friction from the development process.

With Martini v1, many companies were stuck in a cycle where developers handled everything because the platform still felt too technical. That slowed down innovation. Now, with Workflows in Martini v2, teams can move faster, experiment more, and involve more people in building solutions.

For developers, this means:

Less time spent on basic automation requests—teams can handle them independently.
A smoother way to collaborate with non-technical users—without hand-holding.
More freedom to focus on building complex integrations and solving real engineering challenges.

What’s Next for Martini?

We see Martini v2 as a foundation for even bigger things. With Workflows now making integration more intuitive, we’re focusing on expanding its capabilities:

More automation features to reduce manual setup even further.
Pre-built connectors for faster integration with popular tools.
Scalability improvements to handle even larger data flows and API loads.

This isn’t just about improving low-code—it’s about redefining how integration should work in the modern enterprise.

DEV Community: Julie Moore

User Feedback Forced Us to Rethink Everything — Here’s What Changed

User Feedback Forced Us to Rethink Everything — Here’s What Changed

Why Martini v1 Worked (But Had Its Limits)

The Shift: From Low-Code Services to Workflows

Workflows vs. Services: Do Developers Still Have Full Control?

What We Learned (And Why It Matters for Developers)

What’s Next for Martini?