· 5 min read

Why the WebDev Module is Ignition's Best-Kept Secret

Perspective gets the spotlight, but WebDev gives you full control. Here's why serious developers prefer it for dashboards and portals.

WebDev Module Ignition Opinion

If you've been in the Ignition ecosystem for any length of time, you've heard of Perspective. It's Inductive Automation's flagship visualization module — mobile-first, drag-and-drop, the default recommendation for nearly every new project.

And Perspective is good. For a lot of use cases, it's exactly the right tool.

But there's another module that's been quietly powering some of the most impressive dashboards and integrations in the Ignition world — and it rarely gets the attention it deserves.

The WebDev module.

What the WebDev Module Actually Does

At its core, the WebDev module lets you program directly against the web server inside your Ignition Gateway. That means you can:

  • Build REST APIs that let external systems (ERPs, MES platforms, mobile apps) read and write data through Ignition
  • Create custom dashboards using standard HTML, CSS, and JavaScript — served right from the Gateway
  • Expose data endpoints that return JSON for tag values, database queries, alarm states, or anything else you can script
  • Receive webhooks from external services and trigger actions in Ignition
  • Serve files — reports, images, documents — directly from the Gateway filesystem

Everything runs in Gateway scope with full access to system.db, system.tag, system.alarm, and the rest of the Ignition scripting API. Your resources mount under /system/webdev/{project}/{resource} and are accessible from any device on the network.

So Why Doesn't Everyone Use It?

Two reasons, and they're both fair:

1. It requires web development knowledge. Inductive Automation's own documentation says it plainly: "The Web Dev module requires specialized web-programming knowledge." If your team isn't comfortable with HTML, CSS, JavaScript, and REST API design, the learning curve is steep.

2. Perspective is "good enough" for most things. When you need a quick operator screen or a mobile-responsive view of a process, Perspective gets you there faster. Drag, drop, bind, done.

But "good enough" and "great" aren't the same thing. And the gap between them matters more than most people think.

Where WebDev Wins — And It's Not Close

Full Design Control

Perspective gives you components. WebDev gives you a canvas.

When you build a dashboard with WebDev, you're writing real HTML and CSS. That means you can design exactly the interface your operators need — not the one that Perspective's component library happens to support. Custom charts, animated SVGs, complex multi-panel layouts, real-time updating cards that look like they belong in a modern SaaS application.

If you've ever fought with Perspective's flex container trying to get a layout that "should be simple" to actually work, you know the pain. With WebDev, CSS Flexbox and Grid just... work. Because they're CSS Flexbox and Grid.

Performance on Large Displays

Here's something most people discover the hard way: Perspective has overhead. The session model, the component bindings, the WebSocket communication layer — it all adds up. On a factory floor display that needs to show 200+ data points updating in real time, Perspective can struggle.

A well-built WebDev dashboard fetches data via lightweight JSON endpoints and updates the DOM directly. No session state. No component lifecycle. Just fast.

We've seen factory floor dashboards go from 5-second load times in Perspective to sub-second with WebDev. On a 24/7 production line, that difference matters.

TV Dashboards and Kiosk Displays

This is the killer use case. Every manufacturing plant has TVs on the floor showing production stats. Perspective works for this, but it has quirks — session timeouts, authentication prompts, occasional reconnect issues.

WebDev dashboards are just web pages. Open the URL in Chrome, full-screen it, walk away. They don't maintain sessions, they don't time out, and they poll for data on their own schedule. Set it and forget it.

Integration Is a First-Class Feature

Need your ERP to push work orders into Ignition? Write a doPost endpoint. Need a mobile app to pull quality data? Write a doGet endpoint that returns JSON. Need to receive webhook notifications from a cloud service? Same thing.

WebDev turns your Ignition Gateway into a proper API server. And in a world where every system needs to talk to every other system, that's incredibly valuable. 

# Example: A simple REST endpoint for machine status
def doGet(request, session):
    line = request['params'].get('line', 'all')

    if line == 'all':
        query = "SELECT machine_id, status, oee FROM machine_status"
        data = system.db.runQuery(query, "production_db")
    else:
        query = "SELECT machine_id, status, oee FROM machine_status WHERE line = ?"
        data = system.db.runPrepQuery(query, [line], "production_db")

    rows = []
    for row in system.dataset.toPyDataSet(data):
        rows.append({
            "machine": row["machine_id"],
            "status": row["status"],
            "oee": float(row["oee"])
        })

    return {"json": {"machines": rows, "count": len(rows)}}

That's it. A clean JSON API for machine status, queryable by line, running directly on your Gateway. Any device on the network can consume it.

When to Stick with Perspective

WebDev isn't a replacement for Perspective — it's a complement. Here's when Perspective is still the right call:

  • Operator interaction screens — forms, buttons, controls that write back to tags or databases
  • Quick prototyping — when you need something functional in hours, not days
  • Teams without web dev skills — if nobody on staff knows HTML/CSS/JS, Perspective's visual designer is the pragmatic choice
  • Session-aware features — user-specific views, role-based content, authentication-gated screens

The best Ignition deployments use both. Perspective for operator screens and interactive workstations. WebDev for floor displays, executive dashboards, API integrations, and anywhere you need pixel-perfect design or raw performance.

The Real Barrier Isn't Technical

Here's the thing most integrators won't tell you: the reason WebDev dashboards aren't more common isn't that they're worse. It's that they require a different skillset.

Most Ignition integrators are control engineers who learned Perspective because it's part of the platform. They're great at PLC logic, tag configuration, and Perspective views. But building a responsive, modern web dashboard from scratch? That's web development — and it's a different discipline.

This is exactly the gap we fill at ModernHMI. We combine deep Ignition expertise with modern web development skills to build dashboards that actually look and perform like the software your team uses everywhere else in their lives.

Because the best dashboard isn't the one with the most features. It's the one people actually look at.

Curious whether WebDev is right for your environment? We'll tell you straight — sometimes Perspective is the better call, and we'll say so. Take the free readiness check and find out in 2 minutes.