Where to Find Flic Integration and SDK Resources for Developers

Updated

Flic's developer resources are spread across a few distinct areas of flic.io rather than a single page. The Mobile SDK, Developer Portal, Flic Hub Studio, and Flic MQTT are the core entry points for building integrations, while ready-made bridges like the MIDI Controller, Keyboard Emulator, Mouse Emulator, Flic for OSC, and Flic for Mac cover common no-code or low-code scenarios. Start with the All Integrations and Get started links if you want to see what already exists before writing code.

Core developer entry points

The site groups its developer-facing tools under a Developer Tools section. Based on the site's navigation, these are the main destinations:

Resource What it's for
Mobile SDK Building mobile apps that talk to Flic buttons
Developer Portal Central access point for developer documentation and tools
Flic Hub Studio Working with the Flic Hub programmatically
Flic MQTT Connecting Flic events to MQTT-based systems

The site also states that Flic Buttons integrate with existing solutions and can be deployed and managed "thanks to our free SDK's" — so the SDK is positioned as the foundation for custom deployments, not just hobby projects.

Ready-made integration tools

If you don't want to build from scratch, the Setup → All Integrations path lists prebuilt options. The developer-relevant ones named on the site are:

  • Flic MIDI Controller — use buttons as MIDI inputs
  • Flic Keyboard Emulator — map button presses to keyboard shortcuts
  • Flic Mouse Emulator — map button presses to mouse actions
  • Flic for OSC — send Open Sound Control messages
  • Flic for Mac — Mac-specific integration

These are worth checking first: if your target system already accepts keyboard, MIDI, OSC, or MQTT input, one of these may remove the need for custom code entirely.

Where to start, depending on your goal

  • Prototyping a custom app or service: go to the Mobile SDK and Developer Portal first. The SDK is the documented path for programmatic control.
  • Connecting to an existing automation or messaging system: check Flic MQTT and All Integrations before writing anything.
  • Controlling creative or audio software: the MIDI Controller and Flic for OSC pages describe the mapping approach.
  • Triggering desktop actions: the Keyboard Emulator and Mouse Emulator are the lightest-weight options.

For business and multi-device deployments

The site separates consumer tools from business tooling. Under Business Solutions, it lists Device Manager and Flic Cloud Buttons, alongside a Message Button and the IoT Gateway. If you're deploying many buttons across a site — the site names healthcare, hospitality, lone worker safety, retail, logistics, and schools as example industries — Device Manager is the relevant management layer rather than the individual SDKs.

One caveat: the site describes the SDKs as free, but it does not publish pricing or account requirements for the Developer Portal, Hub Studio, or Device Manager on the pages referenced here. Confirm access terms on those pages before planning a deployment around them.

Practical next step

Open All Integrations to see whether your target platform is already covered. If it isn't, move to the Developer Portal and Mobile SDK for the programmatic route, and use Flic Hub Studio or Flic MQTT if your integration runs through a hub or a message broker rather than a phone.