TweetFollow Us on Twitter

Strange Brew

Volume Number: 20 (2004)
Issue Number: 3
Column Tag: Programming

QuickTime Toolkit

by Tim Monroe

Strange Brew

Running QuickTime for Java Applications on Windows


In the two previous QuickTime Toolkit articles (in MacTech, January and February 2004), we took a look at using Apple's QuickTime for Java classes to build a simple Java-based Macintosh application that can manipulate QuickTime movies. Our application -- called "JaVeez" -- can open movie files and display their movies in windows on the screen. Figure 1 shows a typical movie window displayed by JaVeez.

Figure 1: A JaVeez movie window (Macintosh)

JaVeez supports all the standard editing operations on linear movies and can save edited movies into their original files or into new files. If the user tries to close an edited movie file, JaVeez displays the dialog box shown in Figure 2, which gives the user the opportunity to save or discard those edits.

Figure 2: The Save Changes dialog box (Macintosh)

In this article, I want to investigate what needs to be done to get JaVeez to run on Windows operating systems as well as on Mac OS X. In other words, I want to see how to turn the window in Figure 1 into the window in Figure 3.

Figure 3: A JaVeez movie window (Windows)

And I want to see how to turn the dialog box in Figure 2 into the similar dialog box in Figure 4.

Figure 4: The Save Changes dialog box (Windows)

The good news is that we don't really need to do very much work at all to get JaVeez running on Windows, thanks to its Java underpinnings and to the platform-independent graphical toolkits AWT and Swing. We need to add a small amount of platform-specific code to adjust the placement of the Quit and "About JaVeez" menu items, and we need to make a few adjustments to our Xcode project. But ultimately, and indeed fairly quickly, we'll have a single executable file that can be launched on both Mac OS X and Windows computers.

Once we've got JaVeez running on Windows, we'll take a look at extending it on both platforms by allowing the user to resize its movie windows. To do that, we'll need to install a movie controller action filter procedure. As we've had some trouble doing that with a few of the development environments we've considered in recent articles, it will be interesting to see how easy it is to do this using QuickTime for Java.


Let's begin by considering the code changes we need to make to get JaVeez running properly on Windows, all of which are related to the creation and handling of menus. On Mac OS X, the "About JaVeez" and Quit menu items are contained in the Application menu. On Windows, those items need to be moved into the File menu and the Help menu, respectively. Figure 5 shows the File menu on Windows. Notice that the Quit item is labeled "Exit" on Windows.

Figure 5: The File menu of JaVeez (Windows)

Figure 6 shows the Help menu on Windows.

Figure 6: The Help menu of JaVeez (Windows)

First we need to create the new menu and menu items; then we need to attach actions to those new menu items.

Creating Menus and Menu Items

It's easy enough to add a separator line and the Exit menu item to our existing File menu. The only mildly interesting hoop we need to jump through is to figure out whether JaVeez is running on Macintosh or Windows. There are in fact at least three ways we can do this.

The standard way to check whether a Java application is running on Macintosh is to look at the mrj.version property, like this:

if (System.getProperty("mrj.version") != null)

"MRJ" stands for "Macintosh Runtime for Java", which was the official name of earlier versions of the Java support on Macintosh computers. If the mrj.version property exists, then the string object returned by the System.getProperty method is non-null and hence our application is running on some version of Mac OS.

While this way of determining that our application is running on Mac OS is still supported in JS2E version 1.4.1 and later, it is no longer the recommended way of doing so. A better way is to look at the property, like this:

if (System.getProperty("").equalsIgnoreCase(
                                                         "Mac OS X"))

This expression evaluates to true just in case our application is running on some version of Mac OS X.

There is yet a third way to determine the current system our application is running on, using the QTSession class we encountered in the two previous articles:

if (QTSession.isCurrentOS(QTSession.kMacOSX))

We'll use this third way throughout our application. For instance, Listing 1 shows the code we'll add to the addFileMenuItems method to add the Exit menu item to the bottom of the File menu.

Listing 1: Adding items to the File menu

