We initially built our Mac SDK to help anyone developing a Mac-only or cross-platform app save significant time building common features when your time could be better spent coding a great product.
It makes it incredibly easy to take payments in-app, use licensing for access control and / or offer trials to your users - either using our off-the-shelf payments, trials and licensing solution or customizing and using the bits you don’t want to build and maintain yourself.
Hundreds of Mac developers use our platform, often in highly creative ways. Our current and highly popular Mac SDK v3 worked well but was initially built for simpler billing and licensing models, which means that your creativity came at the cost of increasingly complex integrations and work-arounds.
We’ve taken all we’ve seen in the last years, all our discussions and feedback and turned them into a Mac SDK v4 that is more flexible and customizable, works well with more complex billing or product models, increases anti-piracy protection… And is fully Mojave-compatible (including dark mode!).
Any Billing Model Goes
We’ve made it easier to use subscription billing and now support any billing model you can create in our dashboard. We’ve also improved the clarity of what you can or cannot do, making setting it up much more intuitive.
Customize Your User Journey
We’ve now made it easy to pick and choose what you handle and what we do by decoupling the UI.
Thich means you can delegate everything to us or intercept the UI or logic behind any part of the user journey, in essence letting you customize any part of your trial, licensing and checkout journey.
Flexible Licensing Management
Our Mac SDK v3 only worked if you wanted us to handle both payments, trials and licensing - with our PADPurchaseView as an alternative if you just wanted the checkout.
You can do both with the same Mac SDK v4: let us handle everything, or manage the licensing yourself and use our in-app checkout.
Better Support for Multiple and Child Product Models
Products are now their own object, with typed properties which can be passed from method to method and contain their state, product info, etc.
This significantly improves two frequent use cases:
You sell multiple products / plans within a single app . You won’t need to hardcode product or subscription data any longer.
You sell one app with many ways to buy it . This makes it very simple to unlock and sell specific features within your app.
Easier and Faster Integration
We’ve made simple implementations quicker to get up and running and complex ones much easier to manage.
We’ve also done some spring cleaning. We’ve removed deprecated, unsupported, and generally rarely used features. We’ve also reduced the size of the public header files by combining and simplifying our code.
Improved Anti-Piracy Protection
We’ve especially closed one loophole where legacy v2 licenses could be faked. As soon as you upgrade to v4, any ancient license will be re-verified. If our checks fail for a given license we will by default deactivate it.
If you choose so, you can intercept our deactivation with a hook and take your own measures - for example, upsell a real license to the user who may by now love your product enough to buy it!
Fully Mojave Compatible - Including Dark Mode
Mojave is coming, and we’re ready for it. Dark mode was our favourite part of WWDC 2018, so your users will be able to activate a license or buy your software in dark mode as soon as you migrate to v4.
Migrating to the Mac SDK v4
We’ve prepared 2 short guides to help you get started:
If you’re currently using the Mac SDK v3, follow our guide to migrating from v3 to v4.
If you’re starting from scratch, follow our guide to getting started with v4.
We will continue to maintain the Mac SDK v3 for 12 months, to allow ample time for your transition. This will be our sunset strategy going forward with major SDK releases.
If you want help and advice to migrate or get started with our new Mac SDK v4, get in touch with our seller success team!