I saw the big improvements to the Basic Rules under Automations (Still don't really get the Apps vs. Automations difference is some cases). So I was just curious to see if the Button Controllers UI had been given a facelift too. While the current version is way better than it used to be, and this is just IMHO, I think it could fairly easily be made much better, especially when creating a new automation. BTW, some of the below is about being put into then next blank field, which I thought was being "fixed" per a 2.5.0.x note. If so, I'm not sure where to turn that on or off as it certainly is still happening with 2.5.0.143.
- The very first field should be to name the rule. This would avoid some issues later on with the placement of that filed.
- Under that should be the “Select Button Device”, which I’d suggest to change to “Select Button Device(s)”
- Instead of “Update” (which is a misnomer 1st time) I’d suggest it says “Save Choices”
- When you click Update it puts you into the Name This Button Controller, which skips over adding the button(s). So I’d suggest adding that as the 1st step before even selecting the device
- Once the device is selected then it should take you right to the Select button to define field. As is, you have to click the “+” and then it puts you into that field. So that is an unnecessary step. It should also be labeled “Select button(s) to define”. BTW the capitalization is inconsistent in that it has ”Name This Button Controller” and “Add Button Here” with each word capitalized, but “Select button to define” and “Click to set” with only the 1st letter capitalized
- More significantly, once you click one or more button there is no “Select All, Deselect All, Update” buttons like there was for the Select a device. In fact, there is nothing telling you what to do next. Since you have to click off it it anyways, it would be far better to have a definite button to click.
- The user is then put into the Notes field, skipping over the real action of defining what the button(s) do. There is also a Name This Button Controller field at the bottom of this screen which is a duplicate of the field from the previous screen.
- When I click to create an action (.e.g. 1 Pushed) I’m again put into a Notes filed. As is, I then have to click the “Select Actions to Run (and Create and Mange Conditions and local Variables)” button, then click the “+” by “<- Create New Action” then click the “Select Action Type to add” dropdown. That’s 4 button clicks for nothing when 1st creating a button rule. Instead, the Selection Action Type to add dropdown should appear already opened.
- Once one is clicked on it immediately changes. In a way that is good, saving a step, but bad if that was clicked on by mistake and inconsistent with all the other pages that require a button to click (or the field to be clicked off of). And as along as this step is being automated, then the Select Which Action (each word capitalized) should have the dropdown opened,
- Once that is selected we get other fields to appear automatically. In the case I chose Turn switches on/off (only “Turn” capitalized).
- Yes, the slider says Turn on or off and the bold changes as does the heading Switches to turn [on/off] but instead of the slider (which is really not clear as it defaults to being to the right and the order is first Turn on or off, so off is the right hand one, why not 2 radio buttons with one called “On” and the other “Off”. So much clearer.
- Which I do click Switched to turn on I get the same dropdown as I did to select devices at the start. Here to, I’d change “Update” to “Save Choices” for the same reason, especially the first time through as I’m not “updating” anything - I’m creating it.
- The device I picked is a dummy one I created as a place holder for when I needed to exclude and then re-include a device. As you’ll see in the screenshot the name overflows the button.
- Also, the slider by Track event switch is covering the “?”. This is on a desktop in Safari with the browser taking up about 1/2 the screen width. When I “inspected” the item it looked like it was in a flex box, so maybe it just needs some @media tweaking.
