Whatever you can do in XAML, you can do programmatically in the code-behind file.  As Xamarin Forms is based on an object-oriented hierarchy of UI elements, you can create new instances of a user interface control, set its properties, and call its methods with code. Controls or elements created in XAML can be accessed in the code-behind file by name, or by index if they belong to the child collection of another control. While you can code an app's entire UI in the code-behind file, XAML was developed to separate the user interface from functional code. From a development point of view, the combination of XAML and hot-reload is a massive time saver for fine-tuning the interface. Having to recompile and run the app every time you change a UI element in the code-behind file is literally programming from the last century. As we've seen, manipulating the UI with code does have its place but should be the exception rather than the rule. My name is Hallam Webber, and I hope you've found this Building a Xamarin Forms UI: Code Behind course instructive.