All posts in the ‘Company News’ category

Subscribe to the RSS feed for the 'Company News' category

Moom 3.2.8 released

Tuesday, May 16th, 2017

Late yesterday, we released Moom 3.2.8, which has only one change from Moom 3.2.7, released the day before. The update is available directly from us (via in-app updater, or by downloading it from our site), and it should be available in the Mac App Store app shortly, if not already.

The one change was to the grid, which switched from rectangular (with the circles of 3.2.7) to the new hexagonal layout, as seen at right.

Why did we change the design? Late last week, we learned there’s a US patent that covers resizing windows using a rectangular grid in a miniature preview image. We learned this when the patent’s owner told us they believed Moom’s grid was infringing on their patent. For now, we have redesigned the grid in such a way that no infringement claim can be made, and we’re working on further improvements.

Note: Comments are closed on this post, as we wish to inform you as to what happened, not to start a debate on software patents in general, or this patent in particular.

How Apple’s security system broke some Mac apps

Thursday, February 23rd, 2017

Feb 28 2017 update

Apple has responded quickly to address this issue. Their Developer ID page, which I believe is brand new, specifically addresses provisioning profiles and their relationship to the Developer ID certificate. Here’s what they say (emphasis added):

For apps that utilize advanced capabilities with a Developer ID provisioning profile
Gatekeeper will evaluate the validity of your Developer ID certificate when your application is installed and will evaluate the validity of your Developer ID provisioning profile at every app launch. As long as your Developer ID certificate was valid when you compiled your app, then users can download and run your app, even after the expiration date of the certificate. However, if your Developer ID provisioning profile expires, the app will no longer launch.

That section addresses the crashes seen in PDFpenPro and 1Password: It is now documented that an expired provisioning profile will prevent your app from launching. That’s not necessarily good news…but the good news is that this will, going forward, be a much rarer event:

To simplify the management of your Developer ID apps and to ensure an uninterrupted experience for your users, Developer ID provisioning profiles generated after February 22, 2017 are valid for 18 years from the creation date, regardless of the expiration date of your Developer ID certificate.

So any app that uses a provisioning profile created after February 22nd of this year will not crash due to an expired provisioning profile—even if the developer does nothing and lets their Developer ID certificate expire—until February 22, 2035. That’s effectively forever in the world of a macOS app (it’s longer than macOS/OS X itself has existed, in fact.)

Thanks, Apple, for the quick response! We’re leaving the original article posted as a non-techie overview of the Developer ID system; keep reading if that’s of interest to you.

Recently, some well-known Mac apps, including 1Password, PDFpenPro, and Soulver, had a big problem: They all failed to launch. Nothing had changed with these apps (i.e. no updates had been released), and yet they simply stopped working.

So what happened? All three of these apps (and probably some others we haven’t heard from yet) contained an expired code signing certificate. That expired certificate prevented the apps from launching, though no developer would have expected that, based on Apple’s own documentation. And an expired code signing certificate can’t just be renewed to extend its expiration date (like you would a driver’s license); it needs to be replaced with a new non-expired certificate, which requires distributing an update to the app.

Follow me now, if you wish, for a somewhat deep dive into the world of code signing, as I attempt to explain—from a consumer’s perspective yet with a developer’s hat on—what is code signing, why these apps broke, why the breakage wasn’t expected, and other related questions and answers.

Update: AgileBits has a very detailed blog post that covers this issue in even more depth—well worth the reading time.

What is code signing?

Code signing is a digital signature for apps, proving that an app was created by the developer who signed the app, and it allows the operating system to check whether a given app’s code has changed since it was created. Here’s how Apple summarizes it for developers:

Code signing is a macOS security technology that you use to certify that an app was created by you. Once an app is signed, the system can detect any change to the app—whether the change is introduced accidentally or by malicious code.

You participate in code signing as a developer when you obtain a signing identity and apply your signature to apps that you ship. A certificate authority (often Apple) vouches for your signing identity.

Signing apps is a reasonable way to add security to a system without overburdening the end user with authorization dialogs—like the infamous User Account Control (UAC) in Windows Vista, which popped up “Allow this?” dialogs seemingly every 10 seconds.

How does macOS work with signed apps?

On macOS, code signing’s visible front-end is Gatekeeper, as seen in the Security & Privacy System Preferences panel:

macOS ships with Gatekeeper set to only allow apps from the Mac App Store or from identified developers, so it’s a big advantage for a developer to register with Apple and sign their apps: Any unsigned apps require additional authorization work by the end user before they can be run. Would you want to do that extra work when presented with a scary dialog like this one?

