---
title: Apps, services and hardware
description: Use Impo on your devices, connect your services and give your agent a physical interface.
---

Impo connects your conversations, the services you use and the hardware around you. Talk to your agent in an app or through a device. It can use your connected services, work with photos and respond through a screen, a speaker or another hardware capability.

![Apps and connected services work with the agent on the Impo server. Hardware sends capabilities, instructions, voice, photos and events, and receives commands to speak, show or move.](/assets/framework-map.svg)

## What connects to Impo

| Part | What it gives you |
| --- | --- |
| **Apps** | iOS, Apple Watch, Android, Web and Mac interfaces for conversations, results and personal context. Native apps also expose the capabilities their platform permits. |
| **Agent** | The Impo server brings together conversations, memory and tools, and connects your requests to actions. |
| **Connected services** | The mail, calendars, files and other cloud apps you choose to connect. Hardware can use these through the agent. |
| **Hardware** | ESP32 and Linux devices connected with the Gadget SDK. Microphones, cameras, sensors, speakers, displays and motors are available according to what each device implements. |

A hardware device paired with Impo is called a **gadget**. It can provide a way to talk to your agent, report something that happened, or carry out an action.

## How hardware and the server interact

**The hardware describes itself.** It supplies its capabilities, callable commands, the events it can send and the maker's instructions. A maker can explain what a device is for and what an event means. The agent learns this from the device's registration.

**The hardware sends input.** Speech, text and events reach the Impo server. A camera can return a requested photo for the agent to inspect. Each gadget has its own continuing Conversation for the messages and events it starts. These stay separate from the person's Main Chat.

**The agent responds.** It can use the person's connected services and the device's registered commands, then send back speech, display content or another supported action. The hardware executes the command and reports its result. The server checks account access and allowed operations.

iOS and Android provide Bluetooth setup. iOS also has a dedicated Conversation page for each gadget. After setup, the hardware communicates with the server directly; the phone does not have to relay every interaction. Web and Mac do not provide Bluetooth gadget setup. Mac's computer-access tools use a separate native-device path; Mac does not yet register through the Gadget SDK.

## Two interactions

**“Take a photo with my robot.”** You ask in the app. The agent calls the robot's camera, reads the returned photo and includes it in your conversation.

**You pick up a robot with a motion sensor and speaker.** The device reports a `picked_up` event and what it means. Its Conversation gives the agent the maker's instructions and prior context. The gateway sends the response to the robot's registered `speaker.say` command. Instructions can request a lookup in a connected calendar when that connection is available.

An offline gadget cannot execute a command. Impo reports the failure and does not queue the physical action for reconnection. A successful command result means what that command's contract says: accepted audio playback, for example, is not proof that playback finished.

## Where to extend it

| You want to… | Start here |
| --- | --- |
| Connect your own hardware | Implement an [ESP32 board adapter or Linux device](/docs/gadgets/add-a-board/) with the Gadget SDK. |
| Give hardware a new ability or behavior | Add [commands, events and maker instructions](/docs/gadgets/commands-and-events/). Existing registration carries them to Impo without a separate server definition for each device. |
| Connect another service or teach a new operation | Add a [tool and its instructions](/docs/extend/tools/). |
| Build a new interface | Use the [client API and shared capabilities](/docs/extend/clients-and-ui/). |

The [hardware design](/docs/gadgets/overview/) explains these extension boundaries. Saved, user-created gadget automations are a [separate proposal](/docs/gadgets/gadget-agents/); maker instructions and a continuing Conversation do not imply that automation system is available.

For the code behind these interactions, see [execution and recovery](/docs/architecture/execution/), [personal context](/docs/architecture/context/) and the [implementation reference](https://github.com/impoai/impo/blob/main/docs/architecture.md).
