Hi friends and experts,
I have 3.2 Years of experience in ASP.NET and Sharepoint 2007 as well.
I have got an offer from some USA Based MNC recently the profile is for Mobile Applications.
Package is more that I expected but they are asking 2 years Bond. the probation is 1 Year.
the Interview Process through out went on only .net only.
They said the posotion offered is Software Engineer for Mobile applications with the technologies used in that company are
OOPS concepts and Objective-C .
the mobile applications IS IT EASY OR DIFFICULT compared to .NET ?
they said they will train the employees for necesary skills.
I have some questions to ask.
Why is it they want .NET background for iPhone applicationS?
Is it fine for me to switch into mobile applications?
How would be my growth in that platform?
Please kindl guide me the with the suggestions for Short Term and long term advantages and dis advantages for this issue
thanks in advance
Sainath's Advice on Sunday, February 26, 2012 :
Let me make an attempt to answer your questions.
1. Is the mobile applications area easy or difficult compared to .Net?
Firstly, please do not look upon it only as an opportunity to build applications for the iPhone. If you do some research on the Apple website, you will realize that indirectly your skills will be portable to the iPad as well as the applications you will build are targeting the iOS. For the benefit of other readers, the link is provided below:https://developer.apple.com/devcenter/ios/index.action
As you have already stated and from what I have seen on the website, your primary development language will be Objective C. The IDE support also looks pretty good. My personal judgement is that Objective C may be a little difficult compared to .Net. however, this should not be the stopping factor for you. The fact that you have been selected means that they feel that you possess the ability to work in Objective C. At the end of the day, your success will depend upon your grasp of C, Objective C, OOPS and also some key design patterns like MVC which have been explicitly mentioned on the Apple site.
2.Why is it they want .NET background for iPhone applications?
My hunch is that they might be finding it difficult to find Objective C experts. And the core basics like OOPS, MVC are the same. The fact that they are asking you to sign a 2 year bond with a 1 year probation period also seems to support this. The 1 year probation period means that they may put in substantial effort to provide you training in the necessary skills required to build iPhone applications and hence this lengthy probation period. The 2 year bond means that they do not want to risk losing employees to attrition after investing so much in their training. But 1 year probation also induces some risks - as your confirmation as an employee will take 6 months more than the standard industry practice. I would encourage you to research the organization thoroughly on many counts and come to a fair evaluation of the same. Please check one of my earlier articles on this topic:http://www.dotnetfunda.com/articles/article1441-choosing-the-right-employer.aspx
3.Is it fine for me to switch into mobile applications? How would be my growth in that platform?
Firstly, this is not just a switch into mobile applications. It is a switch from .Net applications to building iOS applications. First and foremost, you should be absolutely sure about the organization which you are joining. It should be a good one - as this change may be a long term one for you.
The success of any mobile platform depends on the quality of applications which are on offer on it.The iPhone is certainly the market leader in this area. Ongoing success in this area will primarily depend upon the quality of applications which continue to get added to the iPhone.
One more point - this is a relatively niche area. The thing about niche areas is that - you typically get paid more than the market average as the supply of IT professionals does not meet the demand requirements. At the same time, the volume of opportunities available to you is on the lower side. It is a double-edged sword. But some degree of risk taking is okay. Risk and return always go together - at the end of the day, you should have full confidence in your own skills and ability to manage yourself should a problem arise, if at all.
I hope my answers have provided some food for thought.