On the new iOS 7 most of the redesigned App´s does have a little blurry Header, especially Facebook or Instagram...
Does somebody know how to do that?!
There isn't a public API for it, however you can use the layer (or the view itself) of a UIToolbar to blur contents behind a view. There is an example project here.
Related
I understand that the UI elements will look different, and that is not what I am worried about. I created a simple app in Xcode 5 that just displays a label right under the status bar. In iOS 7 this looks fine. However, when I run the app on an iOS 6 device, the label appears too far down from the status bar. I know that in iOS 7, y=0 is the top of the screen instead of the bottom of the status bar, so I understand why this is happening, but I can't figure out how to fix it. I have seen solutions using self.edgesForExtendedLayout = UIRectEdgeNone, and others that use the deltas in Interface Builder when Autolayout is turned off, however none of these have worked for me.
How can I fix this (while still using Autolayout)? There must be a better way than just subtracting 20 px from the view's position if the system version is iOS 6.1 or earlier.
You can try using the iOS6/7 deltas on your UIViews in your nib files.
It's located in the size inspector of your UIView.
I think the answer you're looking for is in this tech note. (In short: apply a Vertical Space Constraint anchored to the Top Layout Guide of your view controller.)
Technical Q&A QA1797: Preventing the Status Bar from Covering Your
Views https://developer.apple.com/library/ios/qa/qa1797/_index.html
I discovered an Interface Bulder option named iOS6/7 deltas. Ok, I used this to set a free room for status bar (basically, I reduced UIViewController view contents height by 20pt and changed origin to 20pt). It worked fine, iOS 6 and iOS 7 look the same, but after that I installed it to iOS 5. Well, how can I fix that? Status bar shouldn't overlap contents, also there shouldn't be black space in the bottom.
My guess would be, the nib decoder implementation in iOS5 cannot cope with the values set in Xcode. My suggestion would be to perform your view "fixes" in code, after loading your view. You should also consider dropping support for iOS5, as it has a very small market share.
I have an already shipped app on App Store that made use of Storyboard.
I see from the keynote, comparing to previous model that iPhone 5 has a taller screen.
I wonder how this will impact on my esisting storyboard, because from my 'app point of view' there's only one difference which is the background.png. All the rest is just plain UITableView that can just fit more rows.
I cannot find any document for this on Apple site (I have always been so noob in finding things on Apple developer site).
Has anyone made adjustment to his already developed and published app to match with new layout ?
If yes, do I have to develop a brand new storyboard, or is there an adjustment to be done with code ?
[UPDATE]
I am reporting my experience, now that Xcode 4.5 is long shipped for development.
Xcode itself, as some suggested, asked me if I would like to enable tallest screen support by creating a default png. After saying yes, I had to enter each segue in storyboard for some adjustment, change png background (which was unstrechable by design) with a tallest one, change stretching settings and redeploy.
It has been an annoying work because I have quite some segues, and Xcode doesn't allow to reuse templates within Interface Builder.
Old apps without 1136x640 resolution support will run letterboxed, with black areas on top and bottom.
You can enable new layout support for existing project simply by supplying new Default-568h#2x.png loading screen. Take heed though, you'll have to test your old interface on both old and new resolution (via iOS Simulator) to make sure everything looks good and works as designed.
Its been said when iphone 5 is launched that your app view will be filled with black color on top and bottom if it is not taking account for the increase size ( not designed for iphone5 screen)
so your app will just work fine but will have black border on both and top to filled the extra space..
I saw mulitple apps using this, e.g. Facebook iPad App, Twitter iPad App .
How is it implemented, that multiple views can be draged in and out to the main view?
It seems as they are all in one chain of views.
I can't figured it out.
Thanks for your help.
Twitter and Facebook both do some pretty custom stuff for their iPad apps. They also both have lots of open source iOS code that helped them do it. Check out TWUI from Twitter and Three20 from Facebook.
A slightly easier way to do a similar effect is to use a UISplitViewController. A split view controller is kind of like the big brother of a UINavigationController on the iPhone.
You can add multiple subview uiviews on top of each other and move them when needed with cabasicanimation..
Also another and probably better way is using layers in quartzcore. You can addsunviews to layers and arrange them however you want. You can even make layers drop shadows and have rounded edges..
Feedly for iPhone comes with cool design especially its custom pagecontrol(scrollbar?) placed on the top.
I'm developing an app for iPhone, and to use spaces efficiently as much as it's possible I'm trying to find a way to implement custom pagecontrol like Feedly. I actually think it's possible the app is made with HTML5 and CSS? Although I am not sure. I found some custom opensourced pagecontrol frameworks, but they're to do with something else such as dots' colors either sizes.
Here's example image link to Feedly for iOS http://i.stack.imgur.com/wf595.jpg
Although this is an iPad version, basically iPhone one is the same. You see the green bar just below the status bar, if you slide pages the colored bar scrolls. It's much more like scrollbar.
Thanks.
Okay, so I unarchived the app and it turned out it's mainly made with HTMLs and converted using PhoneGap. I'm not going to use HTML in my app, my journey still goes on...
Putting all contents into an UIWebView (implementing in HTML & CSS) is generally a bad idea performance wise.
What Feedly seems to do is use an UIScrollView.
The ScrollView sends several events including when it's moved and tapped.
They then update the green scroll bar on top whenever the ScrollView is moved.
Likely, they will also load the actual contents within the ScrollView as the user approaches their position to conserve memory.
You can implement something like this yourself in a few days of coding work.
(Disclaimer: This is just how I would implement what you showed. How it is actually done - only Feedly knows.)