Tithi MondalBlog

Article6 min readUpdated

Card UI Design: Lists, Grids and Cards in Mobile Apps

Card UI design and mobile list design explained: when to use a list, a grid or cards, how to handle swipe actions and how to keep long lists easy.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Card UI Design: Lists, Grids and Cards in Mobile Apps: cover illustration

A tiffin service in Durgapur has 40 dishes in its app. The first version shows them as big cards with large photos, one per screen. A customer who wants to compare prices must scroll for a long time. The second version uses a compact list with a small photo, the name, the price and an "Add" button. Customers find what they want in a fraction of the time.

The cards were not wrong. They were used for the wrong job. This article is about choosing between a list, a grid and card UI design, and about the details that make each one work. A card is a block that holds the information and actions for a single item.

Should I use a list, a grid or cards?

Choose by how people decide. If they compare text, use a list. If the picture decides, use a grid. If each item has several parts and actions, use cards. The best pattern is the one that helps the user decide faster.

PatternBest whenExample
ListItems are similar, text-led and comparedTransactions, chat threads, settings, loan offers
GridThe image is the main clueClothes, jewellery, courses with thumbnails
CardEach item has an image, text, a status and an actionBookings, orders, food items, job listings
TableMany columns need comparing, mostly on large screensAdmin data, reports

On a phone, a table rarely works. Turn each row into a list item or card. For large-screen data, see admin dashboard UI and UX design.

Mixed apps often use several: a home screen with cards, a search result as a list, and a catalogue as a grid. See app home screen design.

How do I design a good list on mobile?

A good mobile list gives each row one purpose, one tap area and a clear structure. Each row should let the user recognise the item in under a second.

Rules for list design on mobile:

  • One primary line. The name or title, in the strongest style.
  • One or two supporting lines. Price, date, status. Not more.
  • Consistent alignment. Put the same type of information in the same place on every row. Prices on the right, for example.
  • A tap area of the whole row. Not just the name.
  • Row height of at least 48 points where there is a tap action, which is a general comfortable size.
  • Dividers or space, not both. Thin lines or gaps between items, whichever is cleaner.

Do not cram five details into one row. If a loan app shows the amount, the interest rate, the tenure, the processing fee and the lender in one tiny line, users give up. Show the amount and rate in the row, and put the rest on the detail screen. For finance examples see fintech app UI and UX design in India.

When does a card work well?

A card works well when the item has distinct parts, such as an image, a title, a status and an action, and each card stands alone. Cards also work when the content varies in length.

Good card examples:

  • A restaurant card: photo, name, cuisine, rating, delivery time. See food delivery app UI and UX design.
  • A booking card: date, place, status, "View ticket" button.
  • A course card: thumbnail, title, progress bar, "Continue".

Principles for card layout:

  1. Pick one main action per card. The whole card should open the detail. A secondary button, like "Save", needs its own clear target.
  2. Limit the content. Image, title, two supporting facts, one status. If you need more, the card is too heavy.
  3. Keep the layout identical across cards. Same image ratio, same text position. Uneven cards look broken.
  4. Handle missing data. Decide what shows when there is no photo or no rating. A grey placeholder with a clear shape is better than a hole.
  5. Plan for long text. Allow two lines for a title and then cut with dots. Bengali and Hindi names can be longer and taller than English, so test with real text. See regional language app design in India and Bengali typography in UI.

Do not put a card inside a card inside a card. The nesting creates visual noise, and the tap area becomes unclear.

How do swipe actions work in a list?

A swipe action lets a user swipe a row sideways to reveal a quick action, such as delete, archive or mark done. It is a shortcut for people who know it, so it must never be the only way to do something.

Do:

  • Offer the same action in a menu or on the detail screen.
  • Show a hint the first time, or a small partial reveal, so people discover the swipe.
  • Use clear colours and labels, with text and an icon: a red "Delete" and a grey "Archive".
  • Provide "Undo" after a destructive swipe. See button states and feedback design.
  • Keep swipe actions to one or two per side.

Do not:

  • Hide an essential action only behind a swipe.
  • Use a swipe that conflicts with going back or with a horizontal carousel inside the row.
  • Make delete the easiest swipe without a safety net.

A chat or a task list is a natural home for swipe actions, since users handle many similar items. For chat screens see in-app chat and support screen design. Because swipes are invisible, users with motor limits may not use them. See accessibility in app and web design.

How do I handle long lists?

Long lists need structure, so users do not scroll forever. Break them with search, filters, sections and sorting, and load the content in parts.

Ways to tame a long list:

  1. Group with headers. A contact list with letters, or an order list with "This week" and "Earlier". Sticky headers help users keep their place.
  2. Add search and filters near the top. See search and filter UX design.
  3. Load in pages. Load 15 to 20 items first, then more when the user nears the end. Show a small loading row at the bottom.
  4. Use "Load more" for buying decisions. Infinite scroll makes it hard to reach the footer or return to a position. A visible "Show more" button gives users control.
  5. Remember scroll position. When the user opens an item and returns, the list must be where they left it. Losing the place is a common and annoying bug.
  6. Plan the end. Show a short message such as "You have seen all 42 items" so the user knows the list has finished.

On slow networks, load text first and the images after, and keep image sizes small. See designing for low-end phones and slow networks and empty states, loading and error screens.

What small details make lists and cards feel right?

Small details of spacing, state and consistency decide whether a list feels calm or messy. These are what I check last.

  • Spacing. Use the same gap between cards everywhere, such as 12 or 16 points. See white space and layout basics.
  • Pressed state. A row should change colour briefly when tapped.
  • Loading skeletons. Show grey shapes in the same layout as the real cards.
  • Status labels. Use words with colour: "Delivered", "Pending", "Cancelled". Colour alone is not enough.
  • Text size. Keep list text readable, not tiny to fit more in. See colour contrast in UI and typography basics for non-designers.
  • Marketplace listings. Seller and buyer lists have different needs. On a seller app I designed for a marketplace, the listing list had to show status and stock at a glance, because sellers checked it many times a day. See marketplace app UI and UX design.

If your app shows many items and you are not sure which pattern fits, I can help you test the options in mobile app design. You can also start a conversation here.

Frequently asked questions

When should I use a grid instead of a list?

+

Use a grid when the image is the main reason someone chooses, such as clothes or jewellery. Use a list when people compare text details like price, date or status.

How many details should a card show?

+

Usually one image, one title, two supporting facts and one status or action. Put everything else on the detail screen.

Should I use infinite scroll or a Load more button?

+

Infinite scroll suits feeds that people browse casually. A Load more button suits shopping and search, where users need control and a way to reach the footer.

Are swipe actions accessible?

+

Only if the same action is available another way. Always offer a menu or button alternative, because swipes are hidden and hard for some users.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.