Here's our roundup of this month's developments within the Chirp ecosystem. Have you been working on anything you'd like us to include next month? Get in touch.

🛠 We are hiring

Chirp enthusiasts, we need you! We are looking to hire an iOS developer who is committed to growing our developer community and sharing knowledge of Chirp with the wider world. Applicants should be keen hackers who can attend hackathons and meetups, be fluent in Swift/Objective-C and able to create engaging content for the Chirp blog.

More details available here.
Interested? Drop us a line at

📺 Screensharing

Connecting to projectors or screens are a headache, whether it be proprietary hardware, obscure drivers, hidden cables or crappy UIs - it all around isn’t a pleasant experience.Considering every TV is capable of broadcasting a Chirp we figured there was some magic we could weave with Chirp SDKs  

Check out our guide on the blog

🦋 Flutter

Flutter is Google's new cross platform mobile framework, built to capture the native performance of both iOS and Android devices. Applications are compiled ahead-of-time into a native Arm library, so there is no JavaScript bridge in the middle (unlike React Native and other cross-platform frameworks). We now offer a Chirp plugin for the framework using our existing iOS/Android SDKs. You can use the plugin directly from Flutter's package manager: ChirpSDK.

Read the tutorial, or skip straight to the example code.

If you’re interested we’ve also done the same for Kotlin and React Native.

🌄 Sunsetting the v1 API

We will be sunsetting version 1 of the Chirp REST API as of April 2019. Legacy apps running the v1 SDKs (from 2015 and before) will no longer be able to access network services such as the obsolete "associated data" database.

We’d be more than happy to help you migrate your apps from v1 to v3, if that’s the case, please get in touch at Apps running the 3.x.x Chirp SDKs are unaffected by this change.

We can guarantee that v1 won't be making a Mufasa-esque appearance in the cloud later on.

Chirp SDKs takes any data and converts it into sound. Nearby devices then convert that sound back into the original data via their microphone - while being totally offline.

Get building, for free here at