This website uses cookies to better the user experience of its visitors. Where applicable, this website uses a cookie control system, allowing users to allow or disallow the use of cookies on their computer/device on their first visit to the website. This complies with recent legislative requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user’s computer/device. To learn more click Cookie Policy.

Privacy preference center

Cookies are small files saved to a user’s computer/device hard drive that track, save, and store information about the user’s interactions and website use. They allow a website, through its server, to provide users with a tailored experience within the site. Users are advised to take necessary steps within their web browser security settings to block all cookies from this website and its external serving vendors if they wish to deny the use and saving of cookies from this website to their computer’s/device’s hard drive. To learn more click Cookie Policy.

Manage consent preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies list
Name _rg_session
Provider rubygarage.org
Retention period 2 days
Type First party
Category Necessary
Description The website session cookie is set by the server to maintain the user's session state across different pages of the website. This cookie is essential for functionalities such as login persistence, ensuring a seamless and consistent user experience. The session cookie does not store personal data and is typically deleted when the browser is closed, enhancing privacy and security.
Name m
Provider m.stripe.com
Retention period 1 year 1 month
Type Third party
Category Necessary
Description The m cookie is set by Stripe and is used to help assess the risk associated with attempted transactions on the website. This cookie plays a critical role in fraud detection by identifying and analyzing patterns of behavior to distinguish between legitimate users and potentially fraudulent activity. It enhances the security of online transactions, ensuring that only authorized payments are processed while minimizing the risk of fraud.
Name __cf_bm
Provider .pipedrive.com
Retention period 1 hour
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to support Cloudflare Bot Management. This cookie helps to identify and filter requests from bots, enhancing the security and performance of the website. By distinguishing between legitimate users and automated traffic, it ensures that the site remains protected from malicious bots and potential attacks. This functionality is crucial for maintaining the integrity and reliability of the site's operations.
Name _GRECAPTCHA
Provider .recaptcha.net
Retention period 6 months
Type Third party
Category Necessary
Description The _GRECAPTCHA cookie is set by Google reCAPTCHA to ensure that interactions with the website are from legitimate human users and not automated bots. This cookie helps protect forms, login pages, and other interactive elements from spam and abuse by analyzing user behavior. It is essential for the proper functioning of reCAPTCHA, providing a critical layer of security to maintain the integrity and reliability of the site's interactive features.
Name __cf_bm
Provider .calendly.com
Retention period 30 minutes
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to distinguish between humans and bots. This cookie is beneficial for the website as it helps in making valid reports on the use of the website. By identifying and managing automated traffic, it ensures that analytics and performance metrics accurately reflect human user interactions, thereby enhancing site security and performance.
Name __cfruid
Provider .calendly.com
Retention period During session
Type Third party
Category Necessary
Description The __cfruid cookie is associated with websites using Cloudflare services. This cookie is used to identify trusted web traffic and enhance security. It helps Cloudflare manage and filter legitimate traffic from potentially harmful requests, thereby protecting the website from malicious activities such as DDoS attacks and ensuring reliable performance for genuine users.
Name OptanonConsent
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonConsent cookie determines whether the visitor has accepted the cookie consent box, ensuring that the consent box will not be presented again upon re-entry to the site. This cookie helps maintain the user's consent preferences and compliance with privacy regulations by storing information about the categories of cookies the user has consented to and preventing unnecessary repetition of consent requests.
Name OptanonAlertBoxClosed
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonAlertBoxClosed cookie is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice. It ensures that the cookie consent message is not shown again to the user, enhancing the user experience by preventing repetitive notifications. This cookie helps manage user preferences and ensures compliance with privacy regulations by recording when the notice has been acknowledged.
Name referrer_user_id
Provider .calendly.com
Retention period 14 days
Type Third party
Category Necessary
Description The referrer_user_id cookie is set by Calendly to support the booking functionality on the website. This cookie helps track the source of referrals to the booking page, enabling Calendly to attribute bookings accurately and enhance the user experience by streamlining the scheduling process. It assists in managing user sessions and preferences during the booking workflow, ensuring efficient and reliable operation.
Name _calendly_session
Provider .calendly.com
Retention period 21 days
Type Third party
Category Necessary
Description The _calendly_session cookie is set by Calendly, a meeting scheduling tool, to enable the meeting scheduler to function within the website. This cookie facilitates the scheduling process by maintaining session information, allowing visitors to book meetings and add events to their calendars seamlessly. It ensures that the scheduling workflow operates smoothly, providing a consistent and reliable user experience.
Name _gat_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _gat_UA-* cookie is a pattern type cookie set by Google Analytics, where the pattern element in the name contains the unique identity number of the Google Analytics account or website it relates to. This cookie is a variation of the _gat cookie and is used to throttle the request rate, limiting the amount of data collected by Google Analytics on high traffic websites. It helps manage the volume of data recorded, ensuring efficient performance and accurate analytics reporting.
Name _ga
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga cookie is set by Google Analytics to calculate visitor, session, and campaign data for the site's analytics reports. It helps track how users interact with the website, providing insights into site usage and performance.
Name _ga_*
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga_* cookie is set by Google Analytics to store and count page views on the website. This cookie helps track the number of visits and interactions with the website, providing valuable data for performance and user behavior analysis. It belongs to the analytics category and plays a crucial role in generating detailed usage reports for site optimization.
Name _gid
Provider rubygarage.org
Retention period 1 day
Type First party
Category Analytics
Description The _gid cookie is set by Google Analytics to store information about how visitors use a website and to create an analytics report on the website's performance. This cookie collects data on visitor behavior, including pages visited, duration of the visit, and interactions with the website, helping site owners understand and improve user experience. It is part of the analytics category and typically expires after 24 hours.
Name _dc_gtm_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _dc_gtm_UA-* cookie is set by Google Analytics to help load the Google Analytics script tag via Google Tag Manager. This cookie facilitates the efficient loading of analytics tools, ensuring that data on user behavior and website performance is accurately collected and reported. It is categorized under analytics and assists in the seamless integration and functioning of Google Analytics on the website.

