Solutions
Cutting-edge solutions tailored to everyday issues in the modern digital environment.
Services
Innovative tools and services designed to address complex challenges today’s digital landscape.
IT FOR What WE DO MENU
Services
Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.
IT FOR HOW WE DO MENU
Services
Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.
Ready to clean up your CRM workflow?
Book a CRM Workflow Audit and see where leads, follow-ups, reporting, or disconnected tools can be fixed first.
Connected IoT Device Platform
Software that connects a water-focused smart device to the people who use it, from first pairing to everyday use.
Business goals
The client makes a connected device in the water category. Hardware alone doesn't deliver the value a smart product promises. Customers expect to pair it easily, see what it's doing on their phone and get updates without sending it back. The client needed software that made the device and its data useful every day, plus tools that would let its own team support products already in customers' hands.
Project overview
Hexagon built the software around the client's IoT devices. That includes the connection between device and phone, companion apps, a cloud backend that receives and stores device data, and an admin console for the client's team. Users pair a device, see its readings and status, and receive alerts. Staff can look up devices, check their status and manage firmware releases from one place.
Challenges faced and solved
A connected product is judged on its worst moment, which is usually the pairing screen or a dropped connection.
Setup that loses people in the first minutes
A customer unboxes a device, opens the app and expects it to work. If pairing fails or the steps are confusing, the next stop is a support call or a return.
We built a guided pairing flow in the app that walks the user through each step and says clearly what to do when a connection fails.
Devices don't stay online
Water products get used in kitchens, bags and outdoor spots with patchy signal. Readings taken while disconnected can vanish, which leaves users with gaps and doubts about the numbers.
We designed the data flow around interruptions. Readings are held until a connection returns, then sent to the backend, so a dropped signal doesn't have to mean lost history.
Raw readings mean little to a user
A sensor produces a stream of values that only an engineer would love. People want to know a plain answer: is it working, what has changed, and do I need to act?
We turned device data into status cards, history views and alerts inside the app, written in terms a non-technical owner can act on.
Support is blind once a device ships
When a customer calls, the support team can't see the product in their hand. Without device records, every problem starts with guesswork and a long list of questions.
We gave the client's team an admin console showing each registered device with its owner, status and firmware version, so conversations start from facts.
Features
| Feature | Description |
|---|---|
| Device owners | |
| 1. Account and Sign-In | Owners create an account that ties their devices and data together across phones. |
| 2. Guided Pairing | Step-by-step screens connect a new device to the app, which is the moment most connected products win or lose a customer. |
| 3. Device Dashboard | A home screen shows current status and latest readings at a glance. |
| 4. Usage History | Past readings are charted over time, so an owner can see patterns and not only today's number. |
| 5. Alerts and Reminders | Push notifications flag conditions that need attention, so owners don't have to keep checking the app. |
| 6. Device Settings | Owners adjust preferences and rename a device from their phone. |
| 7. Multiple Devices | One account can hold more than one device, which suits households and repeat buyers. |
| 8. Firmware Update Prompts | The app tells the owner when an update is ready and guides them through installing it. |
| 9. Help and Troubleshooting | In-app guidance covers common connection and care questions before a customer needs to call. |
| Device and cloud | |
| 10. Secure Device Registration | Each unit is registered against a unique identity, so data reaches the right account. |
| 11. Data Ingestion | The backend receives readings from devices and stores them against the correct unit. |
| 12. Offline Sync | Readings wait on the device or phone until a connection returns, which protects the owner's history. |
| 13. Firmware Delivery | Updates can reach devices already in the field, so improvements don't require a product return. |
| 14. Device Health Signals | Battery and connection status are reported back, which helps identify faults early. |
| Client team | |
| 15. Device Registry | Staff can look up any registered unit along with its owner, status and firmware version. |
| 16. Customer Lookup | Support finds a customer and their devices quickly, which shortens the back-and-forth on a call. |
| 17. Firmware Release Management | Staff choose which version goes out, which keeps rollouts under control. |
| 18. Fleet Reports | Reports across devices show activation and activity, helping the team see how the product is used. |
How the platform is put together
Each layer has one job.
The result
The client's devices gained a software layer that connects hardware, owners and the team supporting them.
| Area | Before | After |
|---|---|---|
| First use | A device with no companion experience | Guided pairing in a mobile app |
| Seeing device data | Readings stayed with the device | Status, history and alerts on the owner's phone |
| Product updates | No path to improve units after they shipped | Firmware releases managed from the console |
| Customer support | No view of a unit once it left the warehouse | Device registry showing owner, status and version |
How we took it from idea to launch
Good software follows a process. Here are the six stages, and what happens in each one.
Discovery & Requirements
Goal: Define the product vision, target audience and core business requirements.
Key activities- Stakeholder interviews
- Market and competitor research
- Defining user personas
- Drafting technical specifications or a Product Requirements Document (PRD)
Design (UX / UI)
Goal: Create an intuitive user experience and visual interface.
Key activities- UX design: information architecture, user flows and wireframes
- UI design: high-fidelity mockups and interactive prototypes in Figma or similar tools
- Design system: colors, typography and component libraries
Development: Frontend & Backend
Goal: Build the functional application using agile sprints.
Key activities- Backend: set up databases, design APIs (REST, GraphQL), implement server logic, and configure authentication and authorization (OAuth, RBAC)
- Frontend: build responsive interfaces and connect components to backend APIs
- Version control: manage code through Git and GitHub
Security & Optimization
Goal: Harden the application against vulnerabilities and boost performance.
Key activities- Security: address the OWASP Top 10, including injection, XSS and CSRF, enforce encryption in transit and at rest, and implement rate limiting
- Optimization: code splitting and lazy loading, database indexing, API caching and load testing
- QA and testing: unit, integration and end-to-end tests
Beta Release
Goal: Deploy to a controlled group of real users to catch edge-case bugs and gather feedback.
Key activities- Set up staging and production CI/CD pipelines
- Launch a closed or open beta with real users
- Monitor errors through observability tools
Public Release (Launch)
Goal: Roll the software out to the general public.
Key activities- Final production deployment
- DNS configuration
- Marketing and onboarding rollout
- Post-launch performance and security monitoring
Business benefits
The app gives owners a reason to keep using the device after the first week.
Guided setup and in-app help deal with common questions early.
Firmware updates let the product improve after purchase.
Usage data shows the team how devices behave in real homes.
Conclusion
Connected hardware fails in places a demo never shows: a weak signal, a confusing setup screen, a firmware bug on units already sold. Hexagon built the client's software with those situations in mind, covering the device connection, the apps, the cloud and the tools its team uses. Hardware companies rarely want to manage separate vendors for each of those pieces. If you have a device that needs software, or software that isn't keeping up with your device, we'd welcome a conversation.
Talk to us about your projectRelated services: IoT development · custom software development
Related projects
FAQs
BUSINESS SYSTEMS
SOFTWARE
AI
INTEGRATIONS
Build, Improve, or Connect the Systems Your Business Depends On.
Whether you need custom software, CRM, ERP, AI, automation, integrations, or modernization, tell us what you’re trying to improve. We’ll review your requirements and recommend the most practical next step.
300+
Software projects delivered
37+
Enterprise apps built
150+
delivery team members
10+
countries served
Tell Us About Your Project
No sales pressure. Tell us what you’re trying to build, improve, integrate, automate, or replace. We’ll review your answers and come back with a clear recommendation within 1 business day.
Prefer to talk now? Call +1 (801) 259-4800 or book a free 30-minute consultation.
Custom software, CRM, ERP, AI, integrations, and business systems built to improve how growing organizations operate.
© 2026 Hexagon IT Solutions. All rights reserved.