6 ms·

Very nice. I am running a similar site, and I wonder whether it isn't a bit overwhelming to have all the bells and whistles on the one page, upfront. In my exp

Very nice. I am running a similar site, and I wonder whether it isn't a bit overwhelming to have all the bells and whistles on the one page, upfront. In my experience, you get tons of bounces because people don't know (yet) what your site is for (but as someone who does know what options are, it does look useful). I don't think there is any single "answer" though. My "solution" in the past has been either to break up all the options into a sequence of choices (so the user only has to make one choice at a time, rather than worry about all the other knobs and dials/what they do/what they have missed), or (where possible) divide the choices between pages in some way that makes sense (this wouldn't make sense in this case but you would do puts and calls on separate pages). Would be interested to hear any other solutions though. I do these kind of sites (tables, lots of things to select, lots of data) almost exclusively and so I am always looking for more solutions. Some other thoughts: maybe make the top bar smaller to give yourself more room. I am not a big fan of centred data in tables because the spacing can feel irregular. And I would try to standardize column title length (for example, using abbreviations/tooltips) so your spacing is even too. My eye is drawn immediately to the underlying price column because of the gap created by centring/title length, which isn't good because this isn't really an important column. I would also consider working out which column is most important and making that more prominent (if possible) so the table is scannable (another option is hiding some columns, again I am not sure how this fits with your vision for users but is the user scanning rows and only needs to look at the delta later? Some of your columns are clearly duplicated in the description too, do you need separate columns for bid/ask...lots of options I think to cut the table down a bit...I have a 15" laptop and 10 columns feels like a lot). Finally, very minor point, but I wonder whether the font on the unselected multi-select buttons is too light...it is very, very slight but just blends a bit too much with the background, imo (generally, the colour scheme/contrasts for your selections are excellent, I feel my eye is drawn to the right places and nothing is distracting). Well done though. I think there is a huge niche for these kind of financial information products. EDIT: Open Interest is spelt wrong in the table's column headers.

mrhichem 5y ago
Thank you for your feedback. What made me make this screener is what you called "sequence of choices" I found on most other screeners. What I wanted as a user was to have full control on screening criteria. Maybe it is overwhelming for some. But from my point of view the more I had criteria the better
mrhichem 5y ago
Totally agree with your remarks regarding the interface.
duckmysick 5y ago
> I do these kind of sites (tables, lots of things to select, lots of data) almost exclusively and so I am always looking for more solutions. How do you deal with displaying a table with 10-20 columns on small screens? It compares similar objects across different metrics and a single column is either a grade (A-F) or a number. The best I came up with so far is collapsing rows into cards, but it sucks when you want to compare them with each other. For example finding objects with grade A or B in a certain column.
- hogFeast 5y ago
  Ah yes, that is quite a problem. I would consider carefully if it is really worth it for you. Making tables responsive is utterly hellish. But what you can do is make the table horizontally scrollable. This isn't too complex but, of course, it creates a new problem which is: what do you do if the user needs to look at one col at the start of the table and one col at the end? In the cases where I have added scrolling, I froze the first col (which gets a little involved when you have to freeze the first col and then scroll all the others). It is tricky, afaik there are no library impls of this, but there are no other options if you have a really data-heavy website and mobile users. A strong implementation of horizontal scrolling with first col freezing is the NBA's stats website - https://www.nba.com/stats/player/201566/ https://www.nba.com/stats/player/201566/ Doing cards is a definitely an option in some circumstances but if you are building an application where the user needs to scroll through rows then it becomes problematic. For example, if you have a website like the NBA...it makes sense (I think) to do cards for a team's upcoming matches...you don't need to display a whole lot of information (the opponent, the date, the venue), users aren't going to scroll through 20 rows. But if you are doing a player's stats with lots of columns and users might want to go back 10 years and compare AST today with AST 10 years ago...then cards aren't a good solution.
  - duckmysick 5y ago
    > Making tables responsive is utterly hellish. It really is. I briefly considered sticky/frozen columns, but I wanted sticky headers too - which I think are important too. In your NBA example it's difficult to tell what the numbers exactly mean without scrolling back to the top. I researched a few options some time ago, but all of them were complicated or flat out not working. Datatables.js had a crazy workaround: the fixed columns were separate tables styled to look like they are part of the main table. I ended up with a summary view that had just 3 columns, so no side scrolling was necessary. There was a filter option, where users could select other columns that interested them. Not perfect, but it turned out ok. The hunt continues.

mrhichem 5y ago

Thank you for your feedback. What made me make this screener is what you called "sequence of choices" I found on most other screeners. What I wanted as a user was to have full control on screening criteria. Maybe it is overwhelming for some. But from my point of view the more I had criteria the better

mrhichem 5y ago

Totally agree with your remarks regarding the interface.

duckmysick 5y ago

> I do these kind of sites (tables, lots of things to select, lots of data) almost exclusively and so I am always looking for more solutions. How do you deal with displaying a table with 10-20 columns on small screens? It compares similar objects across different metrics and a single column is either a grade (A-F) or a number. The best I came up with so far is collapsing rows into cards, but it sucks when you want to compare them with each other. For example finding objects with grade A or B in a certain column.

hogFeast 5y ago
Ah yes, that is quite a problem. I would consider carefully if it is really worth it for you. Making tables responsive is utterly hellish. But what you can do is make the table horizontally scrollable. This isn't too complex but, of course, it creates a new problem which is: what do you do if the user needs to look at one col at the start of the table and one col at the end? In the cases where I have added scrolling, I froze the first col (which gets a little involved when you have to freeze the first col and then scroll all the others). It is tricky, afaik there are no library impls of this, but there are no other options if you have a really data-heavy website and mobile users. A strong implementation of horizontal scrolling with first col freezing is the NBA's stats website - https://www.nba.com/stats/player/201566/ https://www.nba.com/stats/player/201566/ Doing cards is a definitely an option in some circumstances but if you are building an application where the user needs to scroll through rows then it becomes problematic. For example, if you have a website like the NBA...it makes sense (I think) to do cards for a team's upcoming matches...you don't need to display a whole lot of information (the opponent, the date, the venue), users aren't going to scroll through 20 rows. But if you are doing a player's stats with lots of columns and users might want to go back 10 years and compare AST today with AST 10 years ago...then cards aren't a good solution.
- duckmysick 5y ago
  > Making tables responsive is utterly hellish. It really is. I briefly considered sticky/frozen columns, but I wanted sticky headers too - which I think are important too. In your NBA example it's difficult to tell what the numbers exactly mean without scrolling back to the top. I researched a few options some time ago, but all of them were complicated or flat out not working. Datatables.js had a crazy workaround: the fixed columns were separate tables styled to look like they are part of the main table. I ended up with a summary view that had just 3 columns, so no side scrolling was necessary. There was a filter option, where users could select other columns that interested them. Not perfect, but it turned out ok. The hunt continues.