Is there no support in the official Flic Mac app for the Twist? Why are you so bad at disclosing the limitations of your products? My initial experiences with the Flic Twist have been incredibly frustrating due to your poor communication about this very basic stuff. Did you really not learn anything from the rough early experiences of your other products? Communicate!
@Emil I am sympathetic to the difficulties of effectively communicating product complexities. These implementation details you provided are interesting to me personally, but they are not particularly helpful to an average customer. It really feels like y'all have not carefully considered the types of questions a customer new to any of your products might ask. e.g. "I have/am interested in this product; does it have this capability?" or "I already have a Flic Button, can I do the same things with a Flic Twist?" Customers expect a certain level of consistency between different products from the same company. When you fail to deliver that consistency—and you do not effectively document the differences—it leads to frustrated customers.
The product matrix on the Twist product page comparing the Flic Button and the Flic Twist seems like a good place for some of this information. You already have a "Compatibilty" row in that matrix where you could explicitly list "Flic For Mac app" in the Flic Button column, and omit it from the Flic Twist column.
In the Flic For Mac app itself, on the "Add Flic" page next to the Flic Button illustration you could show a picture of the Flic Twist encircled by the crossed out sign.
Meanwhile, the Flic For Mac app page does not explicitly mention that it cannot configure a Flic Hub. That seems like a good place to mention that, especially when it is perfectly reasonable for a customer to assume that it can. Maybe add a feature matrix somewhere comparing the respective capabilities of the Android, iOS, and Flic For Mac app?
So the Flic "action engine" or whatever it could be called, i.e. the piece of software that communicates with buttons (and twists if supported) and performs a configured set of actions when a button is pressed currently have four different implementations: Android app, iOS app, Flic Hub and Mac app.
However, the Android app and iOS app also contains a UI client for the Flic Hub so that it can be configured. Currently, the Mac app cannot be used to configure a Flic Hub.
Where/how do you suggest we can communicate this better to our users? Feel free to give links or something where the info needs to be better. We try to make it clear on our website and in other sales material but due to all the different combinations of setups that are now possible since the new Hub Mini and Twist, it is possible that we can have missed or been unclear at some places.
@Emil I have a Flic Hub. It is not clear that having a hub is a necessary but not sufficient condition to use the Twist with the Mac app, which is why it is important that this is unambiguously spelled out in the documentation.
@seth_flic Our Flic Twist page https://flic.io/twist says "A Flic Hub is necessary to use Flic Twist".
I will take your feedback and tell our marketing team to update the website also for the mac app https://flic.io/applications/mac-app to make it more clear that it currently only supports the buttons.
@seth_flic Our Flic Twist page https://flic.io/twist says "A Flic Hub is necessary to use Flic Twist".
I will take your feedback and tell our marketing team to update the website also for the mac app https://flic.io/applications/mac-app to make it more clear that it currently only supports the buttons.