Applying a Card-Based Design to User Interfaces: Best Practices

  • 38349 views
  • 8 min
  • Mar 14, 2019
Anastasia D.

Anastasia D.

Copywriter

Alexander M.

Alexander M.

UI/UX Designer

Share

Today, people tend to switch between two or three devices throughout the day as they visit various websites. So it’s crucial for designers to create appealing interfaces and an enjoyable experience across all devices. In order to achieve interface consistency, web and mobile design trends are moving toward the card-based UI design approach. In this article, we’ve teamed up with Alexandr Martynenko, one of the leading UX designers at RubyGarage, to share best practices for applying the card design pattern in web and mobile projects.

What is card-based design?

Cards are little rectangles used in interface design to outline the main idea of a product, service, or piece of information. Each card usually consists of an image, a bit of text, graphics, and a link to a page with more detailed information on the topic. Cards seem pretty simple, so what makes them so popular in UI design? The answer is that they look like real tangible cards. Before digital cards, people were used to seeing business cards and sticky notes all around them. People intuitively perceive cards as pieces of content, so they make it easy to scan information.

Card-based patterns are now more popular than ever. They’re especially beneficial for ecommerce websites and social networking sites where users scan information quickly and usually via mobile devices. Cards are successfully used by the biggest companies, including Google, Instagram, Pinterest, and Facebook. Microsoft implemented a card-based design in their Windows operating system in 2006.

 Instagram cards
Instagram cards
Pinterest cards
Pinterest cards
Facebook cards
Facebook cards

As a rule, a card consists of an image, title, description, and action. Here’s how a card looks in a wireframe:

Сard in a wireframe

Now that you know what card-based design is about, we can talk about the main pros and cons of this design approach.

Advantages of a card-based design

Chunking content

Cards usually have a similar structure on the page, which helps to organize content into chunks. This enhances the scannability of content, helps to avoid long unreadable texts, and allows users to save time while getting the main information. Good scannability is essential for online shops and marketplaces, as they’re content-heavy websites. Card-based web design is also a good solution for a blog like ours.

RubyGarage cards
The RubyGarage blog employs a card-based design to use space efficiently. Each card highlights a header image, article title, category, number of views, and reading time.

Great mobile responsiveness

As people actively use multiple devices, from phones and tablets to laptops and desktop computers, it’s necessary to create a responsive design for all screens. Cards can easily be resized and rearranged according to different screen sizes. It’s important for mobile and web pages to have the same content, as Google has started to prioritize mobile sites for indexing. Cards allow designers to build a unified aesthetic across devices and thereby create a consistent user experience.

Enhanced user experience

Card-based UI design bridges the gap between usability and interaction due to its responsiveness and consistency. Cards create an enjoyable user experience by:

  • laying out information clearly
  • being interactive, thereby encouraging users to stay longer on a website
  • making browsing more pleasant
  • relaying content to a user within three seconds, increasing user engagement
  • being highly manipulable
  • simplifying sharing, helping content go viral

