2026 • macOS • 16:52
Discover the key design considerations for updating your app for touch on macOS. We’ll explore the touch gestures now available on Mac, how system gestures work, how to size controls and touch targets while keeping your app great with a pointer and keyboard, and how to adapt hover interactions. Finally, we’ll dive into the expansion behaviors of native controls like steppers, dials, and sliders, and what that means for your app.
Speaker: Cas Lemmens
Downloads from Apple
Transcript
Hi, my name is Cas Lemmens. I’m a Human Interface Designer at Apple, and I’m working on macOS. This session covers how to design for touch on Mac. We’ll first talk about touch interactions you can add to your app. Then we’ll look at how system gestures on macOS now support touch. We’ll look at optimizations you can do to your UI to make it easy to interact with touch. And lastly, we’ll see how small controls can expand to show a larger layout optimized for touch. Let’s first look at how macOS and touch work together.
macOS on a device that supports touch doesn’t look any different than macOS on a device that doesn’t. The resolution, the size of windows, text and UI controls haven’t changed. In fact, if I put them side by side, they look identical. And that is by design. The Mac’s primary input methods remain keyboard and mouse, which is reflected in macOS’s UI size and density. Touch is a secondary input for macOS, and therefore has little impact on how macOS looks.
Of course, that doesn’t mean macOS is difficult to use with touch. What’s most exciting about bringing touch to macOS is the ability to directly manipulate the UI. I can simply reach my hand up to the display, and any control or UI element I touch will instantly react to my touch and finger movement.
For example, if I were to open Photos with my mouse, I have to locate my mouse on the display, move my mouse to the Photos app icon in the Dock, and click it. In contrast, with touch, I can tap the app icon directly. Thanks to touch’s direct manipulation, there’s no need for me to locate and move a pointing device. I can look, point, and touch.
Of course, tapping is just the start. All the familiar gestures I’ve used before on the trackpad of my Mac or on my iOS device can now be used on my Mac as well. Take a look at how easy it is to use Photos with touch using these gestures.
First, I can select a photo with a simple tap. Tapping to select is a very important interaction on macOS. It allows people to easily organize, modify, and move content between different apps. Hence, tapping to select follows the same gesture as clicking on trackpad. This makes it easier for people to switch between trackpad and touch without having to change how they select. Though on iOS, selection is often achieved by going through a selection mode, on macOS we recommend to allow modeless selection through click and tap.
Next, I can scroll the photos in my library by swiping or dragging my finger. Though scrolling requires two fingers on the trackpad, I use one finger on display. If I want to open a photo, I can double-tap the photo. Because we’ve reserved single tap for selecting the photo, a double tap is required to open the photo.
Single tap to select and double tap to open is a standard macOS uses for both trackpad and touch on display. If your app requires selecting and opening of items, use these same gestures to allow consistency between apps and inputs. Now from here, I want to edit this photo a bit, so I tap Edit and select Crop. Here, I can use two-finger gestures like pinch and rotate to crop the photo.
That photo looks really good to me. Let’s return to my photo library. The last interaction we’ll see is tap and hold. When I tap and hold a photo, notice a few things happen. First, the photo scales up under my finger. This is a visual cue to tell me the photo is now attached to my finger. Second, the photo’s context menu appears next to the photo, giving me an overview of what’s possible.
I can drag from here, at which point the context menu disappears. I can then drop the photo in an album. Of course, keyboard modifiers such as Shift and Option are supported when dragging with touch too. Alternatively, I can move my finger into the context menu and select an option. I’ll add it to a different album here.
This table gives an overview of the basic gestures your app can support and how they map between trackpad and touch. Select and Open have the same gestures with trackpad and touch. Scrolling happens with two fingers on trackpad, but one finger on display. Zoom and Rotate have the same gesture.
It’s applied to the object under either my cursor for trackpad or my finger for touch. And lastly, dragging and showing the context menu happens by tap and holding the display. While with trackpad, a context menu is shown when clicking with two fingers. Dragging happens by click and dragging. Of course, you can add your own custom gestures to your app as well.
For example, in Maps, I can drag two fingers up to show my map in 3D. I can do this interaction on trackpad too, but with a different gesture. Since dragging two fingers pans the map, Maps uses the Option modifier key while dragging on trackpad to show the map in 3D.
Next, macOS now allows multiple touch gestures at the same time. So far, the mouse only allowed us to interact with one control at any given time. But with touch, multiple fingers can interact with different controls simultaneously. For example, in Logic, I can change two individual sliders at the same time using two fingers.
Allowing multiple gestures at the same time makes your app feel alive and responsive when using touch, and it brings unique possibilities that are otherwise harder to do with the cursor. Now that we’ve talked about which gestures you can support in your app, let’s briefly look at where in the app these gestures are best used.
Because of the larger display and the ergonomics of a MacBook, I can touch the device in multiple ways. The edges of the display are easy to touch by grabbing the side of the display with my hand. This provides a stable base for anchoring my hand, allowing precise interactions with my thumb.
The left and right side of my app window are therefore best used to show rich controls and dense UI, such as inspectors and navigation sidebars. To touch the center of the display, my hand will extend midair without support to stabilize it. Hence, the center of the display is best used for coarse, imprecise and big gestures. For example, pan or swipe to move or pinch to zoom and rotate.
When adding your own custom gestures, your gestures should work with touch and trackpad and possibly Magic Mouse. Avoid adding gestures that only work with touch. You can use modifier keys where needed. This can help make your gesture work for all inputs. Avoid drastically changing the layout or UI of your app to support a new touch gesture.
And if your app runs on iOS, you can use the same gestures on macOS as in iOS. Though keep in mind the parity between the interaction on display and the interaction on trackpad. Easily switching between inputs on your Mac is sometimes more important than parity with your iOS app.
The action your gesture does should be duplicated elsewhere in the UI, for example in a menu. And keep in mind display regions and how easy it is to touch them. Allow precise gestures near the display edge and leave the display center available for coarse gestures. Next, let’s look at some of the system gestures.
Just as on trackpad, macOS has a range of multi-finger touch gestures to navigate the system. These gestures are controlled by macOS and are therefore not available to any app running. Let’s look at them. Swiping upwards with three fingers on the display invokes Mission Control, while swiping downwards with three fingers invokes App Exposé. Pinching inwards with a thumb and three fingers shows apps, while spreading outwards with a thumb and three fingers reveals the desktop.
Swiping left or right with three fingers navigates between desktop spaces. Swiping down from the top edge of the display presents the menu bar when it’s hidden, and swiping up from the bottom edge of the display presents the Dock when it’s hidden. Swiping over the Dynamic Island invites Siri.
Swiping left from the right edge of the display presents Notification Center, and lastly, swiping down from the top right edge of the display reveals Control Center. If you’d like to use any of these multi-finger gestures, the session “Bring touch to your Mac app” explains how to do this in AppKit, Mac Catalyst, and SwiftUI. Those are all the system gestures. Now let’s see how you can optimize your UI for touch.
Touch on macOS uses a touch target of 36 points. This creates the same physical size on display as iOS’s 44 points. All macOS’s framework controls have been updated to use this new touch target, but notice it’s invisible. The controls haven’t changed size and therefore don’t require a new layout.
The new touch target together with updated Liquid Glass makes these controls the best choice to use in your app. It will make your app more cohesive and harmonious with other apps. If you are using non-Apple framework controls, consider increasing the touch target area around your control instead of changing the control size.
When designing inspectors or other control-heavy areas, medium-sized controls continue to be the default control size. Window toolbars use extra-large-sized controls by default. Large and extra-large controls should not be used outside of the toolbar. They should only be used sparingly to emphasize key moments or in apps of which content consumption is the primary use case. For example, the play button in TV.
For views in your app that are very list-based or mainly revolve around settings, use FormStyle. Here as well, each row by default measures the 36-point height we mentioned before. FormStyle can also be used for simple inspectors or popovers. For very dense apps, smaller or mini-sized controls can still be used. They fully support touch regardless of their size. If your app is using custom small controls, ensure touch works, even though the tap target might be small. To make sure macOS feels alive and responsive to your touches, touch events should never be ignored.
Even in dense apps, touch can still be a benefit. For example, here in Xcode, I can use touch to scroll or navigate sidebars. Menus are now also touch optimized. They optimize layout based on the input you used to invoke them. When using the cursor, the menu appears as it has before.
But when using touch, the menu shows slightly larger rows to help make selection easier. And views in your app that are briefly presented, such as popovers or custom menus, can show slightly altered layouts depending on the input used to invoke them. Now, let’s talk about hover. Hover actions are a great way to show relevant actions in a moment. But of course, touch doesn’t support a hover state like mouse. So follow these guidelines to ensure these actions remain available. First, hover actions that are purely showing information, like tooltips, are not required to work with touch.
Next, actions that are easily feasible with touch also don’t need extra hover affordances to support it. For example, when hovering a horizontal carousel, macOS reveals buttons to scroll left and right. These help support mice without scroll wheels or gesture recognizers. However, since horizontal scroll is always possible via touch, these left and right buttons remain hidden during a touch interaction.
In general, when interacting with content, only the most important hover actions relevant to that content should reveal themselves. For example, in Safari, when using touch to interact with a website, only two hover actions appear. The close button of the current tab and the plus button in the address bar.
Notice there are no hover actions that reveal themselves on other tabs or in the sidebar. Hover actions hide themselves as well. This happens when I either interact with the hover action, I start using my mouse, or I touch anywhere outside of the area to which the hover applies.
Lastly, it’s recommended to have actions that appear on hover be duplicated elsewhere in your UI. Throughout macOS, you’ll frequently notice that an action that appears on hover also appears in the context menu of that same item or area. For example, when hovering a list in Reminders, a button appears on hover, allowing you to share that list. When interacting with touch, Reminders doesn’t show this button for any list. Instead, you can select a row or tap and hold a row to reveal the context menu from which you can share.
Last but not least, let’s look at how small controls can expand to better accommodate touch. macOS has always been known for its density, allowing us to show rich, effective controls in small areas. Good examples of these small controls are the stepper, dial, and slider. Even though macOS now supports touch, these controls preserve their style and size, avoiding to compromise macOS’s density. Yet to make these easier to touch, these controls now expand in place when interacting via touch. Let’s look at the stepper. These small up and down buttons on the right are definitely too small to accurately hit with touch.
By making the stepper an expanding control, we can now reveal larger up and down buttons when tapping anywhere on the control. Notice the value doesn’t change when tapping the control to expand. From here, I can tap these larger buttons to change the value with each tap, or I can tap and hold to continuously change the value.
Expanded controls collapse themselves when I’m not interacting with them. I can also tap outside to collapse them quicker. Next, let’s look at the dial. The dial allows for precise rotation using the cursor, but the control itself is too small to use with touch. Here as well, the dial has been made expandable. I can tap the dial, which reveals a larger dial optimized for touch. I can change the value here by dragging the knob.
Or I can tap and hold the dial to immediately change its value. Notice how the knob lands underneath my finger, making it easy and fast to change the value from here. Lastly, we’ll look at the slider. A slider with sufficient length is quite easy to touch. Because of the length, you’re able to change its value accurately. However, when the length of the slider becomes quite small, that accuracy is lost. Therefore, sliders have the option to expand when presented small.
Similar to the dial, I can tap the slider anywhere to expand it. And again, the value doesn’t change when I do so. From here, I have the full length to change the slider’s value. Or I can tap and hold the slider, which will expand the slider in place with the knob landing right underneath my finger.
To summarize, here are some next steps to prepare your app for touch on macOS. Avoid redesigning your app just to support touch. Your app on a Mac that supports touch should have no visual distinction from your app on a Mac that doesn’t. Use gestures to navigate your app and directly manipulate your content.
Use 36 points as a touch target on macOS, and use Apple frameworks to get touch-optimized layouts and expandable controls. Most apps will work great with touch right away. Keep keyboard and mouse as a primary input. Touch remains secondary, but a little bit of polish to support it can make a big difference.