Mobile appInductive Automation Ignition (MES/SCADA) Agent view

How to add a mobile app to Ignition (MES/SCADA)

Short answer

For most plants the mobile app is a Perspective project served from the Gateway and opened on phones and tablets, using camera scanning for barcodes. A native or PWA wrapper over Web Dev or REST endpoints is only needed for strong offline work or device features Perspective does not cover.

Ignition is unusual among MES and SCADA platforms because mobile is a first-class target. Perspective is built on web technology and is designed to run in a browser or the Perspective mobile app on phones and tablets, with responsive layouts. Many teams discover they do not need a separate app at all: they need a well-designed mobile Perspective project with the right screens for operators and maintenance staff.

The harder questions come when the requirement is more than a screen. Warehouse and kitting staff want barcode scanning with a hardware scanner or camera, field technicians go to remote pump stations with poor connectivity, and quality inspectors want to attach photos and signatures to a record. Each of these has a native answer inside Perspective, a workaround, or a clear point where a custom app makes sense.

Because the Gateway is the single place where security, tags and SQL access are enforced, a mobile app is also an exposure decision. Making a Gateway reachable from phones outside the plant network is a different risk profile from a screen on a wired HMI, and it drives the VPN, reverse proxy or identity provider design more than any UI choice.

What teams use it for

Operator downtime and scrap entry on tablets

Line tablets run a Perspective page for reason codes, scrap counts and notes, writing to MES tables with the operator's identity.

Maintenance rounds and inspections

Technicians walk a route, scan an asset tag, record readings and photos, and the app creates a work request if a reading is out of range.

Material moves with barcode scanning

Staff scan a pallet and a location label to record a move, with lot and quantity validated against SQL before posting.

Supervisor approvals and alarm triage

Supervisors see active alarms, acknowledge, and approve shift events from a phone while walking the floor.

Remote site visits

Field staff at remote sites check tag values and sign off visits, with queued entries pushed when they reconnect.

Visitor and contractor sign-in tied to area permits

Contractors register through a mobile page and the record links to permit and lockout state held in SQL.

Inductive Automation Ignition (MES/SCADA) integration surface

  • Perspective module: responsive browser-based sessions and a mobile app, with camera and some device features exposed through components or scripting; exact capabilities depend on the Ignition version.
  • Barcode and QR scanning options, including camera-based components in Perspective or keyboard-wedge Bluetooth scanners typing into focused fields.
  • Web Dev module REST-style endpoints and Gateway scripting for a native or PWA client that cannot use Perspective sessions.
  • Gateway security zones, identity providers (OpenID Connect or SAML) and roles, which govern what a mobile user can see and write.
  • SQL Bridge and Named Queries for transactional writes from scans, with Perspective session tags for user and location context.

How it works

  1. 1

    Start with Perspective mobile

    Build task-focused pages with large touch targets, and test on the actual devices and browsers your staff carry, not just a desktop emulator.

  2. 2

    Pick the scanning method

    Bluetooth or rugged-device scanners that act as a keyboard are the most robust. Camera scanning is convenient but depends on lighting, label quality and the device.

  3. 3

    Design the access path

    Decide between plant Wi-Fi only, VPN, or a reverse proxy with an identity provider. Never put the Gateway directly on the internet.

  4. 4

    Validate every scan server-side

    Use Named Queries to check lot, location and work order before posting. Return clear errors the user can act on.

  5. 5

    Plan for offline

    Perspective requires a connection to the Gateway. If offline operation is essential, build a PWA or native client with a local queue and idempotent endpoints on the Gateway.

  6. 6

    Roll out with device management

    Use MDM, kiosk modes and per-role pages, and monitor sessions and errors from the Gateway status pages.

Example flows

Pallet move by scan

Trigger: A forklift driver scans a pallet label on a rugged handheld.

  1. The Perspective page receives the scanned lot into the focused field.
  2. A Named Query validates the lot and its current location.
  3. The driver scans the destination location label.
  4. The move posts in a transaction and the screen confirms the new location.

Result: Inventory location in the MES schema updates within seconds, with the user recorded.

Maintenance round with photo

Trigger: A technician starts a route on a phone.

  1. They scan the asset QR code and enter a vibration reading.
  2. The reading exceeds a limit, so the page prompts for a photo and note.
  3. The submission writes a record and triggers a notification to the maintenance lead.

Result: An out-of-range reading becomes a tracked request with evidence.

Keeping data on-prem

Perspective sessions are served by your own Gateway, so the application and data stay on-prem by default. The decision is how phones reach it. Keep devices on plant Wi-Fi or a VPN, or publish through a reverse proxy in the DMZ with single sign-on and device checks. For sites with sensitive data, add a local language model service for voice-to-text notes or a helper that fills forms from a photo, hosted on a GPU in the plant and called by the Gateway, so recordings and images do not go to public cloud services.

Security checklist

  • Authenticate through your identity provider with multi-factor, and map roles to Perspective security levels.
  • Do not expose the Gateway port to the internet; use VPN or a hardened reverse proxy.
  • Treat every scan and form value as untrusted input and validate in Named Queries.
  • Restrict mobile roles to the MES writes they need and block tag writes to control values.
  • Use MDM to wipe or lock lost devices and prevent saved credentials on shared tablets.

Ways to get it done

Perspective project used in a mobile browser or the Perspective app

Effort: Days to a few weeks per screen set.

Most operator, supervisor and maintenance use cases with reliable plant Wi-Fi.

PWA or native app over Web Dev endpoints with a local offline queue

Effort: Two to four months with testing on real devices.

Remote sites, basements and plants with poor coverage or special hardware.

Partner-led design with an assistant for voice and photo capture

Effort: Scoped per site; Netray can build the assistant while your integrator owns the Perspective screens.

Teams that want hands-free entry and guided forms, running models on-prem.

Pitfalls

  • !Desktop-sized Perspective views shrunk onto a phone are slow to use; design separate mobile layouts.
  • !Camera scanning on glossy or damaged labels is unreliable, so keep hardware scanners as a fallback.
  • !Dropped Wi-Fi mid-transaction can cause duplicate submits; make writes idempotent with a client-generated ID.
  • !Session count and licensing can surprise teams as mobile use grows; check Gateway capacity and licence terms.
  • !Caching assumptions from a native app do not apply to Perspective, which depends on a live Gateway connection.

Frequently asked questions

Does Ignition have a mobile app?

Yes, in practice through Perspective. Perspective pages run in a mobile browser and in a Perspective mobile app, with responsive layouts. Capabilities such as camera access differ by version and device, so test on your own hardware.

Can Perspective work offline?

Not in the way a native app can. Perspective sessions depend on a connection to the Gateway. For true offline use, build a PWA or native client with a local queue that syncs through Web Dev or REST endpoints when connectivity returns.

How do I scan barcodes?

The most dependable method is a Bluetooth or rugged-device scanner that types into a focused Perspective field. Camera-based scanning is possible in some setups but depends on version, device and label quality. Validate every scan in a Named Query.

Is it safe to let phones reach the Gateway?

It can be, with discipline. Use VPN or a reverse proxy with SSO and device controls, restrict roles, and never publish the Gateway directly. Treat mobile access as a separate security review item rather than an extension of the HMI network.

When do I need a custom native app?

When you need robust offline work, deep device integration, background sync or a very specialised scanner workflow. For most operator and maintenance tasks on reliable Wi-Fi, a well designed Perspective mobile project is faster to build and easier to maintain.

Want Mobile app working on your Inductive Automation Ignition (MES/SCADA)?

A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.

Get a free assessment