Paralayout is a set of simple, useful, and straightforward utilities that enable pixel-perfect layout in iOS. Your designers will love you.
To install Paralayout via CocoaPods, add the following to your
To install Paralayout via Swift Package Manager, add the following to your
dependencies: [ .package(name: "Paralayout", url: "https://github.com/square/Paralayout.git", from: "1.0.0"), ]
To install Paralayout via Carthage, add the following to your
Or, manually check out the submodule with
git submodule add [email protected]:Square/Paralayout.git, drag Paralayout.xcodeproj to your workspace, and add Paralayout as a build dependency.
Paralayout is a set of à la carte utilities, of which you can use as much or as little functionality as you like.
Hairline will size itself correctly on any screen resolution, and provides conveniences for positioning within its superview.
/// Put a line at the bottom of the view, inset 20 points on each side. let separator = Hairline.new(in: view, at: .maxYEdge, inset: 20)
Get the math right for multi-phase layout transitions and animations without tearing your hair out! Under the hood it’s simply a value between 0 and 1, but it makes computing that value, and deriving a new value from it, effortless.
// Determine how far we are into the transition of collapsing the header. let headerCollapseAmount = Interpolation(of: header.frame.height, from: maxHeaderHeight, to: minHeaderHeight) // The icon shrinks to half its usual size... let avatarSize = headerCollapseAmount.interpolate(from: 80, to: 40) avatar.frame.size = CGSize(width: avatarSize, height: avatarSize) // ...as it completely fades out. avatar.alpha = headerCollapseAmount.interpolate(from: 1, to: 0)
Create an aspect ratio from any size, rect, or width/height value, and use it to compute pixel-snapped frame rectangles.
videoPlayer.frame = AspectRatio.widescreen.rect(toFit: bounds, at: .topCenter, in: view)
These extensions provide numerous conveniences for computing rectangles and snapping coordinates to pixel dimensions. The
ScaleFactorProviding protocol encapsulates the latter, allowing a view to provide the context necessary to align its subviews to pixels. One benefit of this approach is that unit tests can cover both 2x and 3x scale factors regardless of the simulator used to run the test.
The extra space within a label above the "cap height" and below the "baseline" of its font is deterministic but non-obvious, especially at different scale factors. The simple
LabelCapInsets value type encapsulates that logic.
The core positioning function (and its numerous derived convenience functions) allows one view to be positioned relative to another view:
titleLabel.align(.leftCenter, with: icon, .rightCenter, horizontalOffset: 8) icon.align(withSuperview: .topCenter, inset: 20)
These methods extend
UIView.sizeToFit() to include constraints, which is particularly useful for labels and other views whose width and height are related to each other.
let labelSize = label.frameSize(thatFits: bounds.insetBy(dx: 20, dy: 20).size, constraints: [ .fixedWidth, .maxHeight ]) titleLabel.wrap(toFitWidth: boundsWidth, margins: 20)
Distribute a set of views vertically or horizontally using fixed and/or proportional spacing between them:
/// Vertically stack an icon, header, and button, with twice as much space at the bottom as the top. selectionScreen.applySubviewDistribution([ 1.flexible, headerIcon, 8.fixed, headerLabel, 1.flexible, button, 2.flexible]) /// Left-align a pair of labels, one above the other, with equal space above the title and below the subtext (despite the subtext being a smaller font). cell.applySubviewDistribution([ 1.flexible, titleLabel, 8.fixed, subtextLabel, 1.flexible ], alignment: .leading(inset: 10)) /// Equally size a pair of buttons with a hairline divider between them, and size/position them at the bottom of the alert. alert.spreadOutSubviews([ cancelButton, acceptButton ], axis: .horizontal, margin: alert.hairlineWidth, inRect: alert.bounds.slice(from: .maxYEdge, amount: buttonHeight))
Fixing layout issues is as simple as using the Xcode debugger. Remember that on a 2x device, view frame coordinates will be snapped to half-point boundaries (
x.5 only), while on 3x devices they are on 1/3-point boundaries (
x.667). The offsets used for view alignment do not need to be rounded (and generally shouldn’t be, to avoid accumulating rounding error), but view sizes should be.
We’re glad you’re interested in Paralayout, and we’d love to see where you take it. Please read our contributing guidelines prior to submitting a pull request.