Home > Articles > Programming > General Programming/Other Languages

OS X for iOS Developers: Why You Should Be Building Desktop Applications

iOS app developers draw on the same tools and languages used for OS X development. Erica Sadun, bestselling author of The Gourmet iOS Developer's Cookbook: Even More Recipes for Better iOS App Development, explores why iOS devs might want to consider building desktop applications.
Like this article? We recommend

Xcode. Interface Builder. Objective-C. Swift. These core tools power your iOS development tasks. Many developers, however, never consider how easily these skills transfer to the desktop. OS X development is based around the same tools and the same languages, with a large API overlap. This write-up explores what it takes to start building OS X apps from an iOS background.

Moving from UIKit to App Kit

If you can build an iOS app in Xcode using Objective-C or Swift and Interface Builder, you know pretty much everything you need to create OS X apps. Whether you're working with strings, dates, notifications, constraints, or dictionaries, the APIs are essentially identical between platforms.

The biggest difference lies in interfaces. OS X uses the AppKit framework, which supplies all the windows, buttons, menus, and views you need to build your user experience. AppKit expects mice, keyboard, and trackpad input. iOS leverages UIKit, a newer touch-based system created for smaller screens and the less precise input that finger touches entail.

While AppKit focuses on menus, windows, pop-up elements, and multitudes of buttons, checkboxes, and text fields, UIKit specializes in folding interfaces down to their essentials. It uses a bare minimum of control types to establish interaction intent. Navigation stacks compress apps to single interaction scenes. So while you may develop similar application semantics for both platforms, how you express those underlying semantics can look and feel quite different between desktop and mobile platforms.

Why Bother with OS X?

Many iOS developers discount OS X. The market is smaller, customer discovery is more difficult, and the app store less well integrated. Signing up for official distribution certificates costs an additional $99 per year, and expected revenue is almost always going to be far less than you can earn via the iOS App Store. If you want to bypass the App Store—and many developers do, because of sandboxing and other restrictions—you have to set up your own rights system and storefronts. So why develop for OS X? Compelling reasons remain.

OS X development offers a great way to expand your app beyond the phone. Whether you're connecting files through iCloud, playing games together in the game center, or offering services with Bonjour, an OS X client enables you to expand your brand and add value.

You might also explore OS X-only development. The market may be limited, but it's still a terrific ecosystem, whether you work inside the App Store or use developer signing outside it. You can build utilities to enhance people's workdays or create games to add some fun to their lives. Nothing says development has to start and end in the mobile world; you already have most of the skills you need to build OS X apps.

API Differences

Long-established video games occasionally sneak in a retro-styled level reminiscent of an older title in the series. In many ways, moving from iOS to OS X feels a lot like that. All the skills you've developed apply, but API specifics can feel slightly off or outdated.

To be fair, developing for OS X doesn't mean jumping into the past. The desktop is a lively, modern, and evolving target. Yosemite offers many new OS X features, just as 8.x added new iOS features. Moving from U

Kicking the Tires

