Cell Appearance

Explore options for presenting data while taking advantage of the convenience of ListView.

PDF for offline use
Related Samples:

Let us know how you feel about this


last updated: 2016-12

ListView presents scrollable lists, which can be customized through the use of ViewCells. ViewCells can be used for displaying text and images, indicating a true/false state and receiving user input.

There are two approaches to getting the look you want from ListView cells:

  • Customizing built-in cells – easier implementation and better performance at the expense of customizability.
  • Creating custom cells – more control over the end result, but have the potential for performance issues if not implemented correctly.

Built in Cells

Xamarin.Forms comes with built-in cells that work for many simple applications:

  • TextCell – for displaying text
  • ImageCell – for displaying an image with text.

Two additional cells, SwitchCell and EntryCell are available, however they aren't commonly used with ListView. See TableView for more information about these cells.


TextCell is a cell for displaying text, optionally with a second line as detail text.

TextCells are rendered as native controls at runtime, so performance is very good compared to a custom ViewCell. TextCells are customizable, allowing you to set:

  • Text – the text that is shown on the first line, in large font.
  • Detail – the text that is shown underneath the first line, in a smaller font.
  • TextColor – the color of the text.
  • DetailColor – the color of the detail text


ImageCell, like TextCell, can be used for displaying text and secondary detail text, and it offers great performance by using each platform's native controls. ImageCell differs from TextCell in that it displays an image to the left of the text.

ImageCell is useful when you need to display a list of data with a visual aspect, such as a list of contacts or movies. ImageCells are customizable, allowing you to set:

  • Text – the text that is shown on the first line, in large font
  • Detail – the text that is shown underneath the first line, in a smaller font
  • TextColor – the color of the text
  • DetailColor – the color of the detail text
  • ImageSource – the image to display next to the text

Note that when targeting Windows Phone 8.1, ImageCell will not scale images by default. Also, note that Windows Phone 8.1 is the only platform on which detail text is presented in the same color and font as primary text by default. Windows Phone 8.0 renders ImageCell as seen below:

Custom Cells

When the built-in cells don't provide the required layout, custom cells implemented the required layout. For example, you may want to present a cell with two labels that have equal weight. A LabelCell would be insufficient because the LabelCell has one label that is smaller.

All custom cells must derive from ViewCell, the same base class that all of the built-in cell types use.

Most cell customizations add additional read-only data (such as additional labels, images or other display information). If buttons or other controls that can be focused are added, the cell itself may not be clickable on Android. See below for a way to overcome this limitation.

Xamarin.Forms 2 introduced a new caching behavior on the ListView control which can be set to improve scrolling performance for some types of custom cells.

This is an example of a custom cell:


The XAML to create the above layout is below:

<?xml version="1.0" encoding="UTF-8"?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
        <ListView  x:Name="listView">
                        <StackLayout BackgroundColor="#eee"
                            <StackLayout Orientation="Horizontal">
                                <Image Source="{Binding image}" />
                                <Label Text="{Binding title}"
                                TextColor="#f35e20" />
                                <Label Text="{Binding subtitle}"
                                TextColor="#503026" />

The XAML above is doing a lot. Let's break it down:

  • The custom cell is nested inside a DataTemplate, which is inside ListView.ItemTemplate. This is the same process as using any other cell.
  • ViewCell is the type of the custom cell. The child of the DataTemplate element must be of or derive from type ViewCell.
  • Notice that inside the ViewCell, layout is managed by a StackLayout. This layout allows us to customize the background color. Note that any property of StackLayout that is bindable can be bound inside a custom cell, although that is not shown here.


Specifying a custom cell in C# is a bit more verbose than the XAML equivalent. Let's take a look:

First, define a custom cell class, with ViewCell as the base class:

public class CustomCell : ViewCell
        public CustomCell()
            //instantiate each of our views
            var image = new Image ();
            StackLayout cellWrapper = new StackLayout ();
            StackLayout horizontalLayout = new StackLayout ();
            Label left = new Label ();
            Label right = new Label ();

            //set bindings
            left.SetBinding (Label.TextProperty, "title");
            right.SetBinding (Label.TextProperty, "subtitle");
            image.SetBinding (Image.SourceProperty, "image");

            //Set properties for desired design
            cellWrapper.BackgroundColor = Color.FromHex ("#eee");
            horizontalLayout.Orientation = StackOrientation.Horizontal;
            right.HorizontalOptions = LayoutOptions.EndAndExpand;
            left.TextColor = Color.FromHex ("#f35e20");
            right.TextColor = Color.FromHex ("503026");

            //add views to the view hierarchy
            horizontalLayout.Children.Add (image);
            horizontalLayout.Children.Add (left);
            horizontalLayout.Children.Add (right);
            cellWrapper.Children.Add (horizontalLayout);
            View = cellWrapper;

