Jitouch on OS X 10.10 Yosemite

Jitouch has apparently been worked on since October 18th, 2014 for Yosemite compatibility, but as of writing this post it’s still broken.

This sucks, because it’s one of the core apps that makes OS X usable for me. I don’t want to sound melodramatic, but using Yosemite has been a daily struggle without all of my Jitouch muscle-memory UX goodness.

Here’s how to halfway fix it:

First, open System Preferences, right click Jitouch, and select “Remove Jitouch Preference Pane”:

Remove Jitouch from preferences

Next, download the Yosemite beta. Instead of double clicking to install it, you need to manually move it to /System/Library/PreferencePanes. This folder is hidden by default, but you can open it by selecting Go -> Go to Folder in Finder:

Go -> Go to Folder in Finder

then type /System/Library/PreferencePanes and hit Go:


Now just drag and drop the Jitouch.prefPane you downloaded before into this window:

drag and drop Jitouch.prefPane to /System/Library/PreferencePanes

Jitouch will now show up in System Preferences -> Security and Privacy, which will re-enable a lot of the broken gestures (like drawing characters).

Jitouch now shows up in the Security and Privacy page of System Preferences

I’m still having some quirky trouble, though. Here’s a list of the bugs I’ve noticed:

  • next/previous tab is triggered twice, which is incredibly annoying. Update: a day after installing the new Jitouch beta with the abov steps, next/previous tab is only getting triggered once!
  • When my laptop has been asleep for a while (long enough to trigger hibernation or safe sleep mode), Jitouch stops working. It seems to work again if I manually put my laptop to sleep and immediately wake it up again.
  • The One-Fix One-Slide-Up action is gone, which is what I used to use to resize windows.
  • Move Window and Resize Window have been merged into a single Move/Resize action. To trigger Resize from Move/Resize, use One-Hold Right-Tap.

If you notice anything else, let me know @cgenco on twitter and I’ll add to this list. The developer has been frustratingly unresponsive @macjitouch.