Back to Blog

iOS8 Day-by-Day :: Day 17 :: Live Rendering in Interface Builder

Posted on 12 Aug 2014 Written by Sam Davies

Updated 9 Apr 2015: This post has been updated to Swift 1.2

This post is part of a daily series of posts introducing the most exciting new parts of iOS8 for developers – #iOS8DayByDay. To see the posts you’ve missed check out the index page, but have a read through the rest of this post first!

To enjoy each of the 39 posts all in one place, you can now also download the iOS8 Day-by-Day eBook free from our website! 


Custom views are a great way of both splitting up your code as a nod towards software design best practices, but also allowing the creation of resusable components. I’ve talked about this concept a lot in terms of building custom UI Controls – in fact I’ve given a fair few talks on the subject.

One of the limitations in the iOS world with this technique is that you instantly lose the ability to work with Interface Builder (IB) in Xcode. Well, you can continue to use it, but you have to work with a large set of blank rectangles:

Storyboard before

However, this has all changed with Xcode 6, which introduces the concept of Live Views, which are views which appear in IB as they will in the running app. The exciting news is that they are super easy to use – and you can find out how today.

The sample project which accompanies this project contains the code from for the RWKnobControl I created for a tutorial on building custom controls over on The code has been translated into Swift, but other than that remains the same. You can get hold of this project in the iOS8 day-by-day repo on github at


The simplicity associated with this new functionality is truly beautiful. Given that you have a UIView subclass, then enabling the live-rendering in IB is as simple as annotating the class with the @IBDesignable annotation:

class KnobControl : UIControl {

Now, the view in the storyboard will automatically update to render the live view:

Default Storyboard

And that’s it! The objective-C equivalent is IB_DESIGNABLE.

If you need to provide any custom setup for the IB view then you can override the prepareForInterfaceBuilder() method, which will get called only when rendering inside interface builder.


It’s all very well and good being able to see the view in interface builder, but in the knob control example you’ve just seen it doesn’t look too good. The knob control has a whole set of properties that are used to configure its appearance. If you annotate these properties with @IBInspectable (IB_INSPECTABLE in objective-C) then IB will provide you with config fields in the attributes inspector to configure them:

var value:CGFloat {
get { return self._primitiveValue }
set { self.setValue(newValue, animated: false) }
var startAngle:CGFloat {
get { return self.knobRenderer.startAngle }
set { self.knobRenderer.startAngle = newValue }

Attributes Inspector

As you change these values then the view in the storyboard itself will update to reflect the new settings:

Updated Visualization

You can edit any types that you are used to using within IB:

var color: UIColor = UIColor.whiteColor()

var text: String = ""

var rect: CGRect = CGRect.zeroRect

var point: CGPoint = CGPoint.zeroPoint

var int: Int = 0

var float: CGFloat = 0.0

var image: UIImage = UIImage()

Inspectable Types

Debugging Views

So you’ve managed to get a view which appears inside IB, but maybe it’s not behaving in quite the way you want it. In days gone by you would have thrown in some breakpoints to your view code, and then run it up in the simulator to debug it. Obviously you can continue to use this methodology, but the new live views functionality also offers the ability to debug views right in Interface Builder.

Set up you break points in the usual way, and then select the view in the storyboard. Use the Editor > Debug Selected Views menu option to kick off the debug process.


The debug process works in exactly the same way as it does on a device or in the simulator – so once you’ve started debugging then changing a value in the attributes inspector will run exactly the same code you’d expect – and hence hit any appropriately placed breakpoints.


This new functionality is really great for anybody who uses custom views and quite likes using IB for laying out their view controllers. It’s so simple to integrate into your views that there isn’t really any excuse not to do it for views which are fairly simple. Obviously there are many custom views which are far more complex (and require table views and the suchlike), however the hooks in to the IB render process might still allow big gains over the iterative render process that you’re used to.

The code for this project is again available in the github repo at Go fork it and then gimme a shout to say hi – I’m @iwantmyrealname on Twitter.


Back to Blog