In your constructor for the page with the ListView, set the ListView's ItemTemplate property to a new DataTemplate:

public partial class ImageCellPage : ContentPage
        public ImageCellPage ()
            InitializeComponent ();
            listView.ItemTemplate = new DataTemplate (typeof(CustomCell));

Note that the constructor for DataTemplate takes a type. The typeof operator gets the CLR type for CustomCell.

Binding Context Changes

When binding to a custom cell type's BindableProperty instances, the UI controls displaying the BindableProperty values should use the OnBindingContextChanged override to set the data to be displayed in each cell, rather than the cell constructor, as demonstrated in the following code example:

public class CustomCell : ViewCell
    Label nameLabel, ageLabel, locationLabel;

    public static readonly BindableProperty NameProperty =
        BindableProperty.Create ("Name", typeof(string), typeof(CustomCell), "Name");
    public static readonly BindableProperty AgeProperty =
        BindableProperty.Create ("Age", typeof(int), typeof(CustomCell), 0);
    public static readonly BindableProperty LocationProperty =
        BindableProperty.Create ("Location", typeof(string), typeof(CustomCell), "Location");

    public string Name {
        get { return(string)GetValue (NameProperty); }
        set { SetValue (NameProperty, value); }

    public int Age {
        get { return(int)GetValue (AgeProperty); }
        set { SetValue (AgeProperty, value); }

    public string Location {
        get { return(string)GetValue (LocationProperty); }
        set { SetValue (LocationProperty, value); }

    protected override void OnBindingContextChanged ()
        base.OnBindingContextChanged ();

        if (BindingContext != null) {
            nameLabel.Text = Name;
            ageLabel.Text = Age.ToString ();
            locationLabel.Text = Location;

The OnBindingContextChanged override will be called when the BindingContextChanged event fires, in response to the value of the BindingContext property changing. Therefore, when the BindingContext changes, the UI controls displaying the BindableProperty values should set their data. Note that the BindingContext should be checked for a null value, as this can be set by Xamarin.Forms for garbage collection, which in turn will result in the OnBindingContextChanged override being called.

Alternatively, UI controls can bind to the BindableProperty instances to display their values, which removes the need to override the OnBindingContextChanged method.

When overriding OnBindingContextChanged, ensure that the base class's OnBindingContextChanged method is called so that registered delegates receive the BindingContextChanged event.

In XAML, binding the custom cell type to data can be achieved as shown in the following code example:

<ListView x:Name="listView">
            <local:CustomCell Name="{Binding Name}" Age="{Binding Age}" Location="{Binding Location}" />

This binds the Name, Age, and Location bindable properties in the CustomCell instance, to the Name, Age, and Location properties of each object in the underlying collection.

The equivalent binding in C# is shown in the following code example:

var customCell = new DataTemplate (typeof(CustomCell));
customCell.SetBinding (CustomCell.NameProperty, "Name");
customCell.SetBinding (CustomCell.AgeProperty, "Age");
customCell.SetBinding (CustomCell.LocationProperty, "Location");

var listView = new ListView {
    ItemsSource = people,
    ItemTemplate = customCell

On iOS and Android, if the ListView is recycling elements and the custom cell uses a custom renderer, the custom renderer must correctly implement property change notification. When cells are reused their property values will change when the binding context is updated to that of an available cell, with PropertyChanged events being raised. For more information, see Customizing a ViewCell. For more information about cell recycling, see Caching Strategy.

Enabling Row Selection on Android

To allow row selection for cells that also include input elements such as buttons, a simple custom renderer is required. In the common code, create a subclass of Button so that a custom renderer can be added in the platform projects:

public class ListButton : Button { }

The renderer implementation for Android simply sets the Focusable property which allows the row to be selectable as well as host-clickable buttons. This code is added to the Android application project:

[assembly: ExportRenderer (typeof (ListButton), typeof (ListButtonRenderer))]
// ...
public class ListButtonRenderer : ButtonRenderer {
    protected override void OnElementChanged (ElementChangedEventArgs<ListButton> e) {
        base.OnElementChanged (e);
        Control.Focusable = false;

As stated above, only Android requires the ButtonRenderer to be implemented. iOS and Windows Phone platforms both allow the button to be clicked without implementing a custom renderer.

Xamarin Workbook

If it's not already installed, install the Xamarin Workbooks app first. The workbook file should download automatically, but if it doesn't, just click to start the workbook download manually.