This is why almost all mainstream apps are signed, as well as small little one-off apps from single coders: Nobody wants their app to generate the above dialog. (The app in my screenshot, Disk Inventory X, was last updated in 2005—long before signed apps came to be a thing. There’s nothing malicious about it; it was just a good example for the screenshot.)

How do signed apps help keep me safe?

Here’s how Apple explains the safety aspect for users on the Gatekeeper page:

For apps that are downloaded from places other than the Mac App Store, developers can get a unique Developer ID from Apple and use it to digitally sign their apps. The Developer ID allows Gatekeeper to block apps created by malware developers and verify that apps haven’t been tampered with since they were signed. If an app was developed by an unknown developer—one with no Developer ID—or tampered with, Gatekeeper can block the app from being installed.

There are two key security advantages that come from signed apps. The first, as noted above, is that the system can confirm that the app you’re trying to run hasn’t had its code changed since it was signed. So if a piece of malware did manage to modify the binary for a particular signed app, that app wouldn’t launch because its signature would be found to be invalid.

The second big advantage is that Apple can revoke a certificate if a developer were to do something truly malicious. Once revoked, any apps that were signed with that certificate will stop working. Here’s how Apple explains it to developers

Code signing your app allows the operating system to identify who signed your app and to verify that your app hasn’t been modified since you signed it. Your app’s executable code is protected by its signature because the signature becomes invalid if any of the executable code in the app bundle changes. Note that resources such as images and nib files aren’t signed; therefore, a change to these files doesn’t invalidate the signature.

Code signing is a good thing from the user’s perspective; from a developer’s perspective, it adds to the complexity of the build-and-release process, but the benefits outweigh the added complexity.

One element of this complexity is that the certificates do expire, and an expired certificate must be replaced with a new non-expired certificate, which requires distributing an update to your app. But until recently, this hasn’t been a time-critical item, and an expired certificate wasn’t a big deal.

Wait, an expired certificate isn’t a big deal?

Historically, the answer to that question was “No, it’s not.” In fact, Apple still explicitly tells developers that an expired code signing certificate won’t affect existing apps (added emphasis mine):

If your certificate expires, users can still download, install, and run versions of your Mac applications that were signed with this certificate. However, you will need a new certificate to sign updates and new applications. If your certificate has been revoked, users will no longer be able to install applications that have been signed with this certificate.

This is why developers haven’t viewed an expired certificate as a critical issue: It shouldn’t have any effect on already-released apps. To reiterate the point, Apple states so again on another page, even calling it out with a highlight:

The message can’t be any clearer: There’s nothing inherently bad about an expired signing certificate, at least relative to already-released apps.

In fact, you probably have a number of apps on your Mac—or your iPhone—with expired certificates. For example, an older app from a developer who has since gone out of business. Apps from such developers will run just fine, even though they contain an expired certificate. This is a good thing for users, because you don’t need a developer to still be in business to use their app.

Once the certificate data is embedded in the app, the fact that it’s expired doesn’t remove the safety provided by the signature: If a piece of malware modifies an app with an expired signing certificate, the code signing check will still fail (and the app won’t launch), so the user is protected.

Apple can also revoke an expired certificate (in the case of malware) and the app will fail to launch, so the user is protected.

Neither of these safety valves require the certificate to be current, only that the app contains a valid signature, created at the time it was built.

From a developer’s perspective, it’s also good that expired certificates don’t cause apps to fail to run. For example, we distribute old versions of our apps, for users on older versions of macOS/OS X. At some point, the certificates in those apps will expire. If we had to create new builds for all 50+ versions of the apps we distribute, that would be a nightmare. And if we didn’t do that, we’d have a lot of upset users of older versions, complaining that their apps no longer run.

Still, shouldn’t developers replace their expired certificates?

Yes, they should. But as noted above, Apple explicitly tells developers—in at least two places—that they only need these certificates to build new apps or update existing apps. So if you have a certificate that’s set to expire, but you don’t have an urgent need to update an app or create a new app, it’s supposed to be a non-event.

It’s a bit of speculation, but it’s possible (probable, even) that the affected apps’ developers actually had new, non-expired certificates in hand. But those certificates would only be used to create an update to the app, and they’d been told that an expired certificate in an existing app wasn’t anything to worry about.

