Summary

I maintain expo-mqtt, an Expo Modules (Swift/Kotlin) library that provides MQTT client support for Expo apps. Since it includes native code, it requires an Expo Development Build (Dev Client) and does not work in Expo Go.

Problem / Motivation

Expo developers often need MQTT for realtime/IoT use cases (device control, telemetry, health monitoring, bidirectional messaging). Today there isn't an official Expo SDK module for MQTT, so developers end up using incompatible RN libraries or ad-hoc solutions.

Proposed change

Add a short mention in the docs recommending expo-mqtt as a third-party option for MQTT when using Development Builds, with a clear note that it requires native code (Dev Client).

Library

npm: expo-mqtt https://www.npmjs.com/package/expo-mqtt

GitHub: https://github.com/rtsouza26/expo-mqtt

Platforms: iOS (Swift) / Android (Kotlin)

Requires: Expo Development Build (Dev Client). Not supported in Expo Go.

Config plugin: yes/no (link to docs section)

Example app: (link)

Suggested doc location

I believe this fits well in one of these pages:

“Using Libraries” (as an example of a native module requiring Dev Builds)

“Adding custom native code / Customizing” (third-party native modules)

If you prefer, I can open a PR adding a small “MQTT” note with links + constraints.