Re: Any plans to implement iOS geofences?
jay (support) wrote:
Benjamin, we understand very well what the API provides, what we'd like it to provide, and the gap between.
If I create a plugin, the user needs someway to get that information....
The bottom line is this: state information can be accessed. Perhaps not as conveniently as some might wish but it's there and accessible. Holding back useful functionality (like enabling the built-in controls of subclassed devices) because it may hide informational state information, which is already fundamentally hidden in Indigo Touch/IWS seems quite counterproductive to me.
And, just as a reminder - you can create clipping files with control pages in them to distribute to your users if you choose. Again, it's not the perfect, but it's available (no need to whine about the limitations/problems with it - I'm just pointing out something that might help).
I disagree. User's had enough problem with the Applescript Security Script, and while there have been huge steps forward with the v5.x upgrades that make Switchboard significantly easier...
I can't imagine the difficulties of supporting users trying to copy IWS control pages from a clipping file would entail.
I want to use more of these features.... For example, Inside of switchboard is a prototype Security Control panel.
But I am concerned about ease of use issues for the end-users. I can't see adopting a feature that will involve the user having to do complex setups, since I know from the Security Script that'll end up with me crying in my Coca-Cola.
Right now, I have several users complaining that Switchboard is too complex, and they can't understand it... I am tempted to ask them to install the Classic Security script as a comparison....
I am targeting my plugins to be accessible to the average user, and trying to keep the complexity of the install down.
If that means certain features have to wait to be introduced to the users, then that is what I will do...