Another important fact is that simply getting a new non-expired certificate doesn’t solve the problem: The certificate data is built into the app itself, not stored externally somewhere where a newer version can be retrieved. To get their new certificates into their apps, these developers would have had to push an update to users—and unless they had a minor update ready to go, the sole purpose of the update would be to replace the expired certificate.

Most developers dislike releasing numerous updates, especially updates with only one change (assuming it’s not a critical bug fix), and again, Apple tells developers that an expired certificate isn’t a big deal. A normal business approach to this situation would be…

  1. Set up the new certificates, so they’re ready for the next update.
  2. When the time comes for the next update, the build will contain the new non-expired certificate data.

But because the expired certificates broke these apps, the developers had to release an update just to refresh the certificate data. That’s not good for developers or users.

Why exactly did these apps break?

Given Apple’s position that an expired certificate should have no impact on an app’s ability to run, there’s no doubt that Smile and AgileBits and others were very surprised by reports of their apps failing to launch. So really, why did these apps fail?

The common thread in all three of these apps is that they included support for using iCloud for sync or storage. Access to iCloud was originally restricted to App Store apps, but that changed with the release of Yosemite: Now any registered developer can include iCloud support in their apps.

To do so, a developer needs to flip a switch in Xcode to add iCloud support:

Flipping the toggle from Off to On creates something called a provisioning profile. This profile says “It’s OK for this app to use iCloud, even though it’s not in the App Store.” This was best explained by Smile’s Greg Scown to Adam Engst in this tidBITS article:

What’s new with PDFpen 8 is that, in addition to being code signed, it has a provisioning profile, which is essentially a permission slip from Apple that’s checked against an online database in order to allow the app to perform certain actions, called entitlements. For PDFpen, the entitlement that’s being granted is the capability to access iCloud despite being sold directly, rather than through the Mac App Store, a feature that wasn’t possible until about a year ago.

The only apps that crashed due to expired certificates (so far, at any rate) were those that used this iCloud provisioning profile outside of the Mac App Store. What happened with PDFpenPro and the other apps is that the expired signing certificate rendered the iCloud provisioning profile invalid. The invalid provisioning profile, in turn, prevented the app from ever launching.

According to everything Apple has told developers, this should not happen. To the best of my knowledge, developers were never given any warnings about expired certificates and iCloud provisioning profiles. If they had been told, it’s a fair certainty that they all would have updated their apps with new certificates before the expiration date. Of course, this wouldn’t help any user who didn’t update their copy of the app before the certificate’s expiration date.

What made the situation even worse is that the provisioning profiles are checked by the system itself, before the app even runs. As a result, the app can’t tell the user something is wrong, because the app didn’t actually launch. Again, from tidBITS:

An app called taskgated-helper determines this even before PDFpen’s code runs, so there’s no way for Smile to detect the error condition and present an error to the user.

So the app can’t tell the user what’s going on, and even worse, the OS doesn’t tell the user what’s going on: The app just seemingly dies in an instant. That’s bad for the user, and bad for the developer, because they’re blamed for something they didn’t even know was occurring (because their app never loads, and no crash reports are generated). If the OS is going to kill the app, the OS should tell the user why it did so, so the user has some understanding about the problem.

Will this happen again in the future?

First, from our perspective: As we currently don’t use iCloud (or other) provisioning profiles, our behavior won’t change: An expired certificate is not reason alone to update an app. And as discussed above, doing so for all old apps with (eventually to be) expired certificates would be a nightmare.

For developers who do use iCloud (or other) provisioning profiles, it appears that unless Apple fixes something, they will have to pay very close attention to their certificate expiration dates, and make sure they push out app updates (and hope all their customers update) before the certificates expire.

How can I find out more about code signing in apps I use?

As a user, if you’re really interested in this stuff for some reason, there’s an app called RB App Checker Lite that can take a look inside any application and see its certificates (and a bunch of other data).

The output is definitely way up on the geek scale; here’s what it shows for Flying Meat’s Acorn image editor:

Here I’ve clicked the arrow next to “The signature contains 3 certificates” in order to view the Flying Meat code signing certificate. As you can see, it appears their certificate was recently replaced, given the nearly-five-years-from-now expiration date.

Code signing is a complex topic; hopefully this article made the subject a bit clearer, and you gained an understanding of how it works, and for how seemingly-irrelevant expired certificates brought down a number of Mac apps.

The new Many Tricks’ end user license agreement

Thursday, April 28th, 2016

