UIActivityViewController
On iOS,
UIActivity provides a unified interface for users to
share and perform actions on strings, images, URLs,
and other items within an app.
You create a UIActivity
by passing in the items you want to share
and any custom activities you want to support
(we’ll show how to do that later on).
You then present that view controller as you would any other modal or popover.
let string = "Hello, world!"
let url = URL(string: "https://nshipster.com")!
let image = UIImage(named: "mustache.jpg")
let pdf = Bundle.main.url(forResource: "Q4 Projections",
withExtension: "pdf")
let activityViewController =
UIActivityViewController(activityItems: [string, url, image, pdf],
applicationActivities: nil)
present(activityViewController, animated: true) {
…
}
When you run this code the following is presented on the screen:
By default,
UIActivity shows all the activities available
for the items provided,
but you can exclude certain activity types
via the excluded property.
activityViewController.excludedActivityTypes = [.postToFacebook]
Activity types are divided up into “action” and “share” types:
- Action (
UIActivity) activity items take an action on selected content, such as copying text to the pasteboard or printing an image.Category Action - Share (
UIActivity) activity items share the selected content, such as composing a message containing a URL or posting an image to Twitter.Category Share
Each activity type supports certain kinds of items. For example, you can post a String, URL, and / or image to Twitter, but you can’t assign a string to be the photo for a contact.
The following tables show the available activity types for each category and their supported items:
UIActivityCategoryAction
| String | URL | Image | Files | ||
|---|---|---|---|---|---|
air |
✓ | ✓ | ✓ | ✓ | |
add |
✓ | ||||
assign |
✓ | ||||
copy |
✓ | ✓ | ✓ | ✓ | |
print |
✓ | ✓ | |||
save |
✓ | ✓ | |||
UIActivityCategoryShare
| String | URL | Image | Files | ||
|---|---|---|---|---|---|
mail |
✓ | ✓ | ✓ | ✓ | |
message |
✓ | ✓ | ✓ | ✓ | |
post |
✓ | ✓ | ✓ | ||
post |
✓ | ✓ | |||
post |
✓ | ✓ | ✓ | ||
post |
✓ | ✓ | ✓ | ||
post |
✓ | ✓ | |||
post |
✓ | ✓ | ✓ | ||
Creating a Custom UIActivity
In addition to the system-provided activities, you can create your own activities.
As an example, let’s create a custom activity that takes an image and applies a mustache to it via a web application.
![]() |
![]() |
| Before | After |
Defining a Custom Activity Type
First,
define a new activity type constant
in an extension to UIActivity.Activity,
initialized with a
reverse-DNS identifier.
extension UIActivity.ActivityType {
static let mustachify =
UIActivity.ActivityType("com.nshipster.mustachify")
}
Creating a UIActivity Subclass
Next,
create a subclass of UIActivity
and override the default implementations of the
activity type property
and activity, activity, and activity instance properties.
class MustachifyActivity: UIActivity {
override class var activityCategory: UIActivity.Category {
return .action
}
override var activityType: UIActivity.ActivityType? {
return .mustachify
}
override var activityTitle: String? {
return NSLocalizedString("Mustachify", comment: "activity title")
}
override var activityImage: UIImage? {
return UIImage(named: "mustachify-icon")
}
…
}
Determining Which Items are Actionable
Activities are responsible for determining
whether they can act on a given array of items
by overriding the can method.
Our custom activity can work if any of the items is an image, which we identify with some fancy pattern matching on a for-in loop:
override func canPerform(withActivityItems activityItems: [Any]) -> Bool {
for case is UIImage in activityItems {
return true
}
return false
}
Preparing for Action
Once an activity has determined that it can work with the specified items,
it uses the prepare(with method
to get ready to perform the activity.
In the case of our custom activity, we take the PNG representation of the first image in the array of items and store that in an instance variable:
var sourceImageData: Data?
override func prepare(withActivityItems activityItems: [Any]) {
for case let image as UIImage in activityItems {
self.sourceImageData = image.pngData()
return
}
}
Performing the Activity
The perform() method is usually the most important part of your activity.
Because processing can take some time,
this is an asynchronous method.
However, for lack of a completion handler,
you signal that work is done by calling the activity method.
But if an activity provides a view controller
(as ours will, to show the result),
UIKit presents that view controller instead of calling perform(),
so the work has to happen there.
Our custom activity delegates the mustachification process to a web app
using a data task sent from the shared URLSession.
The mustachify(completion:) method calls its completion handler
on the main queue with the resulting image,
or with nil if an error occurred in the request
or we can’t create an image from the provided data.
func mustachify(completion: @escaping (UIImage?) -> Void) {
let url = URL(string: "https://mustachify.app/")!
var request = URLRequest(url: url)
request.httpMethod = "POST"
request.httpBody = self.sourceImageData
URLSession.shared.dataTask(with: request) { (data, _, error) in
var image: UIImage?
if error == nil, let data = data {
image = UIImage(data: data)
}
DispatchQueue.main.async {
completion(image)
}
}.resume()
}
Showing the Results
The final step is to provide a view controller to be presented with the result of our activity.
We override the activity property
to return a navigation controller
containing a simple view controller that displays the image:
override var activityViewController: UIViewController? {
let viewController = MustachifyViewController(activity: self)
return UINavigationController(rootViewController: viewController)
}
When its view loads,
the view controller asks the activity to mustachify the image
and shows the result in an image view.
The “Done” button stays disabled until the image arrives.
When the user taps it,
it calls activity with true
to indicate that the activity finished successfully,
and UIKit dismisses it.
If the image couldn’t be mustachified,
or if the user taps “Cancel”,
it calls activity with false to indicate failure.
class MustachifyViewController: UIViewController {
let activity: MustachifyActivity
let imageView = UIImageView()
init(activity: MustachifyActivity) {
self.activity = activity
super.init(nibName: nil, bundle: nil)
}
required init?(coder aDecoder: NSCoder) {
fatalError("init(coder:) has not been implemented")
}
override func viewDidLoad() {
super.viewDidLoad()
self.view.backgroundColor = .white
self.imageView.frame = self.view.bounds
self.imageView.autoresizingMask = [.flexibleWidth, .flexibleHeight]
self.imageView.contentMode = .scaleAspectFit
self.view.addSubview(self.imageView)
self.navigationItem.rightBarButtonItem =
UIBarButtonItem(barButtonSystemItem: .done,
target: self,
action: #selector(done))
self.navigationItem.rightBarButtonItem?.isEnabled = false
self.navigationItem.leftBarButtonItem =
UIBarButtonItem(barButtonSystemItem: .cancel,
target: self,
action: #selector(cancel))
self.activity.mustachify { [weak self] image in
guard let self = self else { return }
if let image = image {
self.imageView.image = image
self.navigationItem.rightBarButtonItem?.isEnabled = true
} else {
self.activity.activityDidFinish(false)
}
}
}
@objc func done() {
self.activity.activityDidFinish(true)
}
@objc func cancel() {
self.activity.activityDidFinish(false)
}
}
Providing a Custom Activity to Users
We can use our brand new mustache activity
by passing it to the application parameter
in the UIActivity initializer:
let activityViewController =
UIActivityViewController(activityItems: [image],
applicationActivities: [MustachifyActivity()])
present(activityViewController, animated: true) {
…
}
There is a strong argument to be made that
the long-term viability of iOS as a platform
depends on sharing mechanisms like UIActivity.
As the saying goes, “Information wants to be free.” Anything that stands in the way of federation is doomed to fail.

