Physical device
The panel, machine or product that senses something, receives a command or reports its condition.
IoT app developmentFrom device to daily operations
Build an IoT app that keeps devices, customers and your team connected.
Bring device setup, customer control, support and business operations into one clear product experience.
Tell us what the physical product does and who needs to use it. We help plan the app, device connection, operating tools and customer journey around the real work.
Device onboardingMobile appOperations dashboardEcommerce
Connected panel
1Light2Switch3Socket4Light5Switch6SocketFanSpeed · state
APPCustomer experienceSetup, status, control and help
SETNearby setupBluetooth and Wi-Fi guidance
OPSOperationsDevices, alerts and service work
APIConnected servicesRequests, state and business records
What has to work together
A useful IoT product is more than a screen with an on button.
The physical device, setup journey, customer app, connection and operating team all need clear responsibilities.
Guided setup
Help the customer prepare their phone, find the device, connect it and recover from a failed step.
Customer app
Show the customer what the device can do, its current state and what needs attention.
Service connection
Move requests and device reports between the app, the physical product and business records.
Operations
Give the team a place to find devices, investigate errors, provide service and keep history.
Waiting
Illustrative request state
The app should show what it knows.
A customer request can be waiting, confirmed by the device or blocked because the device is unavailable.
The app sent the request and is waiting for the device to report what happened.
Device onboarding
Make setup understandable before asking the customer to try again.
A nearby setup journey can check the phone, find the device, share the network, confirm readiness and explain a failure.
Bluetooth, Wi-Fi and permissions.
Discover the nearby device.
Share the selected network.
Check device-service readiness.
Place it in the account or location.
Show the failed step and next action.
Useful failure states
When something goes wrong, show the customer and the team what to do next.
Select a common problem to see how the product can explain it and guide the next step.
WHAT THE APP SHOWS
Permission needed
Bluetooth permission is off. Explain why it is needed before asking the customer to change it.
Next actionOpen the right phone setting
1Detect2Explain3Guide4Confirm
What Sagiam can build
Customer experience and operating tools around your physical product.
Each layer has a clear job. Together they form one connected product experience.
01 · CUSTOMER
Mobile apps
Accounts, setup, control, updates and help.
02 · ONBOARD
Device setup
Nearby discovery, linking and recovery.
03 · CONTROL
Status and control
Commands, confirmation, history and offline states.
04 · SERVICE
Alerts and support
Notifications, repair, warranty and help routes.
Your connected productDEVICE · APP · TEAM
05 · OPERATE
Operations dashboard
Fleet, errors, onboarding and connection health.
06 · MANAGE
Device lifecycle
Models, reassignment, firmware and retirement.
07 · LEARN
Reporting
Setup, usage, service and customer activity.
08 · SELL
Connected commerce
Products, accessories, installation and service.
Products that benefit from a connected journey
Plan the experience around the device and the people using it.
The device behavior, field conditions, users and operating rules decide the final scope.
Connected journeyPRODUCT → APP → SERVICE → TEAM
Smart homes and buildings
Lighting, access, room control and monitoring.
Equipment and field service
Machine status, repair work and history.
Energy and utilities
Usage, availability and operator review.
Consumer connected products
Setup, remote control, updates and warranty.
Mobility and transport
Asset condition, alerts and maintenance.
Retail and connected service
Sales, installation and after-sales support.
Selected connected-product work · Local draft
MeiSpace brings IoT apps, commerce and operations into one product system.
Sagiam designed and developed the represented MeiSpace ecosystem across connected-device apps, commerce experiences, service logic and admin operations.
Evidence status: Built software; production status and measurable outcomes pending client confirmation.
How we plan the work
Start with the device and the people who need to use it.
Six practical stages keep the hardware, software and operating process aligned.
Understand the product
Review what the device does, how it communicates and who owns each part.
Define users and jobs
Map the customer, installer, support, operator and administrator roles.
Plan every state
Cover setup, normal use, waiting, offline, errors, retries and recovery.
Prototype the journey
Make difficult steps visible before the complete product is built.
Build and connect
Create the agreed apps, services, dashboards and business connections.
Test and hand over
Check devices, permissions, commands, reconnects and team workflows.
Questions before an IoT project
Make the device, app and business requirements clear.
Can you build an app for our existing hardware?
Yes. We first review the device communication, available APIs or firmware documents, supported models, user roles and failure states before defining the app and service work.
Can you connect Bluetooth and Wi-Fi devices?
Yes, when the hardware and firmware expose the required communication. Bluetooth can support nearby discovery or setup, while Wi-Fi can support the connected service after setup.
What happens when the device goes offline?
The app should show that the device is unavailable or that its state is last known. The exact retry and recovery process depends on the hardware and connection.
Can customers manage more than one device or location?
Yes. The product can be planned around homes, rooms, branches, sites or another structure that matches the customer and operations model.
Can you build an operations dashboard?
Yes. It can cover agreed device states, onboarding, support, firmware work, alerts, reports, roles and activity history.
Can the app also sell devices or services?
Yes. An agreed project can include product discovery, ordering, installation, warranty or service journeys alongside connected-device features.
What do you need before estimating the project?
Share the device model, communication method, available firmware or API documents, expected users, target platforms, operating process and required integrations.
How long does an IoT app take to build?
The timing depends on hardware readiness, firmware access, supported device models, user journeys, integrations and field testing. We estimate after reviewing these inputs.
Start with what you already have
Show us the device, the users and the job they need to complete.
Bring the device model, communication method, current firmware or API documents, user roles and required business connections. We will help turn them into a practical product plan.