Ever since Peter and I relaunched Many Tricks in 2010, we’ve never had an official software license agreement. The closest thing we’ve had is this blog post, which explains limits on the use of our apps across multiple Macs (tl;dr: Use them on as many Macs as you personally use). However, we’ve never had an actual end user license agreement (EULA) that spells out the legal license you agree to when you purchase one of our apps.

Well, we have one now—it’s also permanently linked in the sidebar here, and will be accessible from within our apps. And a really big thanks to Rich Siegel at Bare Bones Software, who generously agreed to let us use his document as a starting point. I found the Bare Bones EULA to be well written, brief, and easily understood; hopefully our version, which has only minor changes, is still all of those things.

After six years, why did we suddenly need an EULA? The truth is we probably should have had one from day one, but never really felt the need. Recently, however, we’ve received inquiries from government agencies and larger companies interested in buying our apps … and many of these customers aren’t allowed to purchase our apps unless we have an actual legal license agreement. So now we do.

Note that this doesn’t change anything relative to the usage of our apps; we still allow you to use one license to install our apps on as many Macs as you personally use. We just needed to have a formal legal software license for larger customers and government agencies.

All direct apps updated to improve update security

Sunday, January 31st, 2016

Yes, that’s right, we’ve updated the updater in our direct apps. Our direct apps rely on Sparkle to inform you when there are new versions available. Over the weekend, we were made aware of a potential vulnerability in how we implemented Sparkle. Basically, if your network is already compromised by what’s called a Man in the Middle attack, then it’s possible an attacker could use the Sparkle update mechanism in our apps to remotely execute code on your Mac. That’s bad.

Although this is a relatively small exposure (as you must already be on a compromised network), we felt it was important to act on it right away, so we’ve updated all of our apps to use Sparkle over secure HTTP (HTTPS). Please update any directly-purchased Many Tricks apps immediately.

Important: There’s a bit of a Catch-22 here … in order to get you this update, it must come over insecure HTTP, because that’s how Sparkle in the app you’re using is configured. If you are concerned that you might be on a compromised network, please do not update using the in-app updater. Instead, just download the relevant app(s) directly from our site, which uses HTTPS.

If you have any questions on this update, please leave a comment or email us directly, and we’ll do our best to address your questions.

Note: Although our App Store apps don’t use Sparkle, we know they’re out of date with some of the other minor bug fixes that came with these releases. We’ll be submitting updates to the App Store next week to get App Store users current.

The Many Tricks holiday sale event and charity drive

Monday, December 14th, 2015

People ask us all the time, “When are your apps going on sale?” And we always reply “We don’t know,” because, generally, we don’t know. But we know now: Our apps—when you purchase directly from us—are on sale for the remainder of 2015, and there are two ways to take advantage of the sale.

Option One: Own Them All

First off, you can own them all for just $50—that’s $62 off the normal price of $112 for all 10. All ten apps, fifty bucks total. These are fully licensed versions, not some special one-off, so they’re all eligible for upgrade pricing when major new releases come out.

On the charity drive front, we will donate $10 for each bundle sold to the United Nation’s refugee fund, to help with the ongoing global refugee crisis. And to get things started, we’ve already donated $500 to the fund.

Option Two: Save Some Coin

If you don’t really want all our apps (we don’t understand such thinking, of course!), you’ll want to use option two: Every purchase is 30% off for the remainder of the year.

We will donate 10% of our net proceeds from any individual sales to that same UN refugee fund.

About the Mac App Store

You may have noticed that this sale is only available to customers who purchase directly from us; our App Store app pricing is unchanged, and we can’t create a bundle of apps there anyway.

So why aren’t the individual MAS versions on sale? Quite honestly, we feel Apple has ignored the MAS for too long, and as a result, the customer experience is not what it should be. Add in the recent snafu with certificates, and we would like to reward those who choose to purchase direct. That’s why this sale is for direct customers only.

So there you have it, the Many Tricks year-end sale event and charity drive.

All direct apps updated ahead of El Capitan’s release

Monday, September 28th, 2015

There are a couple of changes in the soon-to-be-released El Capitan that required us to update our direct-sales app update mechanism—an incredible open-source framework known as Sparkle. (App Store versions don’t have this update mechanism, because the App Store app handles app updates.)

Because of how we implemented Sparkle, we found that the updater wasn’t working properly in El Capitan. So we needed to fix this prior to El Capitan’s release. As a result, today we have updated every single direct app we sell (and even one we give away):

Butler, Desktop Curtain, Key Codes, Keymo, Leech, Moom, Name Mangler, Time Sink, Usher, and Witch

