52 Weeks of Xamarin: Week 13 – Writing It Thrice

In this and a number of following posts, I’ll build the same program three times: once in Xamarin.Forms, once in iOS and once in Android.  ToDoListForms

This is directly based on my Pluralsight course, Beginning Mobile Development with Xamarin

To get started, we’ll go through the Xamarin.Forms application fairly quickly as this series has already covered a lot of material on writing Xamarin.Forms applications.   Let’s begin by creating our model class: ToDoItem

We know we want to save the data to a SQLite database, so we’ll add an ID field and the necessary attributes:

 using System;
 using SQLite;
 namespace ToDo {
     public class ToDoItem {
         [PrimaryKeyAttribute, AutoIncrement]
         public int ID { get; set; }
         public string TaskName { get; set; }
         public string Priority { get; set; }
         public DateTime DueDate { get; set; }
         public bool IsDeleted { get; set; }

Create Page

We start by creating our first page, CreateToDo, and its associated file CreateToDoViewModel.  CreateToDo.xaml provides the UI, which includes the buttons Save, Cancel and Review.  Here is the complete XAML page,

 <?xml version="1.0" encoding="UTF-8"?>
         Text="New Task"
         FontSize="18" />
         Placeholder="New To Do Item"
         WidthRequest="150" />
         WidthRequest="150" />
           Text="Due Date"
           TextColor="Green" />
         <DatePicker x:Name="Date"/>
           Text="Due Time"
           TextColor="Green" />
         <TimePicker x:Name="Time" />
         Orientation="Horizontal" HorizontalOptions="Center">

In the code behind we set up the ViewModel.  The constructor is overloaded, either to initialize the vm and the components, or to also retrieve the designated record from the database.

         public CreateToDo(int id) {
             vm = new CreateToDoViewModel();
             BindingContext = vm;
             ToDoItem toDoItem = App.Database.GetToDo(id);
             ToDo.Text = toDoItem.TaskName;
             Priority.Text = toDoItem.Priority;
             Date.Date = toDoItem.DueDate;
             Time.Time = toDoItem.DueDate.TimeOfDay;
             updateID = id;
         public CreateToDo() {
             vm = new CreateToDoViewModel();
             BindingContext = vm;

OnCancel calls clear which just resets the input.  OnReview will push to the review page (covered next week) and OnSave delegates to the ViewModel the job of saving the contents of the input fields,

 public void OnSave(object o, EventArgs e) {
 public void OnCancel(object o, EventArgs e) {
 public void OnReview(object o, EventArgs e) {
     Navigation.PushAsync(new ListTasksPage());
 private void Clear() {
     ToDo.Text = Priority.Text = String.Empty;
     Date.Date = DateTime.Now;
     Time.Time = new TimeSpan(
           DateTime.Now.Hour, DateTime.Now.Minute, DateTime.Now.Second);

The View Model

The work of saving a new task is as simple as taking in the input from the user and then assigning each value to its appropriate property in the model.  The only complexity is in transforming the due date, which is done with a helper method,

 public void AddTask(string todo,
                     string priority,
                     DateTime dueDate,
                     int hour,
                     int minute,
                     int second,
                     int updateID,
                     bool isDeleted) {
     var newToDo = new ToDoItem {
         TaskName = todo,
         Priority = priority,
         DueDate = SetDueDate(dueDate, hour, minute, second),
         IsDeleted = isDeleted,
         ID = updateID,
 public DateTime SetDueDate(DateTime date, int hour, int minute, int second) {
     DateTime retVal = new DateTime(
     return retVal;


As we’ve seen in previous entries in this series, you will need an interface for SQLite and a file, which I’ve called ToDoDatabase which will get the Connection through the DependencyService, create the table and do the CRUD operations.  I won’t reiterate all that code here as it is shown in earlier entries.

Next week: the review page, and then on to iOS and Android.  I’ll take the latter two much more slowly as we’ve not seen as much of native code in this series.

About Jesse Liberty

Jesse Liberty has three decades of experience writing and delivering software projects and is the author of 2 dozen books and a couple dozen Pluralsight & LinkedIn Learning courses. He was a Senior Technical Evangelist for Microsoft, a Distinguished Software Engineer for AT&T, a VP for Information Services for Citibank and a Software Architect for PBS. He is a Xamarin Certified Mobile Developer and a Xamarin MVP and a Microsoft MVP.
This entry was posted in Essentials, Xamarin. Bookmark the permalink.

3 Responses to 52 Weeks of Xamarin: Week 13 – Writing It Thrice

  1. Hello my family member! I want to say that this article is amazing, nice written and include
    almost all significant infos. I would like too peer
    more posts like this .

  2. Pingback: Adam J Wolf: Weekly Xamarin Newsletter Issue #66 | XamGeek.com

  3. Pingback: Jesse Liberty: 52 Weeks of Xamarin: Week 14 – Thrice (part 2) | XamGeek.com

Comments are closed.