01 // Client outcome
NORRIS // ENGINEERING SYSTEM
Apps for equipment and IoT
We design Web and native apps around real device commands, telemetry, roles and service workflows.
Engineering sprint
35,000 KGSArchitecture, roles, protocol, MVP scope and next-stage estimate.
Timeline: 5 business days02 // Who it is for
Manufacturers and integrators who need a maintainable product rather than a generic screen.
03 // Problems solved
We connect field wiring, power, network, controllers and software so responsibility does not disappear between contractors. A working user flow, API contract, diagnostics and publication plan.
04 // PRICE
Packages, price and boundaries
Prices pending approval before publication
Engineering sprint
35,000 KGS
Timeline: 5 business days
Architecture, roles, protocol, MVP scope and next-stage estimate.
Priced separately: Equipment, production batches, licences, publishing accounts, statutory approvals and third-party work.
Select packageBranded Web/PWA
from 250,000 KGS
Timeline: From 20 business days
Brand, domain, dashboard, roles, core devices and PWA delivery.
Priced separately: Equipment, production batches, licences, publishing accounts, statutory approvals and third-party work.
Select packageWeb + iOS + Android
from 650,000 KGS
Timeline: From 35 business days
Web dashboard and native apps published in the client’s accounts.
Priced separately: Equipment, production batches, licences, publishing accounts, statutory approvals and third-party work.
Select packageDevice + platform
from 900,000 KGS
Timeline: From 45 business days
Device, firmware, provisioning, dashboard and apps.
Priced separately: Equipment, production batches, licences, publishing accounts, statutory approvals and third-party work.
Select packageOEM product
from 1,500,000 KGS
Timeline: From 60 business days
Electronics and software development plus pilot-batch preparation.
Priced separately: Equipment, production batches, licences, publishing accounts, statutory approvals and third-party work.
Select packageWhat is included
Architecture, roles, protocol, MVP scope and next-stage estimate.
What changes the price
Price depends on integration boundaries, interface count, source documentation, resilience requirements, app publication and support. The estimate requires: Protocol, command and telemetry list, roles, target platforms, onboarding flow and store requirements.
05 // SYSTEM
How the system works
The app reads modeled device entities through an API, sends acknowledged commands and exposes role-based diagnostics.
SENSORCONTROLAPP
06 // STACK
Equipment and integrations
The app reads modeled device entities through an API, sends acknowledged commands and exposes role-based diagnostics. Components are selected by protocol, serviceability and documentation. Architecture, models, software versions and code ownership are fixed before implementation.
07 // FALLBACK
If internet or power fails
Critical local functions are designed not to depend on the cloud; remote access and alerts resume when connectivity returns. Backup power is sized separately.
08 // INPUT
What we need from the client
Protocol, command and telemetry list, roles, target platforms, onboarding flow and store requirements.
09 // LAUNCH
Launch sequence
1. Collect inputs. 2. Run a paid engineering sprint. 3. Freeze architecture, interfaces and outcome. 4. Deliver in stages. 5. Run acceptance tests and hand over documentation. Inputs for this service: Protocol, command and telemetry list, roles, target platforms, onboarding flow and store requirements.
Diagnostics and design are separate paid deliverables. Materials are procured after scope approval and prepayment.
10 // SCENARIO
Engineering scenario
Solution diagram — not a published case study
The app reads modeled device entities through an API, sends acknowledged commands and exposes role-based diagnostics.
11 // LIMITS
Constraints and responsibility
Critical local functions are designed not to depend on the cloud; remote access and alerts resume when connectivity returns. Backup power is sized separately. We do not design technical solutions for free in chat. Third-party licences, publishing accounts, approvals and work outside the frozen interface are listed separately.
12 // FAQ
Frequently asked questions
Will the final price match the package price?
Yes when the site fits the stated boundaries. Any change is agreed before procurement. The page states exclusions and price factors explicitly.
What is needed for an exact scope and estimate?
Protocol, command and telemetry list, roles, target platforms, onboarding flow and store requirements.
Who owns the code, data and accounts?
Rights, repositories, domains, app stores and access are documented in the contract and stage architecture before implementation.
How does work start?
With project inputs and paid diagnostics or an engineering sprint. You receive a defined deliverable, not free design work in chat.
13 // NEXT
Related solutions
14 // REQUEST
Request for the selected service
We design Web and native apps around real device commands, telemetry, roles and service workflows.