We have pushed all these updates live, so you should see them automatically (if you have our apps set to auto-update), or you can look in the Preferences > Updates section of a given app and manually check for updates. You can also download the complete new version from our site, if you prefer (just delete the old one and replace with the new; you won’t lose your settings.)

Our site has learned to speak securely

Monday, September 28th, 2015

Every year, we get a few inquiries about why our web site doesn’t use https (i.e. TLS/SSL) to encrypt communications between the user and our site. Our stock answer has been that SSL is slow, expensive, and complicated for a two-person company to manage—and that was true for many years.

However, when I received the latest inquiry about encryption on the site, I thought it was time to revisit the subject. What I found is that SSL is no longer slow or expensive—and the complexity level has dropped dramatically. So we did a bit of work to update our pages, installed our shiny new security certificate, and as of now, you can securely browse Many Tricks by using this URL:

Note that we have not made this the default—but if you load the https site, you won’t be able to load the http version (thanks to something called HTTP Strict Transport Security).

When you’re browsing our https site, you should see a small lock icon next to the site’s name, as seen below in Safari, Chrome, and Firefox:

We don’t collect any financial information here (all purchase details go through our processors, which have always used TLS/SSL encryption). But many people like the security of knowing that their interactions with a given site are encrypted. And now, they can be when you visit

SHA-2 Hashes

The other thing we’ve done is create a page of SHA-2 hashes for all our apps. That page contains a list of SHA-2 hash values, and explains how to use these values to insure that what you download from us is the same as what we uploaded to the server. (Note that this is mostly useful for any potential download interceptions; if someone hacks our server such that they have full access, they could simply modify the SHA-2 values so that everything still looked right to a user.)

Please let us know if you have any troubles with either the https site (or our SHA-2 hash values)—we think we’ve tested everything, but it’s quite possible we’ve missed a page somewhere.

Welcome, Resolutionator

Tuesday, August 4th, 2015

Meet Resolutionator, the newest entry in Many Tricks’ stable of apps. Resolutionator makes it brain-dead-simple to switch the resolution on your display(s), and was developed with retina displays in mind (though it’s perfectly functional on non-retina displays, too).

Like many of our other apps, Resolutionator came about due to an internal need—I use a 13″ retina MacBook Pro, and as crisp and gorgeous as that 1280×800 ‘retinaized’ display is, that’s just not a lot of room when working with lots of windows. As a result, I found myself constantly switching resolutions—I’d use a higher resolution when working on complicated projects, then switch back to the default retina resolution when browsing the web or reading email.

In prior versions of the Mac OS, switching resolutions wasn’t a big deal—an optional menu bar icon provided quick access to any available resolution. But some years back, this feature vanished, never (at least so far) to be seen again. In its place is a convoluted process that requires launching System Preferences and clicking buttons. If you change resolutions once a week, it’s not too bad…but if you change multiple times a day, it gets old, and fast.

Switch via pop-up or menu barEnter Resolutionator, which recreates the old menu bar prompt to let you quickly change the resolution on any and all attached displays, as seen at right.

But Resolutionator goes well beyond the old stock resolution switcher.

You can assign a keyboard shortcut, and then switch resolutions via a pop-up menu. And whether you use a keyboard shortcut or the menu bar icon, Resolutionator lets you switch the resolution on all attached displays from the same location.

Want to conserve menu bar space? After assigning that keyboard shortcut, switch Resolutionator to faceless mode, and it runs completely invisibly, activated only when you press the assigned shortcut. (It can also run as a normal application, complete with Dock icon, if you prefer.)

Those features are useful, though not all that exciting. The exciting feature in Resolutionator is its secret superpower…

Resolutionator’s secret (OK, it’s not really secret) superpower is that it can offer you resolutions—including some that offer more pixels than your display contains—that OS X won’t let you use.

On my 13″ Retina MacBook Pro, for instance, OS X’s Displays panel lists four possible resolutions, ranging from 1024×640 up to 1680×1050.

Out of the box, Resolutionator shows me those four, plus a “native pixels” resolution of 2560×1600. When I enable the “show non-retina resolutions” option in Resolutionator, I see a total of 12 resolutions, including one (2048×1280) that I find very usable when I need screen real estate.

You can go further, if you wish: enable the “show silly resolutions” option, and you’ll gain access to resolutions that are greater than the number of pixels on your display—the last two resolutions in the image at right show more pixels than are available on my MacBook Pro.