Efficient organization

Cards divide information into meaningful sections. These sections allow designers to prioritize content into comprehensive blocks of information. This is visually stimulating for both designers and users. The card structure saves a designer time on aligning elements within the card and makes content more readable and appealing for users.

Minimalism

Minimalist interface design is one of the latest trends. More and more websites and apps are making their screens tidy, without extraneous details. Cards can easily and harmoniously fit into any minimalist design. Moreover, cards can increase content readability and highlight the delicacy of minimalism.

Disadvantages of a card-based design

Hard to stand out

Since cards have become so popular in web and mobile design, it’s getting harder to make your website stand out. Most card-based interfaces look pretty similar, and designers find it difficult to invent something distinctive. So the only thing websites can do is use appealing colors, typography, graphics, and animations to set their interfaces apart.

Not for all websites

Cards are not perfectly suited for all types and sizes of projects. For instance, for a small website with little content, a card-based design may be the wrong decision since there’s no need to divide the site into sections. A card-based design should be implemented in the right context if you want it to work efficiently.

Card-based design best practices

Using cards in interfaces requires a perfect combination of visual design and usability. Cards aren’t only about appealing UI design but also about clear interactions and user experience. Although cards look pretty simple, there are some important rules to ensure a great result. Let’s consider the best practices of applying a card-based design in your projects.

Use one piece of information per card

Remember the rule: one card – one idea. Using different cards for visualizing different pieces of information allows users to distinguish the content and find information easily. Cards can contain various elements but should refer to only one piece of information.

Card-based web design

Avoid inline links

The card itself should be linked to more detailed information, so avoid using inline links in the text in order not to confuse users. When the whole card is clickable, this greatly increases the usability of the interface on both touchscreen devices and desktop computers where a mouse is used.

Card-based web design

Add shadows

By adding shadows, you can create an association with tangible cards and improve overall readability. But keep in mind that shadows should be light; otherwise, they’ll adversely affect how users perceive the interface. In addition, designers can round the card’s corners to make the interface even friendlier.

Card-based web design
A card with shadows and rounded corners

Use the right typefaces

All information a card contains should be easy to read. That’s where typography comes into play. Use simple fonts, limit color schemes, and choose the right font size.

Right typefaces for cards

In this example, you can see how font size affects how information is perceived. The first card has the same font size for the heading, sub-heading, and the text itself. So nothing catches the user’s attention while reading. But the second card perfectly separates the eye-catching headline from the description and makes it easy to get the main idea.

Make cards minimalist

Make your cards clean and minimalist. Try to avoid excessive borders between elements.

Minimalist cards
Compare the first card with excessive borders to the second one with the minimalist design

Limit information

Try to not overwhelm cards with information. They should contain the minimum possible information to outline the main idea, as a card is linked to a more detailed overview. When you add too much content to a card, it becomes too long vertically or too wide horizontally and loses readability.

Cards in the interface design
Less content makes cards more readable

Use attractive images

By using images in card-based design, you increase the overall appeal and user engagement. First of all, images catch the user’s attention, only after which they proceed to the text. So choose visual components carefully, as quality visual content increases the attractiveness of the design as a whole.

Cards in the interface design

Make cards active

Make cards active when you hover the cursor. You can achieve this by doing the following:

  • Framing cards when hovered over
  • Showing a shadow
  • Making an existing shadow bigger or darker
  • Enlarging an image
  • Revealing additional information
Active cards
Hover animations in card-based design add a bit of discoverability and at the same time provide a more interactive user experience

Create a standard grid

Create a standard grid with a constant interval between cards and work with different sizes and breakpoints.

Cards in the interface design

Wrapping up

A card-based design is a growing trend that won’t end anytime soon and will continue increasing in popularity. The best thing about cards is that there’s no strict set of rules to follow when designing them. The only thing designers should keep in mind is simplicity, some basic card design principles, and experience. Don’t hesitate to share your ideas on this topic in the comments below!

CONTENTS

Authors:

Anastasia D.

Anastasia D.

Copywriter

Alexander M.

Alexander M.

UI/UX Designer

Rate this article!

Nay
So-so
Not bad
Good
Wow
11 rating, average 4.64 out of 5

Share article with

Comments (1)
M/S Zinavo
M/S Zinavo over 2 years ago
Thanks for sharing information. Your web-site is very cool. I am impressed by the details that you have on this blog. It reveals how nicely you perceive this subject
Reply

Subscribe via email and know it all first!