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).
Related
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 5 years ago.
Improve this question
How is it with the copyright? For example I have linked a button to a Facebook page in my App and on the Button I've put a small image of the Facebook Icon, where do I have to mention the copyrights?
And Code copied from Stacksocial doesn't have copyright?
I have some really small Images in my App, is it important to convert them for 2x 3x ? for example:
https://imgur.com/a/88p8E
With the new release of Xcode 9 and ios 11 I have a warning: update to recommend setting. And I tried but it destroyed my App because the frameworks needed to update as well. Can I ignore the Warning? Because the App works just fine on ios 11.
Thank you very much! :)
If unsure how to deal with copyright, a lawyer is your best friend. A 1hr consultation should be more than enough to give you an introductory tour of this world and make you feel at ease. Highly recommended if you have no clue what are you getting into. A good online resource to get to know what the different typical open source licenses are and what they mean is Licenses & Standard | Open Source Initiative
It is typically a good idea to provide all pixel density images, if you don't have them or want to easily generate the various images, there's a good tool on the Mac App Store named AssetsProcessor
You should typically apply the update to your project but not to the framework. That does mean that you will have build warnings; something you have to learn to live with until you feel comfortable branching off the different frameworks and updating them yourself. Overall yes, learning which warnings are safe to ignore and which ones should be addressed is important. There's no magic here, except TEST, TEST and TEST to ensure that ignoring a warning won't be the death of your app.
Good luck!
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 6 years ago.
Improve this question
I need an app that can create click/drag macros to interact with other apps or the system in general.
From searching on the app store, and online, the closest thing I could find was autotouch, which could be used to simulate rapid clicking. However, this isn't nearly close enough to what I need.
Thus, I tried to look up the relevant functions so I could write the app myself. Unfortunately, I could not find any prior discussion of this problem.
A good description of the functionality I am looking for is the way TestComplete's Drag method works.
Unless I missed something, there's no straightforward way to create click/swipe/drag macros that work across apps in iOS.
So are there any "hacky" methods to accomplish this task?
Example usages:
create a macro for navigating between menus in another app
clicking very specific spots in a very specific sequence in another app
quickly change settings/configuration in another app
Apps submitted to the iOS App Store are required to be sandboxed, meaning each app exists in its own isolated environment in the file system and is only allowed to interact with the outside system via approved public APIs defined in Apple's frameworks. This, of course, is for security reasons, and no Apple frameworks provide the functionality you want. I would also imagine that enabling apps to control other apps via gesture macros is not something Apple is likely to support in the future, given that even system-wide screen-recording apps are currently banned.
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
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 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 have following question.
Say I want to start to write an app in one month.
What are the advantages and disadvantages if I:
1) Write the app such that only users of iOS7 can use it.
2) Write an app with iOS6/5 in mind. Meaning app is not optimized for iOS7 (e.g., UI etc.) - however due to forward compatibility I assume iOS7 users can still use it.
3) Write an app that is optimized for iOS7 but users of iOS 6 can still use it.
Example advantages and disadvantages.
The disadvantage of supporting only iOS7 maybe that users with other version of iOS can't use it.
Disadvantage of optimizing app for iOS7 while it is usable also for iOS6 may be a lot of work.
In this fashion, I hope that the users here will help me list advantages and disadvantages of the three items I listed initially.
If you're using public, non-deprecated official iOS SDK ( at that time this answer is written, the current stable version is iOS 6.1 ), you can support iOS 5 & 6. The current stable (non-beta) Xcode cannot support iOS 7 development yet.
Also, always support as many non-retiring versions as possible. You have to (compulsory) support iOS 7 in near future, so your choice would only be supporting iOS 5 or not.
Note: Since iOS 5 & iOS 6 are quite similar, supporting iOS 5 won't make you write a lot more codes.
In addition to above :
https://stackoverflow.com/questions/17207126/release-of-ios-7-affecting-development
Application must be compatible with both the latest version and second last version.
So, once iOS 7 is released fully, make your app compatible with iOS 7 also. It will increase your sales.
Your development target has to be iOS 5 when developing the application. There is not much difference in terms of view in iOS 5 and iOS 6, but some features may not be available because of Frameworks advancement. So, take care of that.
Hope this helps !!