OWL Sentry
Pest-control monitoring across web and mobile
Project Overview
OWL Sentry connects IoT pest-control devices with a web dashboard for managers and a PWA for field technicians. Working from the client's brief and requirements, I designed both interfaces from scratch, including screens, reusable components, states and interactive flows for implementation in Mendix.
The Challenge
The challenge was to organise a large set of device data, filters, statuses and service functions into one coherent system. Managers needed an overview of devices, pest activity and field work, while technicians needed access to tasks and device details on mobile. The design also had to work within the platform, time and budget constraints discussed with the development team.
My work covered the dashboard and technician PWA. The marketing website was created separately. Product access requires a client account.
01
Design decision
Web dashboard
An overview first, details on demand
Managers needed to monitor device conditions, service activity and pest trends across multiple locations.
Combining figures with visual summaries
We considered a numbers-only view. I proposed graphical summaries to help distinguish the main information groups.
Each widget combines a key figure and percentage with a breakdown of related statuses. A separate chart below shows pest activity over time.
02
Design decision
Web dashboard
From status icons to device details
The device list had to show multiple conditions per device while giving managers access to detailed readings and past events.
Readings and history within reach
The aim was to keep detailed readings accessible from the device list and retain the device's identity when reviewing its event history.
03
Design decision
Web dashboard
Connecting device status and location
Managers needed to locate devices across sites and narrow the map to those reporting a particular condition.
Four groups for advanced filtering
Following discussions with the client, I simplified the advanced filters into four groups: action required, pests, electronics and service. The device list reflects this grouping through three category icons and a separate warning indicator. Map markers show device locations, while a popover summarises the selected device’s reported issues and provides access to its details.
04
Design decision
Technician PWA
Supporting fieldwork on mobile
The technician PWA combines scheduled work with tasks triggered by device reports. I organised task information, service tools and device details for use during field visits.
Keeping field tools close
Keep the information and tools needed for a service visit accessible throughout the technician’s work.
05
Design decision
Components & handoff
Consistency and handoff
The dashboard and technician PWA used separate component sets with shared icons. I designed component states and used the prototype to explain interaction behaviour to developers.
Making behaviour explicit for handoff
The aim was to reduce ambiguity during implementation discussions by making the intended appearance and response of key UI elements clear.
From tasks to device details
I connected key screens in Figma to communicate navigation, component states and transitions. The prototype shows how these interactions fit into the technician’s mobile workflow.
Watch prototype
Mobile PWA · 0:42
06
Project summary
Delivery & learnings
What I delivered and what I’d improve
Delivered
I delivered designs for the web dashboard and technician PWA, including screen states, reusable components and interactive flows for implementation in Mendix. My involvement ended at design handoff, so I don’t have post-launch performance data.
Feedback
Feedback from the client and developers was positive. The client liked the visual direction and proposed solutions, while developers particularly valued the scope delivered within the two-month timeline.
Looking back
With more time, I’d have organised the dashboard and PWA component sets more systematically, making components and their states easier to find and reuse.