7 min read
Apple's First Touchscreen Mac: Is Your Web App's Onboarding Ready?
The new touchscreen MacBook Pro brings touch to a platform built for the mouse. Here's how to make your tooltips, hints and product tours work for both.
For years Apple said a touchscreen didn't belong on a Mac. On October 28, 2026 it changed course. The new 14- and 16-inch MacBook Pro with a PROLED XDR display is the first Mac you can touch, and it went on sale on November 6.
Most coverage has focused on the hardware. If you build web apps, the more important point is what this means for your interface. Windows has had touchscreen laptops for over a decade, but for many SaaS teams the Mac was the "desktop" they designed and tested on. Now a growing share of your desktop users can tap your UI directly.
Onboarding is one of the first places this shows up. Tooltips, hints and product tours sit on top of your interface and are often designed with a mouse pointer in mind. Here's what changes and how to prepare.
How touch works on the new Mac
A few facts from Apple's announcement and early hands-on reviews:
- Touch is optional. The keyboard and trackpad are still the main way to use a Mac. As CNBC's hands-on put it, you don't have to use touch at all.
- Taps become clicks. According to Apple, "macOS automatically translates touches into clicks," so anything you can click can also be tapped.
- Familiar gestures. You can swipe to scroll a webpage, pinch to zoom, drag and drop, and double-tap a window to fill the screen.
- Controls adapt. CNBC noted that the red close button in a window's corner grows when you touch it, making it easier to hit.
The first point matters most for web developers. These are hybrid devices: the same user might use the trackpad for one action and tap the screen for the next. You can't design for a "touch user" or a "mouse user". You have to design for someone who switches between them at any moment.
Where onboarding breaks on touch
Hover-only tooltips
The most common problem is a tooltip or hint that only appears on hover. A finger has no hover state. When a user taps an element, it either activates straight away or, depending on the browser, briefly shows a hover state they barely see. Either way, the explanation you meant to show is lost.
This affects more than onboarding. Help icons, truncated labels that reveal full text on hover, and menus that open on mouseover all fail the same way. A good rule: anything that appears on hover must also appear on tap or focus.
Small targets
A mouse pointer is precise to a single pixel. A fingertip is not. The "Next" and "Skip" buttons in a product tour, the close "×" on a tooltip and the small pulsing dot of a hint are all things users need to hit accurately.
Apple's Human Interface Guidelines have long recommended 44×44-point touch targets on iOS. The WCAG 2.2 guidelines require at least 24×24 CSS pixels (or enough spacing around smaller targets) and recommend 44×44 for the best experience. Tour buttons that look fine with a mouse can be frustrating to tap.
Accidental dismissals
Most product tours close when you click the dark overlay around the highlighted element. With a mouse that's rarely an accident. With touch it happens all the time. A user reaches for the screen, lands slightly outside the tooltip, and the tour is gone before they finish reading.
Gestures that move the page
On touch, users scroll and zoom with their fingers. If a tooltip is positioned for one scroll position and the user swipes, it can end up pointing at the wrong thing or off screen. WebKit is still fixing bugs here: a Safari Technology Preview release from November fixed viewport units changing size during two-finger zoom on macOS.
How to make your onboarding touch-ready
1. Detect touch capability, not "touch devices"
Don't sniff user agents or assume that "Mac" means "no touch". Use CSS media queries that describe input capabilities:
/* At least one input can't hover precisely, e.g. a finger */
@media (any-pointer: coarse) {
.introjs-button {
min-height: 44px;
min-width: 44px;
}
}
/* Treat hover as a visual extra, never as the only way to reveal content */
@media (hover: hover) {
.help-icon:hover {
opacity: 0.8;
}
}There's an important difference between the two kinds of query. pointer and hover describe the primary input, which on a touchscreen Mac is probably still the trackpad. any-pointer and any-hover match if any connected input has that capability, so they're the safer choice for hybrid devices.
That's also why a hover media query can't fix hover-only content. On a hybrid device, the trackpad reports that hover is supported even while the user is tapping the screen. Keep hover for visual extras and make the content itself open on click or tap.
Apple hasn't documented exactly what Safari reports for these queries on the new MacBook Pro. Test on real hardware or with a touch simulator rather than assuming.
2. Handle the input that was actually used
When behavior should depend on how the user interacted, check it per event with Pointer Events instead of deciding once for the whole session:
helpIcon.addEventListener("pointerup", (event) => {
if (event.pointerType === "touch") {
// A tap: show the help text and keep it open until dismissed
showHelp({ sticky: true });
}
});This works for a user who switches between trackpad and screen several times a minute.
3. Make tooltips and hints open on click
Use tooltips that open on click or tap. Because taps become clicks, one implementation covers both inputs. Intro.js tours and hints already work this way: they listen for clicks, not hovers. Hints are a good fit for touch because the user taps the hint to open its explanation and taps "Got it" to dismiss it.
introJs.hint()
.setOptions({
hints: [
{
element: "#export",
hint: "Export your report as PDF or CSV.",
hintPosition: "middle-right",
},
],
})
.addHints();4. Make tours harder to close by accident
For product tours, turn off closing on overlay tap when touch is available. Keep a clear "Skip" button so users can still leave on purpose:
const hasTouch = window.matchMedia("(any-pointer: coarse)").matches;
introJs.tour()
.setOptions({
steps,
exitOnOverlayClick: !hasTouch,
showProgress: true,
})
.start();Showing progress helps on any device. People are less likely to give up on a tour when they can see it's only four steps long.
5. Write copy for both inputs
"Click the gear icon to open settings" sounds wrong when the user just tapped. Use input-neutral verbs like "select", "open" or "choose", or no verb at all: "Settings live here." The same goes for keyboard-specific instructions such as "hover over a row to see actions".
6. Test on a touch device
You don't need the new MacBook Pro to test touch. A Windows touchscreen laptop, an iPad, or the device emulation in your browser's developer tools (with touch simulation turned on) will catch most problems. Go through your tour using only your finger:
- Can you reach and tap every button without missing?
- Does any step depend on hover?
- Does the tour survive a swipe or a pinch-to-zoom?
- Did you accidentally close it?
The bigger lesson
The touchscreen Mac doesn't create a new problem. Windows laptops and iPads have been hybrid devices for years. What it removes is the assumption that the main desktop platform for designers and developers is mouse-only.
Onboarding is often a user's first interaction with your product, so it's the worst place to get input handling wrong. A tour that closes by accident or a hint that can't be opened makes your product look broken on day one.
The fix is mostly basic good practice: content that doesn't rely on hover, targets big enough for a finger, and guidance that responds to however the user chooses to interact. Get those right and your onboarding will work on every device, including whatever Apple ships next.
For more on building tours in a modern frontend stack, see our guide on how to add a product tour to a React app. For more onboarding lessons, read our onboarding teardown of Warp.
Details about the touchscreen MacBook Pro are based on Apple's announcement and press coverage as of November 2026. Intro.js is not affiliated with Apple.