All in Xamarin

Reading a SQLite Database

Reading a database will be very straight forward, especially once you know how to establish the connection to the database, which you should already know thanks to our previous post.

All you have to make sure of now is that when reading, you get all that data in the correct format, not as a simple query to a database, but as an actual list of elements. So in this lecture I cover how to do exactly that.

Gesture Recognizers in Xamarin Forms - Tappable Label

Quite often you may want a XAML label to respond to touch gestures. It may be the case that your label must behave as a hyperlink to a website, or perhaps your terms of service and privacy policy (which is a typical scenario in which we add hyperlinks).

By default, XAML labels do not have any events that we could use in this scenario, so your first option may be to create a button and try to make it look like a simple Label (on iOS this is easier than on Android, where buttons always have a background and very distinctive edges).

Inserting to a SQLite Database

Well, now that the Model is ready, and the database is created for both Android and iOS scenarios, there is nothing left for us to do but to start adding the functionality for the necessary requests inside of our application.

In this video, I start by explaining how to insert to the database, and how a specific usage of the using keyword will be rather important for you to understand.

SQLite Xamarin Forms Tutorial - iOS Database Path

When using SQLite inside of your applications, you will need to set the location for the database file.

In this video I cover what you have to do for the iOS scenario, which indeed will be slightly different from the Android one, which means that we will have two versions of the same code -one per platform- and that we will need to code some functionality in the platform-specific projects.

SQLite Xamarin Forms Tutorial - Android Database Path

When using SQLite inside of your applications, you will need to set the location for the database file.

In this video I cover what you have to do for the Android scenario, which indeed will be slightly different from the iOS one, which means that we will have two versions of the same code -one per platform- and that we will need to code some functionality in the platform-specific projects.

Adding NuGet Packages to a Xamarin Forms (starting with SQLite)

So SQLite can be quite useful in a lot of scenarios. I believe most apps should use this light-weight version of a database, even when they rely on another cloud database for their information.

But before we learn how to implement SQLite into our apps, let’s first take a look at how can we add third-party functionality into our apps, so we don’t have to code SQLite functionality from the ground up.

Dynamic-Colored Progress Bars - iOS Custom Renderer in Xamarin Forms

Using XAML in Xamarin Forms we can change the accent color of the Progress Bars we define, and being able to set it to a HEX value, the possibilities are endless (well, not exactly, only about 16 million, but you know what I mean).

But what if you want that color to change dynamically, say, depending on how much the progress bar is filled, especially if you're going to keep your code-behind as clean as possible, so no handling of events and messy code.

Bottom Android TabBar - Xamarin Forms

Something that I haven't always liked about Android is the top-side tab bars. You know, those that can take you from one page to another very easily without reaching your finger too far onto the screen or opening a side menu. I love bottom tab bars, iOS has always had them, and I use them a lot.

Handling Landscape and Portrait Modes in Xamarin Forms

In the previous post, I showed you how you could handle multiple states for a specific element using the VisualStateManager and defining various groups and VisualStates.

In this post, we will use this same feature to change the UI of an example application so that it hides a title when the device is on portrait mode, so there is more space for the main component of the interface, which will be a ListView.

Handling Visual States in Xamarin Forms

If there is something that can take a good-looking app to an incredible-looking app that may very well be Visual States. By defining different Visual States you are able to define how a certain element must look depending on some interaction from the user. The simpler example is with buttons, with which you are able to see when someone hovers over them (perhaps they change color), someone presses them (maybe in addition to colors the scale also changes), maybe also when they lose focus.