Flic got back to me, indicated that I should just write all the code myself to interface with the buttons and not rely on the Flic app. Even if I do rely on the Flic app, I still have to write the code to list what actions are supported by the Flic button for single press, double press, etc. That code is not something that is part of the Flic app itself. The Flic app returns to your app in order for the user to choose an action (according to their documentation and the person that responded). So there is no easy implementation for this unfortunately.
The Flic support person did indicate that the Flic 2 firmware is being updated in the Spring to support MIDI messages. MobileSheetsPro supports triggering actions through MIDI messages, so that may be an option that doesn't require any additional changes. I imagine it will be MIDI over bluetooth though, so we will have to see how well it works on Android.
Mike
UPDATE:
One more piece of information - Flic partnered with forScore a long time ago and added native support for them in the Flic app. They aren't doing this anymore, so my only option is to use the SDK.
The Flic support person did indicate that the Flic 2 firmware is being updated in the Spring to support MIDI messages. MobileSheetsPro supports triggering actions through MIDI messages, so that may be an option that doesn't require any additional changes. I imagine it will be MIDI over bluetooth though, so we will have to see how well it works on Android.
Mike
UPDATE:
One more piece of information - Flic partnered with forScore a long time ago and added native support for them in the Flic app. They aren't doing this anymore, so my only option is to use the SDK.