sure, but the benefits of using C# with MonoTouch over Objective-C is not because you don't have to learn Objective-C but that it can be a more productive environment to write the bulk of your code.
so if you love C# and know how Objective-C works, this is a great framework, lame I'm not truly a fan of C#.. So i guess it won't be a time saver for me.
Comments
Good reasons not to use it:
* you are only interested in developing for one platform--ios.
* you have obj c and any other language talent in house, but don't have c# talent
* you need to use tons of custom native libraries that the framework doesn't have bindings for
* you want to avoid vendor lockin
3rd one is easy to work around. generating bindings is easy.
But for that you don't need to know Objective-C?
sure, but the benefits of using C# with MonoTouch over Objective-C is not because you don't have to learn Objective-C but that it can be a more productive environment to write the bulk of your code.
so if you love C# and know how Objective-C works, this is a great framework, lame I'm not truly a fan of C#.. So i guess it won't be a time saver for me.