One way to convince yourself that you already know how to develop OS X apps is to write one yourself. All you need is Xcode. In the following steps, you build a working application that interactively matches text using regular expressions:

  1. Create a new project. Choose File > New > Project and select OS X > Application > Cocoa Application. For simplicity, leave the Create Document-Based Application and Use Storyboards options unchecked. Xcode builds a working app skeleton. As with iOS templates, you can immediately run the app, which defaults to the single window in Figure 1.

    Figure 1

    Figure 1 Xcode's default project skeleton creates a single window app.

  2. Simplify the window. For this simple example, the app needs only a minimal interface. Select the window and open the Attributes inspector. Disable the Resize, Close, and Minimize checkboxes to ensure that you have a fixed-sized window that won't disappear.
  3. Add a text view and populate it. Use the Xcode object library to drag a text view onto your window. Then select View > Bordered Scroll View > Clip View > Text View in the Interface Builder document outline, as in Figure 2.

    Figure 2

    Figure 2 Text views are embedded into clip views and bordered scroll views. Navigate down the Interface Builder document outline to select them.

    Next, open the Attributes inspector. Fetch a few paragraphs of lorem ipsum–style filler text. Paste the paragraphs into the text view content field in the inspector, as in Figure 3. Then scroll down the inspector pane and disable the Editable Behavior checkbox. Don't worry about the font or text size.

    Figure 3

    Figure 3 Use the Attributes inspector to populate the text view with text.

  4. Establish a text view outlet. While holding down Control, drag from the text view in the outline to the application delegate's header file to create an outlet for the text view (see Figure 4). Name it textView.

    Figure 4

    Figure 4 Control-drag to add outlets to the header file.

  5. Add a text field and build another outlet. Next, drag in a text field and control-drag to the delegate header to build a text field outlet. Name it textField. After this step, the app delegate interface looks like this:

    @interface AppDelegate : NSObject <NSApplicationDelegate>
    @property (unsafe_unretained) IBOutlet NSTextView *textView;
    @property (weak) IBOutlet NSTextField *textField;
  6. Set the text field's delegate. Select the new text field and control-drag to the App Delegate object in the Xcode (see Figure 5). Select delegate from the pop-up to assign the app delegate as the text field's delegate. This action allows the app delegate to respond to changes typed into the text field.

    Figure 5

    Figure 5 Control-drag to set the app delegate as the text field's delegate.

  7. Add code and run. Finish the app by updating the app delegate implementation to the following code:

    @implementation AppDelegate
        NSString *lorem;
    - (void)applicationDidFinishLaunching:(NSNotification *)aNotification {
        lorem = _textView.string;
        NSAttributedString *outputString = [[NSAttributedString alloc] initWithString:lorem attributes:@{NSFontAttributeName : [NSFont fontWithName:@"Georgia" size:18.0]}];
        [_textView.textStorage setAttributedString:outputString];
    - (void) controlTextDidChange: (NSNotification *) notification
        if (notification.object != _textField) return;
        NSMutableAttributedString *outputString =   [[NSMutableAttributedString alloc] initWithString:lorem attributes:@{NSFontAttributeName : [NSFont fontWithName:@"Georgia" size:18.0]}];
        [_textView.textStorage setAttributedString:outputString];
        NSString *sourceString = _textField.stringValue;
        sourceString = [sourceString stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceAndNewlineCharacterSet]];
        NSError *error;
        NSRegularExpression *regex = [NSRegularExpression regularExpressionWithPattern:sourceString options:0 error:&error];
        if (!regex) return;
        [regex enumerateMatchesInString:lorem options:0 range:NSMakeRange(0, lorem.length) usingBlock:^(NSTextCheckingResult *match, NSMatchingFlags flags, BOOL *stop)
             NSRange range = match.range;
             BOOL abut = (range.location + range.length) >= lorem.length;
             if (!abut)
                 [outputString addAttribute:NSForegroundColorAttributeName value:[NSColor greenColor] range:range];
                 [outputString addAttribute:NSUnderlineStyleAttributeName value:@(NSUnderlineStyleThick) range:range];
        [_textView.textStorage setAttributedString:outputString];

Each time the user updates the text field, these methods treat that text as a regular expression and mark out matching occurrences in the text view. Figure 6 shows the running application.

Figure 6

Figure 6 The running application matches input expressions to the lorem ipsum text displayed in the text view. This particular search locates strings of three lower-case letters followed by an additional lowercase letter l. Matches are underlined and colored green.

This code is nearly identical to the code you'd build for iOS. Text storage, attributed strings, and regular-expression handling offer practical cross-platform solutions. The font uses NSFont instead of UIFont, but the call to create an 18-point instance is pretty much the same between platforms. Only the delegate method controlTextDidChange: is markedly different, as iOS uses a more formal UITextFieldDelegate protocol.

The steps used in Interface Builder should also feel familiar. The control-drags to create outlets and connect properties are equivalent to those used for iOS development. Yes, a few things (notably the stand-alone window and the embedded text view) feel different from iOS, but it's the similarities more than the differences that win.

IKit to AppKit does involve a learning curve. If you're prepared to elbow grease your way through web searches, you can easily get up and going with OS X dev.

OS X has been around since 2001—longer, if you take the beta period into account, and even longer if you consider NeXTStep, its predecessor, as part of the evolution. Sample code, mailing list discussions, and how-to write-ups abound. Just about any challenge you run into can be solved with a mix of Google searches and peer support, whether on the Apple developer forums or on IRC. Freenode hosts a #macdev chatroom for OS X development issues.


OS X is a platform that's well worth investigating for many iOS developers. As the simple project in this write-up demonstrates, the distance between iOS and OS X is minimal. iOS skills readily transfer to OS X, and you can start building your own desktop projects in almost no time at all.

You'll find a working copy of this sample project at https://github.com/erica/useful-things in the informit folder.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020