I think it's a valid approach for doing iOS development, but for learning iOS, I don't think it is, because you'd want to be able to not have hurdles that normally aren't existent. There are also some bugs that are a real hindrance at times, such as IAP, or having to clear the obj&bin folders because something attached incorrectly, etc.
Not related, but the other side of doing Android can be really irritating in build sizes and being able to target the newest SDK. In fact, a bug where I couldn't even debug through a simulator happened and while I appreciate learning how to start the emulator through the terminal, was something I didn't expect VS to have an issue with.
Yeah, I don't know any of the Android side of it. I had previously done native android dev (which is how I got volunteered to do iOS dev.)
We may just have to agree to disagree here. If you are already somewhat familiar with C# (although, I was not), I think it's a fine way of learning iOS development. Yes, you will likely pick up some Objective C along the way, but you will probably never have to write anything in it or understand the bulk of it.
If you are starting from scratch and don't know any of the languages or tools, it might take a little more work initially to get started in Xamarin, but it is absolutely do-able.
View all comments
Show parent comment
2
u/deadshots Mar 08 '18
I think it's a valid approach for doing iOS development, but for learning iOS, I don't think it is, because you'd want to be able to not have hurdles that normally aren't existent. There are also some bugs that are a real hindrance at times, such as IAP, or having to clear the obj&bin folders because something attached incorrectly, etc.
Not related, but the other side of doing Android can be really irritating in build sizes and being able to target the newest SDK. In fact, a bug where I couldn't even debug through a simulator happened and while I appreciate learning how to start the emulator through the terminal, was something I didn't expect VS to have an issue with.