How to keep IOS 6 design in my application on IOS7 - ios6

I want to keep my IOS 6 design on a IOS7 device. I build with the IOS6 sdk but the interface is still with IOS7 controls on a IOS7 device.
How can I keep my IOS6 interface ?

Not recommended by apple, but develop your application with XCode prior to XCode 5, application's look and feel will remain same as iOS6 in iOS 7.

You can see both versions designs in interface builder.

Related

ExtJS 4.2.1 in Mobile Browsers

Can the applications developed for desktop browsers using ExtJS 4.2.1 will work fine in the mobile/touch devices with out any resolution issues. Please suggest do we need to do any changes for running the application in mobile browsers.
Extjs 4 and below is not optimised for use on mobile devices, so I doubt this is much you can do to overcome your resolution issues.
Extjs 5 is targeted for both desktop and high end tablet devices such as iPad and Galaxy Tab.
Sencha Touch offers the best support for the most number of mobile devices whilst still working on HTML5 supported desktop browsers.
Note - they have announced they are merging ExtJs and Touch. More details to follow at their upcoming SenchaCon event.
ExtJS 4 can work OK on tablet devices.
For mobile browsers or hybrid mobile apps consider work in Sencha Touch.

When using Xcode5, how do I decide how the app will look? iOS7 or iOS6 style

I have some apps developed using Xcode4.
When opening the projects and build them for the 5 simulator using Xcode5, most of the apps will look iOS7 style when built for 5 simulator while some still looks iOS6 no matter what I do
The apps are pretty much the same so I do not understand how to decide myself which style it is going to be.
Looking at the settings I do not see any difference.
The app which is built as a iOS6 like style seems not possible to change to iOS7 style, and some apps are built as iOS7 style as default and is not possible to change to iOS6 style using Xcode5.
Please help!
Depends, most of the standard UI elements are redesigned in iOS7 (UIAlertView for instance), you can't do a lot, if you want to keep the ioS6 look you should rebuild all these components by yourself.
Elements that adhere to the appearance proxy can be customized to look like pre-iOS7, but it will be a hard job.
In iOS7 you also have another "problem" to manage, by default all views are full-screen, this is simply to solve if you deploy only on iOS7, bit harder if you deploy for prior iOS7 and iOS7.
There i a way around... download the 4.6 version of xcode ance deploy only on iOS6, most of the UI elements will maintain the same aspect, it seems that Apple still accept <=iOS6 binaries.

ios6 ios7 xcode4.6 xcode5 dilemma

I was building an app in xcode 4.6 (ios6.1) and everything was fine.
I ran the same code through xcode 5 (ios 7) on an ios7 device and simulator, and I ran into the full screen (status bar included) issue, horizontal scrollview issues, modal viewcontroller issues, et al.
I’m using a navigation controller with the bar turned off. Instead I’m using a custom view to pass for a bar. So the extendedEdge thing isn’t working as well.
I understand that eventually, I’ll have to update my design and implementation accordingly.
Now here’s the dilemma – I ran the app (backed up original code) from xcode 4.6 (ios6) on an ios 7 device, and it’s working absolutely fine. It’s leaving it’s gap for the status bar, and there are no issues at all.
What I can’t understand now is how to proceed?
Will the app be accepted if I continue working on xcode 4.6 with ios6 (since it’s almost finished)?
I’m not able to move to xcode 5, since it has only the latest ios7 as the Base SDK.
I can’t find a legitimate way to add ios 6 sdk to xcode 5 (except copying the 6.1 SDK to the xcode5 package).
And, if I hadn’t downloaded xcode 5 DP (which installs it separately), the mac app store would have updated my xcode 4.6 to xcode 5
Apple still accept applications submit through Xcode 4.6
But consider that you would loose some new functionality like having different icons to each OS version etc.
Moreover, your app won't use the 64-bit processor (it is still compatible but if your app is a game or something like that it is recommended to use it).
I assume that in few months you won't be able to submit apps using the old Xcode.
UPDATE:
For you to be able to use status bar as before (like hidden), in your apps plist file add a row call it "View controller-based status bar appearance" and set it to NO
Just to update people who might be looking for an answer to this -
Apple will only accept apps and updates made with Xcode 5 on iOS 7, effective 1st Feb 2014.

UITabBar autorotation for ios4+

at the moment i have developed an ios tab bar application the rotates perfectly on the iphone simulator(ios 6.1). The problem is that when i run the app on my real device (ios 4.3), the app works perfectly but it doesn't rotate.
Has anyone got any ideas? Is it possible to support rotation for all three o.s's: ios4, ios5 and ios6?
Prior to iOS 6 i.e in iOS 5 and earlier, an app and a view controller’s default supported interface orientations are set to UIInterfaceOrientationPortrait for iPhone idiom & UIInterfaceOrientationLandscape for iPad idiom while in iOS 6 and later this is UIInterfaceOrientationMaskAll for the iPad idiom and UIInterfaceOrientationMaskAllButUpsideDown for the iPhone idiom.
This might be the reason for your views not rotating in < iOS 6.0. Rotation process and responsible controllers are also different in the 2. Autorotation is clearly explained here in this post- Autorotation in iOS

App development for HP Slate (Slate, Windows tablet)

I was wondering how the SDK is or if there is one for the HP Slate.
Would the apps be better off as a WPF app or a Silverlight app running off a browser on the Slate machines?
I understand that it's just a Windows 7 tablet, but I'm not sure if there are any differences.
You should look at the Native Extensions for Silverlight.
check out here http://msdn.microsoft.com/en-us/library/ms704849(v=VS.85).aspx
i believe windows 7 has all the stuff built in for the stylus and such. As for wpf or silverlight, it all depends on what your goals are for the application. determine if it will be something that will be over the web or if it will be something done on its own LAN and go from there.

Resources