Home > Articles > Programming > General Programming/Other Languages

Replacing Flash with Cocoa

📄 Contents

  1. Why Replace Flash?
  2. Loading the Videos
In light of Apple's recent hostility to Flash, David Chisnall takes a look at replacing a Flash application with a native Cocoa implementation on OS X, using the player for his newly released series of LiveLessons as a case study.
Like this article? We recommend

My new series of LiveLessons, Cocoa Programming Fundamentals, was released recently. (You can probably see an ad alongside this article, encouraging you to buy them.) The DVD version comes with a Flash application for playing the videos. In this article, we'll look at how to replace that Flash app with a native Cocoa version. Don't worry if you haven't bought the LiveLessons—you may still find some of the information in this article to be useful.

Why Replace Flash?

In April 2010, Apple posted an open letter from Steve Jobs on its website, containing a set of (rambling and inconsistent) reasons for not supporting Flash on the iPhone. In case you've been in a coma for the last 15 years, Flash is an Adobe product, purchased from Macromedia, for producing multimedia applications and applets. Used via a plug-in for web browsers and to produce native apps, Flash runs on the vast majority of systems.

The Flash design has some advantages and disadvantages. The advantages are obvious: You can write a Flash app once and then deploy it almost anywhere—exactly what Java promised in the 1990s. Flash is more than just a language, though; it's a complete virtual machine that includes features such as sound and video playback, animations, text rendering, vector art, and so on.

The downside is that Flash is a complete platform of its own, running on top of the native platform, which means that Flash apps don't look and feel like other apps. This approach is fine for things like games, where a native look and feel can harm the player's immersion, but not ideal for other purposes. Because Flash handles text internally, we can use text rendering to see a concrete example of this problem. Look at how differently Flash and Cocoa render the same word, Cocoa, in Figure 1 (the Flash version) and Figure 2 (the Cocoa version).

Figure 1 Flash text rendering.

Figure 2 Cocoa text rendering.

Cocoa uses sub-pixel anti-aliasing, whereas Flash uses whole-pixel anti-aliasing. This difference makes the Flash version look quite blurry when rendered at the correct size. Subtle differences in the kerning also make the Flash text look wrong to people who are accustomed to how OS X renders text.

Another problem that many people complain about is Flash's video playback performance. The Flash implementation of H.264 video compression is terrible. Adobe claims that the problem occurs because Apple doesn't expose low-level APIs for acceleration. But this reasoning doesn't explain why FFmpeg uses about half as much CPU effort as Flash does when decoding H.264, and doesn't require hardware acceleration.

Apple ships an H.264 decoder/encoder as part of QuickTime on OS X. Any application can use this tool, rather than reinventing the wheel. Adobe claims that this approach isn't feasible, because Flash needs to composite other things on top of the video. This argument also doesn't make sense, because QuickTime can render to an OpenGL texture or a Core Animation layer, either of which can then be composited into a scene by using hardware acceleration. The fact that this technique isn't feasible for Adobe implies that Flash is doing all of the compositing in software, which would help to explain its poor performance.

Few of these issues are specific to Flash, of course. Cross-platform APIs always have some similar drawbacks. The price of running on multiple platforms is being constrained to the lowest common denominator, which is why good cross-platform applications tend to have a portable core and some per-platform additions.

Designing the Cocoa Application

The viewer application on the LiveLessons DVD is quite simple: Its single window displays some introductory text on the left and an outline view on the right. When you select an item from the outline view, the viewer switches to displaying the selected video.

We can create this application very easily in Cocoa. In the nib file, we create a window containing all of the views for the initial state. We also create a free-standing NSView containing the QTMovieView (for playing the videos) and some other controls. Switching between the windows is just a matter of replacing one with the other in the view hierarchy, which we can do with this method:

- (void)switchViews
    [self exitFullScreen: self];

    NSView *v = [window contentView];
    NSView *newView = inVideo ? menuView : videoView;
    NSView *oldView = inVideo ? videoView : menuView;
    newView.frame = oldView.frame;
    [v.animator replaceSubview: oldView with: newView];
    inVideo = !inVideo;

Notice that we use the animator property of the window's content view. This is a proxy object used by Core Animation. When you send a message that changes the target state, the animator proxy animates the transition, so you can control the type and duration of the animation entirely in Interface Builder. You don't need to modify the code at all to use a different animation—just select the desired animation from the inspector in Interface Builder.

Because this is a very simple application, we'll create only one new class, which we'll set as the application's delegate. This entire program is only a couple of hundred lines of code. We could separate it out a bit more, but it's not really worth the effort. If you want to extend it to do more complicated things, some refactoring might be in order.

The application shouldn't hardcode anything about the lesson itself. The Flash version uses an XML file to describe each LiveLesson used with it. We could reuse that file, but it's simpler in Cocoa to use a property list.

Controlling the Contents

The property list that describes the lesson is stored in the .app bundle's Resources directory. Cocoa provides some convenient methods for finding and loading the list:

NSBundle *mainBundle = [NSBundle mainBundle];
// Get the path of the project plist
NSString *path = [mainBundle pathForResource: @"project" ofType: @"plist"];
// Load it as a dictionary
lessonDescription = [[NSDictionary dictionaryWithContentsOfFile: path] retain];

First we get the object that encapsulates the application's main bundle. Next, we use that bundle to find the path of the project.plist file. This is stored as an XML property list (or you could use a binary or OpenStep-style plist), which we can edit in a text editor or in XCode's graphical property list editor.

Finally, we use a convenience method on NSDictionary that constructs a new dictionary instance from the contents of the property list file. Then we can use the dictionary just like any other dictionary. It's trivial to add new keys to the code and add the corresponding data to the property list; you don't need to write any code for parsing configuration files.

This is all of the code needed to load the list of lessons to populate the outline view:

// Set the lesson dictionary in a KVO-compatible way
// so that the bindings notice the change
[self willChangeValueForKey: @"children"];
children = [lessonDescription objectForKey: @"Lessons"];
[self didChangeValueForKey: @"children"];

The lessons are stored as a tree in the property list. The Lessons key refers to an array containing one item for each of the 12 lessons. Figure 3 shows the project.plist file in XCode's property list viewer. Notice that each lesson is a dictionary and contains an array for the children key. This array has a child for each video in the series, containing the video filename and some metadata.

Figure 3 The project property list in XCode.

If you look in the nib file, you can see how this design populates the outline view without requiring any code. The outline view column is connected with Cocoa bindings to an NSTreeController instance. The tree controller is bound to the children key in our object, so setting this key in a way that respects key-value observing means that it's automatically picked up by the controller.

This same pattern is used with the chapters dictionary from each lesson in the property list, populating the pop-up button, which allows the user to jump to different chapters in the file.

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