Device integration
MQTT message path for client-selected physical trackers.
Anonymous connected-asset product
Construction Asset Tracking: GPS, IoT and MQTT
An end-to-end product path from physical GPS trackers and MQTT messages to Go services, APIs and a Vue.js map and administration experience.
Context
Physical equipment needed a usable operational view.
A construction-focused product needed to connect hardware trackers with a browser-based workspace for locating and administering assets.
The public case uses a synthetic flow only. It includes no customer name, device identifier, coordinate, real map, broker configuration or operational dataset.
Problem
Hardware events are useful only when the complete chain is dependable.
The product had to bridge constrained devices, asynchronous messages, backend state and an interface useful to operational users.
- 01
Tracker messages had to be consumed through the client’s MQTT environment and translated into application state.
- 02
The backend needed APIs and data handling suitable for map and administration workflows.
- 03
The frontend needed to make asset state understandable without exposing implementation complexity to users.
Approach and solution
Treat device, service and interface work as one delivery path.
The solution connected physical trackers through MQTT to Go services and application data, then exposed the required state through APIs to a Vue.js frontend.
Map and administration workflows were developed alongside backend behaviour so that message handling and user-visible state could be validated as one product path.
Role and responsibility
Nik’s role: most of the Vue.js frontend and Go backend.
Nik implemented most of the frontend and backend for the platform and integrated them with the client’s hardware trackers and MQTT broker.
The work required full-stack product judgement across asynchronous device data, API design, application state, mapping workflows and practical debugging.
Architecture and delivery
A traceable path from tracker signal to user action.
The diagram represents component boundaries, not a real customer deployment.
- 01
GPS trackers
Physical devices producing location and status signals
- 02
MQTT
Client hardware broker and asynchronous message flow
- 03
Go services
Message handling · domain logic · state processing
- 04
Data and APIs
Application persistence and browser-facing interfaces
- 05
Vue.js workspace
Synthetic map flow · asset views · administration
Delivery
Verified delivery scope.
Backend
Most of the Go service and API implementation.
Frontend
Most of the Vue.js map and administration experience.
Result and current status
A developed end-to-end connected-asset product path.
The engagement connected the hardware, messaging, service, data and interface layers required for the product’s core operational experience.
No fleet size, customer adoption or efficiency metric is published because those claims are not supported for public use.
Ways to work together
Three clear ways to move a difficult system forward.
Choose the smallest engagement that can produce a useful decision and a credible delivery path.
- 01
Operational Systems Assessment
A paid, time-boxed discovery producing a process and data map, visible risks and priorities, an architecture and delivery roadmap, and pragmatic next steps.
- 02
Build & Delivery Leadership
Senior technical direction with hands-on implementation of critical paths, aligning owners, operations, product, suppliers and engineering from decision to release.
- 03
Fractional Technical Partner
Ongoing technical leadership for roadmap, supplier and team coordination, architecture choices and continuous delivery improvement.
Next step
Connecting hardware events to a product people can operate?
We can map the device, messaging, service and user-workflow risks before delivery expands.