What does the app and server include?

Device setup and activation, accounts, the data pipeline, remote control, firmware updates, an admin console, and the store listings for the phone app.

Should I build my own server or use an existing platform?

If you already have an app or cloud team, build to fit your stack. If not, start from a proven stack and keep the accounts and data in your own name.

Who should own the accounts?

You should. Open the developer, cloud and app-store accounts under your own company and give the partner access.

Why is it often underestimated?

Because it is scoped last, while it touches every user and every update, and it keeps costing money after launch.

Building the App and Server for a Connected Device: Who Owns Them and Why It Matters

When a device is connected, the product is the device plus an app plus a service. The last two are often scoped last, discovered to be the largest part, and treated as an afterthought in the contract.

What it includes

Device setup, pairing and activation.
User accounts and permissions.
The data pipeline between device, phone and cloud.
Remote control and notifications.
Firmware updates over the air, with rollback.
An admin console for support and monitoring.
Store listings and review requirements for the phone app.

Build your own or start from an existing stack

You already have an app or cloud team. Build to fit your stack. The hardware and firmware should adapt to your interfaces.
You do not. Start from a proven stack for device activation, updates and voice or model access, and customise the brand experience on top. Keep the accounts and data in your own name.

Ownership

The things that must belong to you: the source code you paid for, the cloud tenancy, the developer and app-store accounts and the user data. Settle this in writing at the start. See who owns the design files.

Running costs

A server keeps costing money after launch: hosting, model or speech services, messaging and support. Estimate the cost per active user before you set a price, since it decides whether the product can live without a subscription.

Privacy and data location

Devices with microphones or cameras raise data questions in every market. Decide what is processed on the device, where data is stored and how users delete it.

Keep it with the hardware

Firmware, app and server depend on each other. When one team owns all three, a pairing failure becomes a question of what to fix rather than whose part works.

3CBAY builds the app and the server with the hardware, or builds the hardware to fit a client app and server. Scope and ownership are agreed together at the start of the project, as described on the services page.

Planning a connected product? Tell us what you are building.