>Hi Bonnie, see my reply to John and Viv - did you get to play with Xamarin ?

Hi Pete,

I never got a chance to play with Xamarin this weekend, I played with cameras intead ... we're going to Yosemite in April and have decided to make it a photography trip, with tripods and fancy cameras. So, I've got to get used to using Gary's digital Nikon D700, which I haven't used before. So I've been practicing a bit on the weekends. He's going to actually use a film camera (a medium format View camera), but he hasn't used it in maybe 10 years. He'll also be developing the film himself ... something he's done before, but that was more than 30 years ago. So, he's been practicing too! < g >

Anyway, today might be a good day to play with Xamarin, since we have the day off from work (President's Day ... this company gives us strange holidays, I don't think I've ever worked for a company where we had President's Day as a holiday).

I see from your replies to Viv and John that you're thinking of going the web app route instead. That's not by bag either, in fact I wouldn't even know where to start!

I agree with Viv that a web app would not be as "slick" as a native app.

John also makes a good point about Xamarin being overkill if you're only going to be targeting one platform, Android. However, my argument for using Xamarin is that the code and the development environment will be something familiar, C# and Visual Studio. And what happens if you don't use Xamarin and then they want the app for iOS too?

Anyway, just my 2 cents. I'll be messing with Xamarin in a few hours from now and I'll "report" back if I learn anything useful!

~~Bonnie