Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Are there any changes in Objective-C syntax and version overtime like Python and PHP. Can I use Objective-C that was taught 3 years ago and use it today to make my app.
As usual, it is always a balancing act. You can use all your previous knowledge, but you do not want to be stuck in the past, especially when there are advancements in the compiler every year. Things like ARC, removal of #synthesize for properties and the new literal syntax will improve your code greatly and save your time. I think before you start development, you watch the last three years' WWDC videos to see what's new in the language and compiler, and decide which you would like to learn. The changes are indeed rather minor in the grand scheme of things, so you have nothing to worry about.
Yes you can. Since then the objective c does not have changes that makes impossible to you to do your app.
But since then the iOS version suffered major updates (like ARC, iOS 7, etc) so I recommend that you take that in attention before you start your new app.
Same syntax. Just learn GDC, ARC and you ready to go. New APIs appearing in every new iOS version, but the language stays generally the same
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Coming from Android, I got used to Dagger as my main DI framework.
Recently, I joined a new iPhone project written in Objective-C which have no DI framework.
I would like to add one to our project, and I wonder which one is the best one to use, when it comes to simplicity and performance.
I would like to hear your opinion and experience.
Thanks!
Dependency injection is a popular design pattern in many languages, such as Java and C#, but it hasn’t seen widespread adoption in Objective-C (yet!).
This is an excellent read to get you started on DI is Objective-C. Additionally, you'll find this, this & the Grand Daddy this indispensable for DI in iOS.
This framework seems to be making a lot of noise these days.
In my personal experience, more than anything else DI helps you a lot in testing. It's not all or nothing approach (which is common for many design patterns) allows for easy, no-cost adoption & definitely valuable returns.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have developed an application for ios7 using Objective-C. Its in development phase now. As apple has announced new programming language swift. Will it replace objective-c or both we can use for future development?
I tried to check any update about this, but couldn't get anything.
Objective-C will still be around for quite a while. Apple did not deprecate the language, but it has declared that Swift will be the future of iOS development.
Source:
Swift Programming Guide, Page 2
we can now introduce a new language for the future of Apple software development.
YES.
With the iOS 8 Beta, Objective-C-Only project works.
Though as Matthew notes, you should slowly adapt to Swift.
I would not start a new project in Objective-C though, if there aren't very good reasons for it.
You can have Objective-C code side by side with Swift code and should migrate code to the new programming language. So it is possible to use the old Objective-C frameworks/files in a new Swift project.
You could even use almost C Code, but that is mostly making the project more complex. The same goes with Objective-C and Swift.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Giving that there are many new features specially in memory management, I have iOS 4 / 5 books and there are links to tutorials everywhere for them.
What is the minimum that I should read to take advantage of new features and do not have to 'unlearn' stuffs found in newer versions?
EDIT:
There are some good books about iOS 4/5. Should I avoid them?
Start with the newest SDK and developer tools, Xcode 5. Learn about what's possible with iOS 7 and iOS 6. Don't spend too much time on iOS 4 and 5. Focus on learning about frameworks and not on particular OS versions.
You should still learn about old-style memory management, release and retain methods to understand how ARC is dealing with them for you. However, don't spend too much time on reading. Start coding. Nothing will replace a hands on experience and you learn much quicker when you deal with real projects and real problems.
Focus on iOS 7. There is a quite a bit different in iOS 7 from previous versions, spending time on previous versions is only going to confuse you and make it harder to learn.
Focus on a project and get it built, thats the best way to learn.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I am looking forward to learning XCODE, what is an appropriate approach to mastering ios programming. I want to know precisely, in order, what I should learn to know XCODE. Since there are different aspects to XCODE, I am confused on where to start. Such as COCOA, objective-C, etc. Can anyone provide me with a solid plan that will give me a solid programming skills with XCODE? Thank You
Start with a good book that teaches you Objective-C with Xcode 5.
Stephen Kochan has a good one.
That will get you going.
But check a few to see what makes sense to you.
Just make sure it has Xcode 5 so you don't get lost.
After you get through a bit with Objective-C you should fill in what you need of C.
C is not hard but it is truly agnostic from frameworks that really do interesting things so it makes learning C first rather challenging.
(Like learning math without any real idea why or what to use it for)
In the end though, expect a long road of perpetual learning. You will feel overwhelmed at times. That's normal.
Nobody knows all if it and the masters have years of experience and knowledge.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
At my company, we're trying to evaluate between using storyboards (the more recent Apple supported tool) and xib files (the older tool). Technical differences aside, a concern that has popped up, is that since Apple appears to be pushing for using storyboards in new development, they will drop support for xib files in the future.
At this time (January 2014), is this a valid concern for iOS development?
To avoid this from becoming an opinion-based question, let me also ask - has there been any official indication from Apple on the matter?
Apple usually gives a notice period before they drop support for something, so if they haven't said anything, I guess it's reasonable to conclude that they will continue to support the xib approach.
No, Apple has not officially stated anything when it comes to deprecating XIBs in favor of storyboards. Chances are both will remain for the time being, as they're both useful (sometimes you don't really want or need a storyboard and a standalone XIB will suffice). Anything beyond that would be speculation that seems better left to bloggers.