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.
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 3 years ago.
Improve this question
Currently i am doing IOS App Development and my projects works under AFNetworking Lib V3.2.1 also i am slowly migrating my app into the Swift with AutoLayout.
My clarification whether will get the AFNetworking Next version for Objective-C?. Because this lib last they was updated on May 2018 and its getting older now a days.
Better can I switch over my project into Swift with alamofire network lib.?
Suggestion require to proceed further.
For Objective-C there will be no further updates. Apple now recommends to use swift in every project so why go for objective-c now as its old. Alamofire is very good wrapper written for networking.
I would suggest you to start migrating your project to Swift by using Bridging-Header which serves purpose of using Swift & Objective-C in same project.
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
I developed task using Xcode v8. But now I need to be able to open it in Xcode v7.
I have needed version of Xcode. But I cannot open Files and perform build.
You can use Xcode 7 but you will need to change all the syntax manually. There is no converter available for downgrading.
If your code is completely in Obj-C then it will not be a problem for you, but for swift you will end up with a lot of changes.
If you want to test your functionality you can download lower version simulators and add device with that OS.
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 8 years ago.
Improve this question
I wanted to check if its possible to build iOS app with both 32-bit and 64-bit support without using the new Unified Apis in Xamarin. Unified API support will require code changes in existing Xamarin iOS apps which are using MonoTouch Foundation and we want to avoid that.
Any pointers will be welcome
Thanks in advance!
No it is not possible to support 64 bit apps with the classic API. This is explained in the Xamarin blog post: http://blog.xamarin.com/unified-api-with-64-bit-support-for-ios-and-mac/
It is actually quite easy to update to unified, so i don't see a reason why you want to avoid that, also because it will be a requirement of Apple soon, and you can't publish new updates anymore after there deadline. For more information on how to update see the Xamarin documentation on that: http://developer.xamarin.com/guides/cross-platform/macios/updating_ios_apps/
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
I learnt how to program in iOS 6(mid-scale apps) in a university course last year. I was wondering, how much challenging is it to make a transition to iOS 7? I tried to check out for an iOS 7 full change-log but I only found info related to added features.
Not challenging at all. If you want to use some of the new API's then you will need to learn them. Creating a 'mid-level' app however has remained very much the same.
The major differences are 'stock' element appearances but they are created the same way. Also views are now 'full screen' so that can be confusing at first if you aren't aware.