if (!(QTSession.isCurrentOS(QTSession.kMacOSX))) {
   miExit = new MenuItem(resBundle.getString("exitItem"));
   miExit.setShortcut(new MenuShortcut(KeyEvent.VK_Q, 

And Listing 2 shows the complete revised version of the addMenus method.

Listing 2: Configuring the menu bar

public void addMenus () {
   editMenu = new Menu(resBundle.getString("editMenu"));
   fileMenu = new Menu(resBundle.getString("fileMenu"));
   movieMenu = new Menu(resBundle.getString("movieMenu"));
   if (!QTSession.isCurrentOS(QTSession.kMacOSX)) {
      helpMenu = new Menu(resBundle.getString("helpMenu"));

The addHelpMenuItems method, which is called by this new version of addMenus, is defined in Listing 3.

Listing 3: Adding items to the Help menu

public void addHelpMenuItems () {
   miAbout = new MenuItem(resBundle.getString("aboutItem"));

Creating Actions

All that remains is to define two new action classes and to create instances of those two classes (which, as we saw in Listings 1 and 3, we add as listeners to the Exit and "About JaVeez" menu items). Listing 4 shows how we can handle the Exit menu item on Windows. As you can see, we simply call the existing method attempQuit, which inspects all open movie windows and gives the user the chance to save or discard any unsaved changes.

Listing 4: Handling the Exit menu item (Windows)

public class ExitActionClass extends AbstractAction {
   public ExitActionClass (String text, KeyStroke shortcut) {
      putValue(ACCELERATOR_KEY, shortcut);
   public void actionPerformed (ActionEvent e) {

Similarly, Listing 5 shows how we can handle the "About JaVeez" menu item on Windows; again, we just call an existing method, about.

Listing 5: Handling the About menu item (Windows)

public class AboutActionClass extends AbstractAction {
   public AboutActionClass (String text) {
   public void actionPerformed (ActionEvent e) {

Finally, we need to add a few lines of code to the createActions method to create instances of these two classes; Listing 6 shows the code we need to add.

Listing 6: Creating actions

if (!(QTSession.isCurrentOS(QTSession.kMacOSX))) {
   exitAction = new ExitActionClass(
                        resBundle.getString("exitItem"), KeyStroke.getKeyStroke(
                                    KeyEvent.VK_Q, shortcutKeyMask));
   aboutAction = new AboutActionClass(

When this is all done, the File and Help menus will have the appearance shown earlier in Figures 5 and 6. Selecting the Exit menu item performs the standard application shutdown operations. And selecting the "About JaVeez" item displays the dialog box shown in Figure 7.

Figure 7: The About box of JaVeez (Windows)

Note that we haven't changed any of the code called by the new actions. Our About box looks pretty much the same as its Macintosh counterpart, thanks to the wonders of Java and Swing.

Java Applications

Recall that we started building JaVeez by creating a new Xcode project based on the "Java AWT Application" template. The target built by Xcode is a double-clickable Macintosh application named This application responds appropriately to the basic Apple events OpenApplication, OpenDocuments, and QuitApplication. This means, in particular, that JaVeez automatically opens QuickTime movie files and Flash files dropped onto its icon in the Finder or in the Dock.

In fact is just a directory that holds some special items. We can inspect those items by option-clicking on the JaVeez icon and selecting the "Show Package Contents" item. A Finder window opens that holds a folder named Contents. The Contents folder contains a folder named Resources, which in turn contains a folder named Java. Figure 8 shows the contents of the Java folder:

Figure 8: The JaVeez.jar file

JaVeez.jar is a Java archive file, also called a jar file. It contains the executable code of the application along with any images or other resources used by the application. Jar files are the standard distribution containers for Java applications. In theory, we should be able to move this jar file to a Windows machine, double-click it, and have JaVeez launch and run. In practice, we need to make a couple of minor tweaks to our project for this to work correctly.

Fixing the Manifest

Indeed, double-clicking this existing JaVeez.jar file won't even launch JaVeez on Mac OS X. If we try it, we'll see the warning shown in Figure 9.

Figure 9: The launch warning

The Console log contains this message:

Failed to load Main-Class manifest attribute from

The problem is that the default jar file's manifest (a special file in the archive that contains information about the other files in the archive) does not indicate which class in the jar file is the main class. To fix this, let's add to the project a new file called that contains these lines:

Main-Class: JaVeez

(There is a newline character at the end of the first line; it needs to be there in order for our new manifest to work correctly.) Then we can set this file as the project's manifest file by specifying its name in the target settings panel, as shown in Figure 10. When we build JaVeez, the lines in the file will be appended to the default manifest data.

Figure 10: The manifest file setting

While we're here, let's adjust one other project setting, to prevent an annoying but harmless warning from being issued each time we launch JaVeez. Select the "Cocoa Java-Specific" pane and uncheck the "Needs Java" box, which is shown in Figure 11.

Figure 11: The "Needs Java" setting

Leaving that setting at its default value will result in this warning appearing on the console whenever we launch JaVeez:

-[NSJavaVirtualMachine initWithClasspath:] cannot 
                           instantiate a Java virtual machine:

Let's rebuild JaVeez so that these changes take effect. Now double-clicking the jar file will launch the application, as desired. That's very cool. What's perhaps not so cool is that when we launch JaVeez by double-clicking the JaVeez.jar file, we lose the Finder interaction we got when we launched it by double-clicking the file; in particular, we can't drop files onto the JaVeez.jar file or into its Dock icon.

Adding Stub Classes

Can we now move the jar file to a Windows machine and run it? Not quite, but almost. Recall that JaVeez uses the Application class in the package to handle the basic application-related Apple events. This package is not implemented on Windows, so we need to do a little bit of work to keep the Windows Java runtime engine happy.

There are several ways to work around this issue. The easiest way is to add some stub classes to our project that provide empty implementations of the classes and methods in Fortunately, Apple provides a set of stubs that can be used for this purpose. Look for the sample code package called AppleJavaExtensions on the Apple developer site. This package consists of a file called AppleJavaExtensions.jar. We need to unpack that jar file; in a Terminal window, execute this command:

jar -xf AppleJavaExtensions.jar

When this command completes successfully, you'll see two new directories named META-INF and com. Copy the com directory into the JaVeez folder that contains the application project files and source code. Add that folder to the project; the project file now looks like Figure 12.

Figure 12: The updated project file

Build the project and copy the JaVeez.jar file to a computer running Windows that has Java and QuickTime installed on it. Double-click the jar file and behold the new empty movie window that appears (Figure 13).

Figure 13: An empty movie window (Windows)

Use the Open menu item in the File menu to open a QuickTime movie file and then spend a few minutes verifying that the movie and its window behave as expected. (See Figure 3 again.)

Let's pause to consider our progress so far. We now have a fully-functional Windows application, and we did that with just a couple of easy adjustments to our existing project and source code. We added some code to handle the different locations of the Quit/Exit and About menu items on Mac and Windows, and we tweaked the jar file's manifest to specify the application's main class. Also, we added a few stub classes to our project to provide empty implementations of the package for Windows. Everything runs fine. We're done, right?

Using Reflection

Wrong. To be honest, I'd be very happy to consider our porting work done and then move on to add some features to JaVeez that show off the interesting capabilities of QuickTime for Java. After all, we do now have a single jar file that runs on both Mac OS X and Windows and that has all the features we originally planned. But in fact we're not quite finished. The reason is that the stub-class solution described above, though technically impeccable in terms of getting the job done, has a decidedly non-Java flavor. The generally-preferred solution to the problem of classes being implemented on one platform but not on another is to use a feature of the Java language known as reflection. If you're happy using the stub classes, skip to the next section. Otherwise, read on....

Here's the crux of the issue: JaVeez currently contains the following line of code, which creates an instance of the class and attaches it to fApplication.

                  new {

When the Java runtime engine loads a package, it looks for all classes referenced in the package. Even though this line of code won't actually be executed on Windows, the runtime loader still wants to find some code for the ApplicationAdapter class.

Rather than solve this problem by providing no-op implementations of the classes in, which is what the stub classes provide, we can factor the relevant code into a new package and then load that package only if JaVeez is running on Mac OS X. The Windows runtime engine never sees the references to, so the stubs are no longer necessary. Very nice.

Let's begin by defining a new package, called "osxadapter", which imports the classes and the JaVeez application classes:

package osxadapter;
import javeez.*;

The osxadapter package contains a single class, OSXAdapter, which defines three public methods: handleAbout, handleQuit, and registerMacOSXApplication. (The code upon which this class is based defines two additional methods for handling an application's preferences; since JaVeez does not support user-selectable preferences, I've taken the liberty of removing those methods.) Listing 7 shows the complete definition of the OSXAdapter class.

Listing 7: Handling Application menu items

public class OSXAdapter extends ApplicationAdapter {
   private static OSXAdapter    theAdapter;
   private static
   private JaVeez    mainApp;
   private OSXAdapter (JaVeez inApp) {
      mainApp = inApp;
   // handle the About menu item
   public void handleAbout (ApplicationEvent ae) {
      if (mainApp != null) {
      } else {
         throw new IllegalStateException("handleAbout: JaVeez 
         instance detached from listener");
   // handle the Quit menu item
   public void handleQuit (ApplicationEvent ae) {
      if (mainApp != null) {
      } else {
         throw new IllegalStateException("handleQuit: JaVeez instance 
         detached from listener");
   public static void registerMacOSXApplication (JaVeez inApp) {
      if (theApplication == null) {
         theApplication = new;
      if (theAdapter == null) {
         theAdapter = new OSXAdapter(inApp);

The first two methods, handleAbout and handleQuit, simply call the existing about and attemptQuit methods in JaVeez. They also both call the setHandled method of the ApplicationEvent class to indicate whether or not the event has been handled. Notice that handleQuit needs to pass false to setHandled since we want to allow the user to cancel the application shut-down operation.

The interesting method in the OSXAdapter class is registerMacOSXApplication, which creates an instance of the Application class, creates an instance of the OSXAdapter class, and then adds the adapter object as a listener for the Application object. The registerMacOSXApplication method is the only method that JaVeez needs to call explicitly at run-time. Of course JaVeez cannot invoke that method by name (since it references classes that do not exist on Windows machines); rather, it invokes that method indirectly, using Java's reflection APIs. Listing 8 shows the definition of the macOSXRegistration method that we need to add to JaVeez.

Listing 8: Registering a Mac OS X application

public void macOSXRegistration () {
   if (QTSession.isCurrentOS(QTSession.kMacOSX)) {
      try {
         Class osxAdapter = 
         Class[] defArgs = {JaVeez.class};
         Method registerMethod = 
                              "registerMacOSXApplication", defArgs);
         if (registerMethod != null) {
            Object[] args = {this};
registerMethod.invoke(osxAdapter, args);
      } catch (Exception e) {

As you can see, macOSXRegistration calls Class.forName to find the class named "OSXAdapter" in the package osxadapter. If it finds it, macOSXRegistration executes that method by calling the invoke method.

Callback Procedures

So JaVeez now runs on both Macintosh and Windows computers. We can open one or more QuickTime movies, play them back or interact with them, edit them, and save or discard those edits as desired. JaVeez currently meets or exceeds all our original requirements, using nothing more than standard Java or QuickTime for Java classes and methods.

Let's consider briefly how to extend JaVeez. In particular, let's see how to install a movie controller action filter procedure to receive and respond to movie controller actions. For the moment, we'll handle only the mcActionControllerSizeChanged action, which lets us know that the controller has changed size. We'll use that action to support resizing of movie windows.

Resizing Movie Windows

You may recall from our first article on Java and QuickTime that we initially configured our movie windows so that they cannot be resized by the user; we did that by adding this line of code to the JaVeez class constructor:


Now you might think that part of what we need to do in order to allow resizable windows is to change that false to true. Unfortunately, doing that would lead to problems, because AWT would want to draw its own grow box in the lower-right corner of a movie window, as shown in Figure 14.

Figure 14: A movie window with the AWT grow box

Instead, we want to use the grow box provided by the QuickTime movie controller, which you can see in Figure 15.

Figure 15: A movie window with the movie controller grow box

To accomplish this, we'll continue to pass false in the call to setResizable. We'll get the movie controller to draw its grow box in the standard way, by defining a non-empty grow box rectangle. In the createNewMovieFromFile method, we'll execute these lines of code:

QDRect rect = new QDRect(32000, 32000);

Once we've done this, the movie controller will draw the grow box in the appropriate location and allow the user to resize a movie by click-dragging in that box.

Handling Movie Controller Actions

Now we need to resize the Java frame (that is, window) when the user resizes the movie using the grow box. As usual, we do this by suitably responding to the mcActionControllerSizeChanged action. First, we need to define a movie controller action filter method. Listing 9 shows the code we'll add to JaVeez.

Listing 9: Defining a movie controller action filter method

public class MCActionFilter extends ActionFilter {
   public boolean execute (MovieController mc, int action) { 
     if (action == 
                  StdQTConstants.mcActionControllerSizeChanged) {
      return false; 

As you can see, we simply call the pack method when we receive the appropriate action. We also need to implement the getPreferredSize method, which is called by pack. Listing 10 shows our getPreferredSize method.

Listing 10: Setting the size of a movie window

public Dimension getPreferredSize () {
   Dimension frameDim = new Dimension(0, 0);
   try {
      QDRect rect = m.getBox();
      if (mc.getVisible())
         rect = mc.getBounds();
      // make sure that the movie has a non-zero width;
      // a zero height is okay (for example, with a music movie with 
         no controller bar)
      if (rect.getWidth() == 0)
      // resize the frame to the calculated size, plus window borders
               rect.getWidth() + (getInsets().left + 
               rect.getHeight() + (getInsets().top + 
   } catch (QTException err) {

There's nothing much new here. In fact, this method is based on the sizeWindowToMovie method that appeared in the first article in this series. Using getPreferredSize is by far better Java code.

Finally, we need to install the action filter method, like this:

mc.setActionFilter(new MCActionFilter(), false);

With these changes, the movie windows displayed by JaVeez should resize as expected.


QuickTime for Java provides a very nice set of capabilities for building QuickTime applications with Java. The support for displaying and controlling movies using movie controller components is extensive and easy to use. And, as we've seen in detail in this article, it's extremely easy to write our applications in such a way that they are easily portable to Windows computers running QuickTime and Java. Whether we use Java's reflection APIs or resort to the stub classes, we can get our OS X application running on Windows in a matter of minutes. Cross-platform portability is of course one of the key promises of Java, and it's refreshing to see that promise realized so fully in this case.


Thanks are due once again to Anant Sonone for his assistance and support. The OSXAdapter class is based upon sample code by Matt Drance, who also graciously provided advice on these issues.

Tim Monroe is a member of the QuickTime engineering team at Apple. You can contact him at The views expressed here are not necessarily shared by his employer.


Community Search:
MacTech Search:

Software Updates via MacUpdate

Live Home 3D Pro 3.2.2 - $69.99
Live Home 3D Pro, a successor of Live Interior 3D, is the powerful yet intuitive home design software that lets you build the house of your dreams right on your Mac. It has every feature of Live Home... Read more
Live Home 3D Pro 3.2.2 - $69.99
Live Home 3D Pro, a successor of Live Interior 3D, is the powerful yet intuitive home design software that lets you build the house of your dreams right on your Mac. It has every feature of Live Home... Read more
FileZilla - Fast and reliable F...
FileZilla (ported from Windows) is a fast and reliable FTP client and server with lots of useful features and an intuitive interface. Version MSW: Add misssing file to .zip binary package... Read more
Spotify - Stream music, crea...
Spotify is a streaming music service that gives you on-demand access to millions of songs. Whether you like driving rock, silky R&B, or grandiose classical music, Spotify's massive catalogue puts... Read more
Sierra Cache Cleaner 11.0.6 - Clear cach...
Sierra Cache Cleaner is an award-winning general purpose tool for macOS X. SCC makes system maintenance simple with an easy point-and-click interface to many macOS X functions. Novice and expert... Read more
DiskCatalogMaker 7.1.2 - Catalog your di...
DiskCatalogMaker is a simple disk management tool which catalogs disks. Simple, light-weight, and fast Finder-like intuitive look and feel Super-fast search algorithm Can compress catalog data for... Read more
Live Home 3D Pro 3.1.2 - $69.99
Live Home 3D Pro, a successor of Live Interior 3D, is the powerful yet intuitive home design software that lets you build the house of your dreams right on your Mac. It has every feature of Live Home... Read more
Deeper 2.2.1 - Enable hidden features in...
Deeper is a personalization utility for macOS which allows you to enable and disable the hidden functions of the Finder, Dock, QuickTime, Safari, iTunes, login window, Spotlight, and many of Apple's... Read more
Pinegrow 3.04 - Mockup and design webpag...
Pinegrow (was Pinegrow Web Designer) is desktop app that lets you mockup and design webpages faster with multi-page editing, CSS and LESS styling, and smart components for Bootstrap, Foundation,... Read more
Deeper 2.2.1 - Enable hidden features in...
Deeper is a personalization utility for macOS which allows you to enable and disable the hidden functions of the Finder, Dock, QuickTime, Safari, iTunes, login window, Spotlight, and many of Apple's... Read more

Latest Forum Discussions

See All

The best deals on the App Store this wee...
There are quite a few truly superb games on sale on the App Store this week. If you haven't played some of these, many of which are true classics, now's the time to jump on the bandwagon. Here are the deals you need to know about. [Read more] | Read more »
Realpolitiks Mobile (Games)
Realpolitiks Mobile 1.0 Device: iOS Universal Category: Games Price: $5.99, Version: 1.0 (iTunes) Description: PLEASE NOTE: The game might not work properly on discontinued 1GB of RAM devices (iPhone 5s, iPhone 6, iPhone 6 Plus, iPad... | Read more »
Layton’s Mystery Journey (Games)
Layton’s Mystery Journey 1.0.0 Device: iOS Universal Category: Games Price: $15.99, Version: 1.0.0 (iTunes) Description: THE MUCH-LOVED LAYTON SERIES IS BACK WITH A 10TH ANNIVERSARY INSTALLMENT! Developed by LEVEL-5, LAYTON’S... | Read more »
Full Throttle Remastered (Games)
Full Throttle Remastered 1.0 Device: iOS Universal Category: Games Price: $4.99, Version: 1.0 (iTunes) Description: Originally released by LucasArts in 1995, Full Throttle is a classic graphic adventure game from industry legend Tim... | Read more »
Stunning shooter Morphite gets a new tra...
Morphite is officially landing on iOS in September. The game looks like the space shooter we've been needing on mobile, and we're going to see if it fits the bill quite shortly. The game's a collaborative effort between Blowfish Studios, We're Five... | Read more »
Layton's Mystery Journey arrives to...
As you might recall, Layton's Mystery Journey is headed to iOS and Android -- tomorrow! To celebrate the impending launch, Level-5's released a new trailer, complete with an adorable hamster. [Read more] | Read more »
Sidewords (Games)
Sidewords 1.0 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0 (iTunes) Description: Grab a cup of coffee and relax with Sidewords. Sidewords is part logic puzzle, part word game, all original. No timers. No... | Read more »
Noodlecake Games' 'Leap On!...
Noodlecake Games is always good for some light-hearted arcade fun, and its latest project, Leap On! could carry on that tradition. It's a bit like high stakes tetherball in a way. Your job is to guide a cute little blob around a series of floating... | Read more »
RuneScape goes mobile later this year
Yes, RuneScape still exists. In fact, it's coming to iOS and Android in just a few short months. Jagex, creators of the hit fantasy MMORPG of yesteryear, is releasing RuneScape Mobile and Old School RuneScape for mobile devices, complete with... | Read more »
Crash of Cars wants you to capture the c...
Crash of Cars is going full on medieval in its latest update, introducing castles and all manner of new cars and skins fresh from the Dark Ages. The update introduces a new castle-themed map (complete with catapults) and a gladiator-style battle... | Read more »

Price Scanner via

Save or Share
FotoJet Designer, is a simple but powerful new graphic design apps available on both Mac and Windows. With FotoJet Designer’s 900+ templates, thousands of resources, and powerful editing tools you... Read more
Logo Maker Shop iOS App Lets Businesses Get C...
A newly released app is designed to help business owners to get creative with their branding by designing their own logos. With more than 1,000 editable templates, Logo Maker Shop 1.0 provides the... Read more
Sale! New 15-inch MacBook Pros for up to $150...
Amazon has the new 2017 15″ MacBook Pros on sale for up to $150 off MSRP including free shipping: – 15″ 2.8GHz MacBook Pro Space Gray: $2249 $150 off MSRP – 15″ 2.89Hz MacBook Pro Space Gray: $2779 $... Read more
DEVONthink To Go 2.1.7 For iOS Brings Usabili...
DEVONtechnologies has updated DEVONthink To Go, the iOS companion to DEVONthink for Mac, with enhancements and bug fixes. Version 2.1.7 adds an option to clear the Global Inbox and makes the grid... Read more
15-inch 2.2GHz Retina MacBook Pro, Apple refu...
Apple has Certified Refurbished 2015 15″ 2.2GHz Retina MacBook Pros available for $1699. That’s $300 off MSRP, and it’s the lowest price available for a 15″ MacBook Pro. An Apple one-year warranty is... Read more
13-inch 2.3GHz Silver MacBook Pro on sale for...
B&H Photo has the new 2017 13″ 2.3GHz/256GB Silver MacBook Pro (MPXU2LL/A) on sale for $1399 including free shipping plus NY & NJ sales tax only. Their price is $100 off MSRP. Read more
Apple Tackles Distracted Driving With iOS 11...
One of the most important new features coming in iOS 11 is Do Not Disturb while driving, intended to help drivers stay more focused on the road. With Do Not Disturb while driving, your iPhone can... Read more
iMazing Mini for Mac: Free Automatic and Priv...
Geneva, Switzerland-based indie developer DigiDNA has released iMazing Mini, their free macOS utility designed to automatically back up iOS devices over any local Wi-Fi network. The app offers users... Read more
Clearance 2016 13-inch MacBook Airs, Apple re...
Apple dropped prices recently on Certified Refurbished 2016 13″ MacBook Airs, with models now available starting at $809. An Apple one-year warranty is included with each MacBook, and shipping is... Read more
9.7-inch 2017 iPads available for $299, save...
B&H Photo has 2017 9.7″ 32GB WiFi iPads on sale for $30 off MSRP for a limited time. Shipping is free, and pay sales tax in NY & NJ only: – 32GB iPad WiFi: $299, $30 off Read more

Jobs Board

*Apple* Retail - Multiple Positions - Apple...
SalesSpecialist - Retail Customer Service and SalesTransform Apple Store visitors into loyal Apple customers. When customers enter the store, you're also the Read more
*Apple* Retail - Multiple Positions - Apple...
SalesSpecialist - Retail Customer Service and SalesTransform Apple Store visitors into loyal Apple customers. When customers enter the store, you're also the Read more
Senior Payments Architect - *Apple* Pay - A...
Changing the world is all in a day's work at Apple . If you love innovation, here's your chance to make a career of it. You'll work hard. But the job comes with more Read more
Frameworks Engineering Manager, *Apple* Wat...
Frameworks Engineering Manager, Apple Watch Job Number: 41632321 Santa Clara Valley, California, United States Posted: Jun. 15, 2017 Weekly Hours: 40.00 Job Summary Read more
Manager, *Apple* Media Products - Apple Inc...
Job Summary The Apple Media Products Discovery, Fraud and Abuse team is responsible for protecting the integrity of Apple services. As a manager of the team, you Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.