Is Cards View (used in list view and grid view on the main pages) the right way to display contents?
From the official Material Design site (link below):
"Usage: Cards display content composed of different elements whose size or supported actions vary."
"Cards are a convenient means of displaying content composed of different elements. They’re also well-suited for showcasing elements whose size or supported actions vary, like photos with captions of variable length."
"Cards are unnecessary in a gallery of images (homogeneous content)."
"When to use: As a collection, comprises multiple data types"
IMHO, these and other statements seems to advise against the use of card view in this situation since it's displayed homogeneous content without any type of interaction.
Is Cards View (used in list view and grid view on the main pages) the right way to display contents?
From the official Material Design site (link below):
"Usage: Cards display content composed of different elements whose size or supported actions vary."
"Cards are a convenient means of displaying content composed of different elements. They’re also well-suited for showcasing elements whose size or supported actions vary, like photos with captions of variable length."
"Cards are unnecessary in a gallery of images (homogeneous content)."
"When to use: As a collection, comprises multiple data types"
IMHO, these and other statements seems to advise against the use of card view in this situation since it's displayed homogeneous content without any type of interaction.
Google guidelines: https://material.io/guidelines/components/cards.html#
Alright, I see what you mean. So if I am not mistaken, you're suggesting the use of grid tiles right? I'd have to look into the differences (in implementation) to really take a stance for or against changing it to grid tiles, but for now I can only say that it probably won't be implemented soon. Although I'd love to see the application being optimised, other issues (particularly bugs) have a higher priority at this moment.
I do, of course, appreciate that you've brought this to my attention! :)
Alright, I see what you mean. So if I am not mistaken, you're suggesting the use of grid tiles right? I'd have to look into the differences (in implementation) to really take a stance for or against changing it to grid tiles, but for now I can only say that it probably won't be implemented soon. Although I'd love to see the application being optimised, other issues (particularly bugs) have a higher priority at this moment.
I do, of course, appreciate that you've brought this to my attention! :)
for now I can only say that it probably won't be implemented soon
Yeah, I just wanted to make you notice it, but obviously this "issue" should have a very low priority.
>you're suggesting the use of grid tiles right?
Yes, I think it could be better in this case.
>for now I can only say that it probably won't be implemented soon
Yeah, I just wanted to make you notice it, but obviously this "issue" should have a very low priority.
Is Cards View (used in list view and grid view on the main pages) the right way to display contents?
From the official Material Design site (link below):
"Usage: Cards display content composed of different elements whose size or supported actions vary."
"Cards are a convenient means of displaying content composed of different elements. They’re also well-suited for showcasing elements whose size or supported actions vary, like photos with captions of variable length."
"Cards are unnecessary in a gallery of images (homogeneous content)."
"When to use: As a collection, comprises multiple data types"
IMHO, these and other statements seems to advise against the use of card view in this situation since it's displayed homogeneous content without any type of interaction.
Google guidelines: https://material.io/guidelines/components/cards.html#
Alright, I see what you mean. So if I am not mistaken, you're suggesting the use of grid tiles right? I'd have to look into the differences (in implementation) to really take a stance for or against changing it to grid tiles, but for now I can only say that it probably won't be implemented soon. Although I'd love to see the application being optimised, other issues (particularly bugs) have a higher priority at this moment.
I do, of course, appreciate that you've brought this to my attention! :)
Yes, I think it could be better in this case.
Yeah, I just wanted to make you notice it, but obviously this "issue" should have a very low priority.