While using the built-in settings system may seem useful, the point of using the Xamarin range of products is to be able to use a large amount of the same code on any platform that now supports .NET
. While, at the time of writing, Windows Mobile is languishing at around three percent of the market share of all smart phones, Microsoft is unlikely to allow this to continue and will push their massive reserves into getting people to adopt their smart phones. If you want the pure mathematics, 97 percent of all smart phones can be coded using the .NET platform. (Blackberry has a port of mono for it, but it is not well supported and so can be discounted.)
This, therefore, requires a different strategy for storing user settings. We could use an SQLite database to store the details, but, as has been pointed out, each access to the sub system will cause a performance hit.
The simplest way is to create a settings
class and serialize or deserialize the values as and when...