How does such magic work? OS X handles the hard part, scaling down the entire OS so you achieve the chosen virtual resolution. It may sound silly (hence the option’s name), but it can be very useful: On my 11″ Air, which has a maximum resolution of 1366×768, Resolutionator will let me choose 1920×1080 (and higher, but those are ridiculously hard to read). Is it usable for reading emails or small-text web pages? Not really, but it’s great for eyeballing a page layout without scrolling.

Anyway, there’s more detail on the Resolutionator web page, so head over there, take a look, and download the free trial. If you like what you see (or see more of), a measly $3 will get you a license. If you switch resolutions a lot, we think you’ll find Resolutionator an indispensable tool.

Something different: The Many Tricks holiday sale

Monday, December 15th, 2014

As promised, today we’re announcing both something new and something different … and the something different is our holiday sale. We’ve tried to keep it as simple as possible:

From now through end-of-day (USA Pacific time) on December 31st, 2014, all of our applications are 50% off—whether you buy them from us or from the App Store.

Note: App Store prices are 50% off, except in cases where the price would wind up on a $.50 split (because the App Store forces all prices to end in $.99). So for those “fifty cent split” apps, the App Store versions of each app will be $0.49 more expensive than buying directly from us.

Also note: Upgrades are not on sale. If you’re an existing user of an old version of one of our apps, just buy the full version at the sale price. It will be cheaper than the upgrade!

Finally note: If you want to save even more, just buy four or more of our apps, and you’ll save another 20%. This deal only works on purchases from our site; the App Store doesn’t allow us to create multi-item discounts.

No coupon code, no secret handshake, no treasure hunt … everything’s just half off for the next couple of weeks.

Gift purchases: If you’d like to give one or more apps as a gift, here’s how to do it:

  1. Load the Gift Our Apps web page.
  2. Select which product you’d like to gift, enter the recipient’s name and email address, then click Add to Cart.
  3. Buy whatever else you want for yourself, or proceed to checkout if it’s just a gift. (To give more than one gift, click Continue Shopping on the pop-up cart window, then change the information on the gift page and click Add to Cart again.)

When you complete your purchase transaction, you’ll receive the usual confirmation about payment, but you’ll also receive license files for the gift recipients. The email will read “Hello [your name]: Here is your license file for [product], made out to:,” followed by the recipient’s name and email address and the rest of the license email (and attached license file, of course).

You can then copy and paste the license file email (make sure you include the attachment, and probably exclude the first line with your name in it) in a new email to the recipient, and they’ll get the gifted app directly from you.

Something new: Resolutionator

Monday, December 15th, 2014

resolutionator_iconThe “something new” portion of today’s promised “something different, something new” is a public beta of Resolutionator. And what is Resolutionator? As noted in our teaser last week, it’s a tool to help you with your resolutions in the new year.

resolutions1No, not those resolutions, but resolutions like those seen at right. That’s right; Resolutionator brings back the menu bar resolution switching feature that Apple saw fit to remove at some point in the past.

But as with all our apps, Resolutionator is capable of many additional tricks. You can…

  • Use more resolutions than those available in the Displays System Preferences panel.
  • Switch resolutions via an onscreen menu, accessed via a user-defined hot key.
  • On some Macs, use resolutions greater than the available pixels. For instance, you can set a 13″ Retina MacBook Pro to display at 2880×1800 pixels, greater than its 2560×1600 true resolution. It sounds like magic, but it’s real, and it works.
  • Set resolutions for any attached displays via either the menu bar or floating resolution switcher.

Who might find Resolutionator useful? Owners of Retina Macs who find themselves switching between “OMG it’s stunning!” retina mode and “I need to see more data” more space modes. Users with multiple displays who change resolutions on one or more of the connected displays. Users of Macs with smaller screens (11″ MacBook Air, anyone?) who occasionally wished they could see more data on their screen. And probably many other people who have usage scenarios we haven’t even thought of yet.

We’ve been using Resolutionator internally for a few months, and we think it’s nearly ready to go. But before we release version 1.0, we’d like to get some feedback from the real world…and that’s where you come in: If you’d like to help beta test Resolutionator, drop us a line and we’ll provide a download link and some “getting started” instructions.

Note: Resolutionator is just an app that uses APIs provided by OS X to get and set display resolutions; it can’t harm your display by putting it into a mode it can’t support (because the monitor tells OS X what it can do, and Resolutionator uses those values for its list of available resolutions).

So if you’d like to help us test, drop us a line and we’ll get you set up.