Hi! Thanks for your nice comment! ;). So Java backend vs iOS - interesting choice. My opinion is that there's much more work in Java so the market's very good. And also as regards tooling and suchlike, I think Java really has the edge. I tried doing some development with the iphone quite a few years ago now and I just didn't "really feel it" as far as developing in xcode (iOS's mandatory IDE) - I use Apple stuff myself and from a consumer electronics point of view, I wouldn't go to anything else. As a developer though, their developer experience leaves a lot to be desired (but that's from a few years ago!). So that's something to consider. Plus Java is mostly open source, so you can always "see inside" the libraries you're working with by stepping through them in a debugger, not the same in iOS too. Objective-C, clunky as it was, was replaced by Swift - which seemed to be nicer - but I personally found it more convoluted. But at the end of the day, maybe try both and see how you feel - or watch some tutorials on both and see what resonates with you. You can always jump ship if you don't get on with one specifically and whatever you learn is always useful to gain perspective. Good luck in what you decide though - have a good day! :)
Hello and thnks a lot for your videos i m struggling to choose between java backend or ios development any advice ? Thnks
Hi! Thanks for your nice comment! ;). So Java backend vs iOS - interesting choice. My opinion is that there's much more work in Java so the market's very good. And also as regards tooling and suchlike, I think Java really has the edge. I tried doing some development with the iphone quite a few years ago now and I just didn't "really feel it" as far as developing in xcode (iOS's mandatory IDE) - I use Apple stuff myself and from a consumer electronics point of view, I wouldn't go to anything else. As a developer though, their developer experience leaves a lot to be desired (but that's from a few years ago!). So that's something to consider. Plus Java is mostly open source, so you can always "see inside" the libraries you're working with by stepping through them in a debugger, not the same in iOS too. Objective-C, clunky as it was, was replaced by Swift - which seemed to be nicer - but I personally found it more convoluted. But at the end of the day, maybe try both and see how you feel - or watch some tutorials on both and see what resonates with you. You can always jump ship if you don't get on with one specifically and whatever you learn is always useful to gain perspective. Good luck in what you decide though - have a good day! :)
@ thnks a lot for your detailed answer
No worries, happy to help!