When you write enterprise mobile applications you’re always confronted with authentication. There are a lot of examples that show you how you can authorize the user with Facebook. I don’t know about other countries, but in Belgium enterprise companies don’t let you login on their corporate environment with your Facebook account. You can use Xamarin.Auth for authorization with other services than Facebook, but if the authorization flow is a bit different, you can’t use it anymore.
Last week I gave a Xamarin session to students of the PXL in Hasselt (Belgium). You can find a lot of tutorials about Xamarin, but most of the time they only point towards 1 specific topic. When writing a real world app you can’t get your boss satisfied with a hello world.
When scrolling through all your open apps on your mobile phone, you get a quick look of what the window will look like when you reactivate the app. For some apps (like banking apps) you don’t want data leaked via the preview image that was taken when the app was backgrounding.
Akavache is an awesome library to use when it comes to caching. It’s fast, cross platform and it abstracts the complexity of working correctly and fast with sqlite.
I’ve been programming some Xamarin Forms apps. Setting up a good solution and structure your code isn’t always easy. The Xamarin frameworks are evolving fast and the setup you did some months ago suddenly doesn’t feel that appealing anymore. The way Xamarin.Forms handled navigation changed dramatically over time, the way they handle lists, supporting fragments for Android…