iOS runtime for Rive
Further runtime documentation can be found in Rive's help center.
Rive is a real-time interactive design and animation tool. Use our collaborative editor to create motion graphics that respond to different states and user inputs. Then load your animations into apps, games, and websites with our lightweight open-source runtimes.
This is the iOS runtime for Rive, currently in beta. The api is subject to change as we continue to improve it. Please file issues and PRs for anything busted, missing, or just wrong.
You can clone this repository and include the RiveRuntime.xcodeproj to build a dynamic or static library.
When pulling down this repo, you'll need to make sure to also pull down the submodule which contains the C++ runtime that our iOS runtime is built upon. The easiest way to do this is to run this:
git clone --recurse-submodules [email protected]:rive-app/rive-ios
When updating, remember to also update the submodule with the same command.
git submodule update --init
To insatll our pod, simply add the following to cocoapods and run pod install
.
pod 'RiveRuntime'
Once you have installed the pod, you can run
import RiveRuntime
to have access to our higher level views or build on top of our bindings to control your own animation loop.
There is an example project next to the runtimes.
The examples show simple ways of adding animated views into your app, how to add buttons & slider controls, how to use state machines & how to navigate the contents of a rive file programatically.
To run the example, open the Rive.xcworkspace
in Xcode and run the RiveExample
project.
We have provided high level Swift controller and a UIkit view to easily add rive into your application. All of this is built ontop of an objective c layer that allows for fine grained granular animation control.
The simplest way of adding a riveView to a controller is probably to just set it as the controllers view when it is loaded.
class SimpleAnimationViewController: UIViewController {
let resourceName = "truck_v7"
override public func loadView() {
super.loadView()
guard let riveFile = RiveFile(byteArray: getResourceBytes(resourceName: resourceName)) else {
fatalError("Failed to load RiveFile")
}
let view = RiveView(riveFile:riveFile)
self.view = view
}
}
The RiveView will autoplay the first animation found in the riveFile, our code for loading the local resource as UInt8 data is here.
func getResourceBytes(resourceName: String, resourceExt: String=".riv") -> [UInt8] {
guard let url = Bundle.main.url(forResource: resourceName, withExtension: resourceExt) else {
fatalError("Failed to locate \(resourceName) in bundle.")
}
guard let data = try? Data(contentsOf: url) else {
fatalError("Failed to load \(url) from bundle.")
}
// Import the data into a RiveFile
return [UInt8](data)
}
The riveView can be further customized to select which animation to play, or how to fit the animation into the view space. A lot of configuration is possible on the RiveView, playback controls are added as functions on the view, and to change which file or artboard is being displayed, use .configure
.
The rive view can be further customized as part of specifying layout attributes.
fit can be specified to determine how the animation should be resized to fit its container. The available choices are .fitFill
, .fitContain
, .fitCover
, .fitFitWidth
, .fitFitHeight
, .fitNone
, .fitScaleDown
alignment informs how it should be aligned within the container. The available choices are alignmentTopLeft
, alignmentTopCenter
, alignmentTopRight
, alignmentCenterLeft
, alignmentCenter
, alignmentCenterRight
, alignmentBottomLeft
, alignmentBottomCenter
, alignmentBottomRight
.
This can be specified when instantiating the view
let view = RiveView(
riveFile:riveFile,
fit: .fitFill,
alignment: .alignmentBottomLeft
)
or anytime afterwards.
view.fit = .fitCover
view.alignment = .alignmentCenter
Animations can be controlled in many ways, by default loading a RiveView with a riveFile will autoplay the first animation on the first artboard. The artboard and animation can be specified by name here.
let riveView = RiveView(
riveFile: riveFile,
fit: .fitContain,
alignment: .alignmentCenter,
artboard: "Square",
animation: "rollaround",
autoplay: true
)
furthermore animations can be controlled later too:
To play an animation named rollaround.
riveView.play(animationName: "rollaround")
multiple animations can play at the same time, and additional animations can be added at any time
riveView.play(
animationNames: ["bouncing", "windshield_wipers"]
)
When playing animations, the Loop Mode and direction of the animations can also be set per animation.
riveView.play(
animationNames: ["bouncing", "windshield_wipers"],
loop: .loopOneShot,
direction: .directionBackwards
)
Similarly animations can be paused, or stopped, either all at the same time, or one by one.
riveView.stop()
riveView.stop(animationName:"bouncing")
riveView.stop(animationNames:["bouncing", "windshield_wipers"])
riveView.pause()
riveView.pause(animationName:"bouncing")
riveView.pause(animationNames:["bouncing", "windshield_wipers"])
Mixing goes further than just playing multiple animations at the same time, animations can use a mix factor between 0 and 1, to allow multiple animations effects to blend together. The high level views do not expose this currently. but you can wrap your own render loop around the core libraries. The advance function is where you can specify a mix factor.
The rive ios runtimes allow for delegates that can be provided to the RiveView. If provided these delegates will be fired whenever a matching event is triggered.
There are the following delegates LoopDelegate
, PlayDelegate
, PauseDelegate
, StopDelegate
, StateChangeDelegate
You can crete your own delegate like this, implementing as many protocols are are needed.
class MyDelegate: PlayDelegate, LoopDelegate {
func loop(_ animationName: String, type: Int) {
// do things when the animation loops playing.
}
func play(_ animationName: String, isStateMachine: Bool) {
// do things when the animation starts playing.
}
}
To use a delegate simply pass it to the view on instantiation
let delegate = MyDelegate()
let view = RiveView(
riveFile:riveFile,
loopDelegate: delegate,
playDelegate: delegate,
)
or attach it later
view.loopDelegate = delegate
-
cd into checked out directory
-
build the framework (check
build_frameworks.yml
)sh ./.github/scripts/buildFramework.sh -t iphoneos -c Release
sh ./.github/scripts/buildFramework.sh -t iphonesimulator -c Release
-
create a podfile in the build directory.
- look at
podspec.txt
& replace$RELEASE_VERSION
with something custom cp .github/workflows/podspec.txt archive/RiveRuntime.podspec
- look at
-
check its fine running
pod lib lint --allow-warnings
-
now you can include a reference to the archive in your podfile
pod 'RiveRuntime', :path => '/Users/maxwelltalbot/development/rive/rive-ios/archive/'
Rive allows the artist to set blend modes on shapes to determine how they are to be merged with the rest of the animation.
Each runtime is supporting the various blend modes natively, this means that there are some discrepancies in how blend modes end up being applied, we have a test file that is shipped inside the application that highlights the differences.
For ios, hue and saturation blend modes do not match the original.
Original | iOS |
---|---|