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 an old application in 2 different projects , for iPhone & iPad, historic reason.
These application have developed since ios5.
I want to unify these 2 application and i have a dilemma.
To Create a new universal project using ARC & Storyboard & auto-layout OR continue with one of the platforms for example iPad and insert the iPhone logic there.
(Each way will cause a lot of work)
I'm not looking for the quickest way, rather i'm looking for the best way.
I don't know if moving to ARC & Storyboard & auto-layout will worth it (Considering the fact that the code is already written)?
The only benefit i can think about is when apple will release iPhone 6 the adaptation will be simpler (OR NOT...)
Thanks :)
It would be better to update to the universal project with ARC etc. It will be much more future proof. Also updating to use iOS7 will allow you to use the newer framework changes.
There are rumours that the new iPhone will have a bigger display / more display options. So you will want to make the most of the auto-layout functionality
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 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 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.
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
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
I am currently developing a iOS framework for other developers to use. I intend to use "ECSlidingViewController" framework and add it a webView to that Slide-Up. I already have it working on two projects but they all use storyboards in it.
My search for sample projects to test my framework raised a big question. 9 out of 10 of this samples didn't use storyboard.
So my question is: Should I start developing my framework for non-storyboard apps or is this situation only happening in sample projects.
What do you mean by sample projects.
All applications prior to iOS 5.0 are non-storyboard type.
If you intend to support versions prior to 5.0 only, you have to leave out the option to support storyboard.
If you are supporting older as well as 5.0 + versions you have to build it for storyboard as well as non storyboard applications.
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
say my goal is that both users of iOS5 and iOS6 should be able to use my application.
What shall I do in order to achieve this?
For example, what I know is, I could set Base SDK to 6.1, and Deployment target to 5.0.
Then, in the code I should ensure I don't use iOS6 specific methods (or use code branching with respondsToSelector if I use iOS6 specific methods).
My question is: should I pay attention to anything else, in order to achieve the goal I mentioned above?
Thank you.
You should set the base SDK to 5.x, because that will not allow you to use ios 6 specific features. Though, support for the twitter feature will not work since they differ by operating system. The best option would be to drop the sdk as low as possible and test it, if it does not work, raise it, and then test again, until it works.
Make sure you do not use autolayout, also note that it becomes increasingly difficult to support the two different sized iPhones natively when taking this approach (because of autolayout). Although per Marcus's comment, this is required. Also, you might as well support iOS 5.1 as anyone who has 5.0 can upgrade (and should).
Lastly, definitely test on both iOS versions. There may be some unexpected outcomes, even small ones (like animation effect for modal form sheets with iOS 6 vs iOS 5).