Skip to main content

 

I’m not sure if this is a recent change and it seems that it is, but even if not what possible reason is there to clip the rule names and then have all this blank space next to it?

 

I use a wide monitor, but this is a window taking up only half my screen. It looks the same on my smaller laptop. This is not a screen resolution problem, this is a design problem.

This kind of design does not seem to indicate the users experience is considered at any point, but instead some arbitrary aesthetic.

 

@ophirsw I know you’ve seen my various posts on whitespace and I’m sure are thrilled to see another :) I don’t search these things out and I’m not particularly jazzed about writing these but it seems that this issue of gratuitous whitespace at the expense of product usability seems to keep happening. 

Is there a better way we can communicate how inconvenient these changes are? Is there some other method we can employ that will have a substantive impact on the way these changes are considered to better take the user into account before implementing? Not trying to be dramatic, but more and more screens we jump to are getting increasingly irritating to use. 

Thanks :)

I reported an issue related to whitespace in November 2024 concerning Calculated Fields in Dynamic JO, where it was impossible to update the value in one of my calculated fields after setting it the first time.

 

 

  

A fix was released last week, which solves my problem with evolving my configuration as I clone this template month after month to address the lunch and learn of the month. However, now I can't see the input type or operator at a zoom level of 100% on a 27” viewport.

   

 

We need to do away with these modals. We do not need to see the program layout in parallel to creating or updating calculated fields. Let's use the screen estate wisely so we can configure our programs, data designs, rules, etc., efficiently and comfortably.

Thanks. 


We do not need to see the program layout in parallel to creating or updating calculated fields. Let's use the screen estate wisely so we can configure our programs, data designs, rules, etc., efficiently and comfortably. 

👆💯

 

There’s soooo much unused space (see the blue lines on ​@alizee’s screenshot). This wasn’t an issue in advanced JO (see the second and third screenshots below). You can actually see the logic and operators. What was the reason for this design choice in Horizon?

 

Tons of unused screen real estate
Overview of calculated field setup in advanced JO
Deep dive showing operators logic within field editing for calculated fields in advanced JO

 


Or Cockpit views - not showing the full name of the view is unbelievable.

 

 

 


Another white space issue, that seems new.

My engagement models in the dropdown now show up with … because they’re too long. Meanwhile, there’s a ton of whitespace in the modal.

Please, let’s think responsive design. 

 


Here’s a new one for today (it seems fresh - probably an over the weekend happening):

There’s plenty of whitespace here to absorb those boxes scaling with the contents inside them. Let’s make sure they do.