What are you building?
What are you building?
Built for traffic and time
Members & CommunitySocial EntertainmentDigital EducationMember App DevelopmentMember cards, points and coupons, synced with POSBooking & Registration SystemsOnline booking, scheduling, check-in and eventsBluetooth or Wi-Fi pairing, device control and status, a cloud back end and OTA firmware updates. We align the communication protocol with your firmware team and test together on real devices. After launch, iOS and Android change every year, and the same team keeps the app working.
Free requirements review · Reply within 1 business day · NDA available
JoinX experience
IoT app development covers more than app screens: it also includes the communication protocol with the device, a cloud back end and APIs, OTA firmware updates, store publishing and long-term OS update maintenance. The app pairs with the device over Bluetooth or Wi-Fi, sends commands and reads status, so command formats and error handling must be defined together with the firmware team. Controlling the device away from home, linking it to an account or managing several units requires a cloud back end. Firmware fixes and new features reach devices through OTA updates pushed by the app or the cloud. After launch, iOS and Android change every year, along with Bluetooth permissions, background execution and push rules, so the app needs ongoing adjustment. An IoT app is a system in which the app, the device and the cloud work together, not a single app.
Real projects Device apps and IoT projects
Below are apps we built for equipment makers and hardware brands. Some started as a single device app and later added a back office, brand versions or new features.
Since 2025HVAC and ventilation equipment maker
An app for a clean-air ventilation system, later extended with an admin back office and APIs, plus a separate app version for a partner brand and yearly maintenance.
2026Delta Electronics
An IoT app system for power and electronics products.
Since 2026Coffee machine company
A mobile app for operating coffee machines, with features added after launch.
Since 2024Electronic instrument company
An Android app for a measuring instrument, later extended with web version features and UI/UX improvements.
2025Medical technology company
Apple Watch health data integration and TrueDepth depth image data collection.
2020Electric vehicle company
An electric vehicle app for an EV company.
* Projects without a client name are described by industry under confidentiality agreements.
Scope What IoT app development covers
Each part of a device app affects the others: the pairing method decides whether you need a cloud, and the cloud decides whether OTA and multi-brand versions are possible.
Bluetooth scanning and pairing, Wi-Fi provisioning, reconnection and permission prompts, with stable connections across different phones.
Power, modes, schedules and other commands, with live device status and alerts; when a command fails, users know what happened.
Account and device binding, multi-device management, remote control and push notifications, plus an admin back office for support and sales.
Firmware pushed through the app or the cloud in batches, with retries on failure and each device's version visible in the back office.
One codebase with brand-specific look, name and feature set, published separately and managed per brand, without rewriting for each brand.
App Store and Google Play review and publishing; after each iOS and Android release, Bluetooth, background and push behavior are checked and adjusted.
Compare Bluetooth direct vs Wi-Fi / cloud vs gateway
The connection method depends on the device hardware and how it is used, and it shapes how much the app and back end must do. Many products combine them, for example provisioning over Bluetooth and then connecting to the cloud over Wi-Fi.
| Aspect | Bluetooth direct | Wi-Fi / cloud | Gateway |
|---|---|---|---|
| Suitable devices | Bluetooth direct: Wearables, measuring instruments, portable or close-range devices | Wi-Fi / cloud: Home appliances, ventilation and HVAC equipment, plugged-in fixed devices | Gateway: Many sensors, low-power nodes, multiple units on one site |
| Control away from home | Bluetooth direct: No, the phone must be near the device | Wi-Fi / cloud: Yes, remote control through the cloud | Gateway: Yes, the gateway connects to the cloud |
| Power use | Bluetooth direct: Low, suits battery power | Wi-Fi / cloud: Higher, usually needs mains power | Gateway: Nodes are low-power; the gateway needs mains power |
| Cloud required | Bluetooth direct: Not always; data can stay on the phone first | Wi-Fi / cloud: Yes | Gateway: Yes |
| Development focus | Bluetooth direct: Pairing flow, reconnection, compatibility across phone brands | Wi-Fi / cloud: Provisioning flow, account and device binding, remote control and push | Gateway: Gateway-to-node protocol, data handling for many devices |
| Common issues | Bluetooth direct: Unstable connections on some phones, OS permission changes | Wi-Fi / cloud: Provisioning fails because of home network settings | Gateway: When the gateway goes offline, the whole site goes offline |
Process How we build it
The hard part of an IoT app is not the screens. The app, firmware and cloud must understand every command the same way. Every phase ends with something you can accept.
2–4 weeks
Confirm the communication protocol, command formats and error codes with the firmware team, and decide the connection method, whether a cloud is needed and which features come first.
Depends on scope
Design the pairing, control and alert flows. A clickable prototype is tried by product and support staff before sign-off.
6 weeks–6 months
The app, cloud back end and APIs are built together. Pairing, control and OTA are tested on real devices and verified on phones of different brands and OS versions.
Ongoing
Submit to App Store and Google Play review and publish; monitor connection and OTA errors, and adjust for iOS and Android releases. The same team stays responsible.
Pricing Price ranges
Estimates based on custom app projects in Taiwan in 2026. The final figure depends on the number and types of devices, whether a cloud back end is needed and whether multi-brand versions are required.
| Scope | Price range | Typical content | Timeline |
|---|---|---|---|
| Requirements and protocol review | NT$100k–300k | Review of devices, protocols and data flows, producing a comparable spec | 2–4 weeks |
| Single device control app | NT$500k–1.2M | Pairing, control and status display, with a simple back office | 6–12 weeks |
| Full-featured | NT$1.2M–3M | Accounts and multiple devices, cloud back end, push notifications, OTA | 3–6 months |
| Platform | NT$3M and up | Multi-brand versions, large device fleets, data analytics or AI | 6 months or more |
Device firmware is handled by your hardware team or quoted separately. Cloud hosting, push notifications and store account fees are billed by usage. Post-launch maintenance is a separate agreement.
FAQ Common questions
Based on custom projects in Taiwan in 2026: pairing, control and status display for a single device with a simple back office is about NT$500k–1.2M; accounts and multiple devices, a cloud back end, push notifications and OTA are about NT$1.2M–3M; multi-brand versions, large device fleets or data analytics start at about NT$3M. Device firmware, cloud hosting and store account fees are extra.
A single device control app takes about 6–12 weeks; a full-featured app with a cloud back end, push notifications and OTA takes about 3–6 months; a multi-brand or large-fleet platform takes 6 months or more. A 2–4 week requirements and protocol review comes first, and time for App Store and Google Play review is planned in.
We handle the app and cloud back end; firmware stays with your hardware team or existing firmware vendor. Early in the project we confirm the communication protocol, command formats and error codes with the firmware team, and we test together on real devices during development. If you need help assessing firmware, we can quote it separately.
It depends on whether the device runs on batteries and whether users need to control it away from home. Battery-powered, close-range devices suit Bluetooth; plugged-in devices that need remote control or push notifications suit Wi-Fi with a cloud; sites with many sensors usually use a gateway. Many products combine them, for example provisioning over Bluetooth and then connecting to the cloud over Wi-Fi.
It can, which is why post-launch maintenance matters. iOS and Android change every year, and Bluetooth permissions, background execution and push rules may change with them. We check pairing and control on real devices when new OS betas come out and make adjustments before the official release where needed; maintenance scope is a separate agreement.
One codebase switches look, name and feature set per brand, each version is published under that brand's store account, and the back office can be managed per brand. A fix made once applies to every version, so there is no need for a separate app per brand. We have built a partner-brand app version with yearly maintenance for a ventilation equipment maker.
Related Related services
Get started Start with one device
No full spec needed. Tell us whether the device uses Bluetooth or Wi-Fi, who handles the firmware, what users need to control, and whether you need a cloud back end or multi-brand versions.