One of the minor issues we encountered when developing Falafel 2 Go was that on iOS, the ListView defaults the background color of the ViewCell to white. I’m not sure if this is an oversight, intentionally by design, or if it will be changed in the future, but we needed a way to make it transparent. Otherwise the textured custom background from the design would be covered up by the white background of the ListView on iOS.
Read more at the Falafel Software Blog: Adding Transparency to the ListView on iOS with Xamarin Forms Custom Renderer
We previously looked at how to create User Controls with Xamarin Forms to display an Image Button for the different activities in our Falafel 2 Go application. Now that we have these reusable buttons, we need to make them tab-enabled so that they can launch the appropriate activity. As we’ll see in today’s post, this is very simple to implement with Xamarin Forms.
Read more at the Falafel Software Blog: Adding Tapped Event Gestures to Any XAML Control with Xamarin Forms
In the previous post on making fancy layouts with Xamarin Forms we saw how you can design a Dashboard style application that stretches to fill any device size. However one of the challenges of the particular design we chose for Falafel 2 Go was the need to support the concept of an Image Button, where both the icon and the text work as a single control to launch an activity.
Xamarin Forms does provide an ImageCell control, which can be used in a TableView to render both text and image as a single control. However, this control is laid out horizontally with the text positioned on the right side of the image as you would expect for a list of items.
While we could likely acheive a more precise layout with a custom renderer, we found a much more elegnat, and more importantly, reusable option by instead creating a User Control.
Read more at the Falafel Software Blog: Creating Reusable XAML User Controls with Xamarin Forms
We’ve already seen how Xamarin Forms makes it easy to create cross-platform applications that share common layout and behavior. While the included controls like ListView encapsulate a lot of useful behavior, they don’t make for the fanciest layouts.
Read more at the Falafel Software Blog: Beyond the ListView: Fancy Layouts with Xamarin Forms
We previously looked how to create a Xamarin Forms App using Azure Mobile Services for storing and retrieving data. However, up until now, we have been saving the data globally so that it is accessible to all users. This post will explore how to add device-specific authentication to each app so that users can register and manage their own private data using any of the supported authentication providers.
Read more at the Falafel Software Blog: Using Xamarin Forms DependencyService and Azure Mobile Services to Add Authentication to Cross-Platform Apps
This post continues the series on building a cross-platform app with Xamarin Forms. Although the focus is to demonstrate using Azure Mobile Services, there is a lot that we can do first to improve the user experience of the app. Today we will look at how easy it is to add a loading indicator as well as automatically refresh the app views when changes are made.
Read more at the Falafel Software Blog: Loading Indicators and Automatic ViewModel Refresh in Xamarin Forms
In our last post (Creating Device-Specific Properties in Cross-Platform Apps with Xamarin Forms) we looked at how we can leverage Page Resources to create device-specific properties that can be reused across the page. Today we’ll look at how we can convert these and other reusable property definitions to global resources so that all of an apps resources can be maintained from a single location.
Read more at the Falafel Software Blog: Creating Global Resources for Xamarin Forms Apps
The previous post Cross-Platform Apps with Xamarin Forms and Azure Mobile Services demonstrated a simple Xamarin forms app to store and manage rebates. However, there were a few issues that impeded the user experience that should be polished up.
Specifically, there are some discrepancies between the different platforms, such as different font sizes as well as a missing Page title on the Windows Phone version.
Today we’ll look at how we can create and use page resources to create device-specific properties allowing us to update the Rebate Reminder app to create a more unified user experience.
Read more at the Falafel Software Blogs: Creating Device-Specific Properties in Cross-Platform Apps with Xamarin Forms
Inspired by Jesse Liberty’s fantastic blog series on learning Xamarin Forms, I decided to explore developing a fully cross-platform app of my own using Xamarin Forms. I thought it would be useful to explore how I can leverage Azure Mobile Services within the app to create a unified experience for a user regardless of which device they use, and allow their data to travel with them.
For this app, I’ve chose to resurrect the very first app I ever developed, Rebate Reminder. I wrote this app YEARS ago when was first starting out as a developer, and was an old Windows Forms VB app I wrote in .NET 1.1! I promised myself I would revisit it and make a REAL app of it someday, and it looks like that time is now!
Read more at the Falafel Software Blog: Cross-Platform Apps with Xamarin Forms and Azure Mobile Services
If you are working with Xamarin, perhaps in a shared environment, you may come across a new Forms Xaml Page that is in the file system but not yet included in your project. When you proceed to “Include in Project”, you may then encounter this error in the constructor of the ContentPage:
InitializeComponent does not exist in the current context
Read more at the Falafel Software Blogs: Xamarin Error: InitializeComponent does not exist in the current context