Microsoft vs. Apple: User Interface Decisions

This post is an old research paper I wrote for Indiana Wesleyan University.

Much of the news in the Information Technology field has focused on Microsoft's upcoming operating system, Windows 8. Inevitably, many comparisons are being made between Windows 8 and Apple's most recent release of the Mac OS, which is code-named "Mountain Lion." Both desktop operating systems borrow heavily from their mobile counterparts. However, Microsoft's decision to reimagine Windows from its foundations, discarding the desktop paradigm of computing, is fundamentally risky and has the potential to alienate and frustrate long-time Windows users. Apple's decision to integrate features from its mobile operating system without sacrificing the familiar desktop interface is a less risky move. Although both decisions have the same goal of bridging the gap between the desktop and mobile interfaces, they are indicative of the cultural differences between the two companies and have the potential to shape their future for years to come.

Windows 8

From the moment you log in, it is evident that Windows 8 is a complete reimagining from its predecessors. "Instead of the familiar Start menu, taskbar, and Windows Explorer, you get the Start screen, which consists of square and rectangular icons for your apps called Live Tiles" (Mediati, 2012). The Start screen displays every application installed on the computer by default, but users can choose what does or does not appear. Users can pin favorite Web sites or contacts from their address book to the Start screen to further customize their experience. However, that does not mean the desktop is gone. "Windows 8 will run traditional desktop-style Windows applications too, and it will do so in a desktop environment that resembles the layout of Windows 7" (Mediati, 2012).

Microsoft built Windows 8 with cloud computing in mind. Microsoft bundles its OneDrive service with Windows 8, just as Apple bundles its iCloud service with Mountain Lion. Microsoft's OneDrive service aims to provide users with access to all of their applications and files, thus providing a consistent user experience, regardless of what machine they happen to be logged into. "A big difference between SkyDrive and iCloud is that it offers Web access to any files you've stored on it," meaning users can access their files from any Web browser. Additionally, many third-party applications for Windows 8 can make use of OneDrive to store and retrieve files (Muchmore, 2012).

Galen Gruman of InfoWorld.com summed up his thoughts on the user experience in Windows 8 in his article "Deathmatch: Windows 8 vs. OS X Mountain Lion:"

Ultimately, you're switching between two different computers that share a file system and a few core services, and each computer is optimized for a different set of input methods. It would have been better to leave Metro for tablets and Windows 7 for laptops and desktop PCs, and slowly merged the UIs as Apple is doing with OS X and iOS. For most users, Windows 8 will be a confounding mess. (2012)

Microsoft's decision to merge the desktop and mobile interfaces in Windows 8 and create one operating system for multiple devices demonstrates the company’s need and desire to remain relevant in the an era where users are increasingly reliant on smart phones and tablets to remain connected. In this "post-PC" era, the desktop is no longer the primary method of computing for the average end user. Microsoft’s decision to go "all in" with Windows 8 could spur a new period of innovation at the company or drive users away, causing the company to enter a period of decline.

Mac OS X "Mountain Lion"

Apple has taken a different approach with Mountain Lion. "At its heart, Mac OS X is still an operating system designed for desktops and laptops." At first glance, it does not look like the OS X desktop has changed. However, Mountain Lion does have a similar feature to Windows 8's Start screen: the Launchpad. When Launchpad is opened, it displays an iPad-like grid of icons for your programs, making it easier to locate and access them. However, despite Launchpad's iOS roots, Mountain Lion looks and feels like a Mac, not an iOS device (Mediati, 2012).

Like Microsoft, Apple built Mountain Lion with cloud computing in mind. Apple built its iCloud service into Mountain Lion. "When you sign into your Apple account on a Mountain Lion Mac, all your mail settings, contacts, Safari bookmarks, messages, iTunes backups and other features will be synced via iCloud. And when you launch the App Store, all the apps you purchased earlier through the App Store are available for downloading and installation" (Muchmore, 2012). Like Microsoft, Apple built cloud storage into iCloud. However, users cannot access these files via a Web browser.

"Apple defined the graphical user interface as we know it today, and despite 28 years of changes, the core metaphors remain unchanged. That consistency makes it easy to use each new version of OS X, and Mountain Lion is no exception" (Gruman, 2012). However, Mountain Lion has one user interface flaw that undermines the ease of use: "there are now three distinct UIs and services for saving files: one for traditional apps, one for Versions-enabled apps, and now one for iCloud Documents-compatible apps." This can be confusing to long-time and new Mac OS users.

Apple brings several features from its iOS operating system to the Mac OS in a natural and incremental way. Unlike Microsoft, Apple does not risk alienating long-time Mac users with the changes to the operating system. Apple has taken a much more conservative approach to merging its desktop and mobile operating systems.

Conclusion

Both Microsoft and Apple have the same goal of bridging the gap between the desktop and mobile interfaces, but the decision to take differing approaches are indicative of the cultural differences between the two companies. Microsoft has taken the riskier approach of reimagining Windows from its foundations, which could frustrate the company's user base. Apple has taken a more conservative approach, refining the Mac OS while adding features from iOS. The main difference between the two approaches is how the designs reflect the end user experience. Apple's approach to consistency demonstrates the company's willingness to keep the existing user base happy while adding features those same users like about the iOS operating system. Microsoft is seemingly ignoring the existing user base and introducing a new learning curve. Only time will tell which approach is the correct one.

References

Gruman, G. Deathmatch: Windows 8 vs. OS X Mountain Lion. InfoWorld.com. Retrieved from http://www.infoworld.com/d/microsoft-windows/deathmatch-windows-8-vs-os-x- mountain-lion-200175?page=0,0.

Mediati, N. Windows 8 vs. Mountain Lion: which OS succeeds at bringing mobile to the desktop? PCWorld.com. Retrieved from http://www.pcworld.com/article/252499/windows_8_vs_mountain_lion_which_os_ succeeds_at_bringing_mobile_to_the_desktop_.html.

Muchmore, M. Windows 8 vs. OS X Mountain Lion: Feature by Feature. PCMag.com. Retrieved from http://www.pcmag.com/slideshow/story/265435/windows-8-vs-os-x- mountain-lion-feature-by-feature.

Software Issues and their Impact

Describe at least two software issues (open-source, upgrades, software bugs, copyrights/licenses, global support) and how these issues impact users and organizations.

Two issues that immediately caught my attention were software bugs and freeware/open-source software.

Software defects prevent software from accomplishing what it was designed to do. These defects can result in performance issues, data loss or data integrity issues, or incompatibilities. Software defects are an inevitable part of development. No software will ship one-hundred percent bug-free. The wide range of different combinations of applications, hardware, et cetera can lead to defects being discovered that would otherwise not be. Software bugs can be a source of many problems for companies as they could result in loss data, lost productivity, and increased costs to fix or work around these defects.

Software defects often go hand-in-hand with upgrades. Software upgrades have benefits and drawbacks. The most immediate benefit to upgrading is the ability to use the latest features and newest technology. On the other hand, users may need to learn a new way of working or navigating the software, especially in the case of Windows 8. Upgrading to any new version right away can also expose the user to defects that the manufacturer might not have found. Many companies have policies in place that delay upgrading until the software manufacturer releases a service pack or "point-one" version of the software.

Freeware, free software, and open-source software can be a source of confusion to many end users. Freeware is software that is distributed at no cost. However, users may be – and often are – bound by licensing restrictions, such as not being able to use the software for commercial or "for-profit" purposes. Such licensing restrictions often discourage businesses from using this software, no matter how beneficial it might be.

Open-source software, as its name implies, is software that is distributed along with its source code. This allows users to study or modify the code. Users can also redistribute the code or companies can use part of the code in its own software, as specified in the BSD and MIT licenses. Open-source software is typically distributed for free or at minimal cost. However, open-source software may not come with support guarantees and can carry a higher total cost of ownership (TCO). Additionally, some open-source software – typically Linux-based software – is not available or not compatible with Microsoft Windows. I should point out that open-source software is not always governed by the GNU General Public License (GPL). There are other licensing schemas available, such as the BSD license and the MIT license, which I mentioned above.

Free software – also called libre software – is software than can be studied, modified, and used without the typical licensing restrictions. Free software is typically licensed under the GNU General Public License (GPL). The biggest drawback to using the GPL is the licensing itself. If a software company includes GPL-licensed code in a software product, that company is legally bound to license their software product under the GPL. In some cases, simply including a copy of GPL-licensed code on the same media – even if it is not part of their software – may result in legal issues. This restriction alone can discourage companies from using free software.

E-Waste

What concerns have been raised over e-waste?

There have been many concerns raised over electronic waste (e-waste). The main concern involves the use of heavy metals and materials like mercury, lead, and PVC plastic. When electronics products are thrown away, these materials can leach into the ground and cause serious environmental issues over time. Sometimes non-salvageable components of these products are burned, especially in third-world countries. This creates toxic smoke which enters our atmosphere and causes illnesses in the short term and long-term environmental effects. Another concern is the use of child labor in dismantling used electronics and manufacturing new electronics products.

One of the biggest – perhaps the biggest – contributor to e-waste is the idea of "planned obsolescence." Planned obsolescence involves deliberately manufacturing a product to become obsolete after a period of time. Many critics use Apple as an example, but all electronics manufacturers are guilty of this at one point or another. I’ve pasted a link to the Wikipedia article, which gives an excellent summary of the concept. There are some excellent links near the bottom of the article to resources that go into greater detail.

Another concern – not specifically related to e-waste – is the amount of other waste generated as a side effect. For example, most electronics devices use batteries of some sort. Batteries contain toxic materials such a cadmium, lithium, and alkaline. In addition, there is the packaging. Many companies have taken steps to reduce the amount of packaging, but the sheer volume of electronics devices purchased today nearly negates that effort.

What actions can electronics manufacturers take to address the e-waste problem?

Many manufacturers – such as Nokia and Apple – offer "take-back" or "buy-back" programs that offer consumers the opportunity to recycle their old devices when they are no longer needed. More manufactures can adopt similar programs or provide similar incentives to their customers. Many manufacturers could also discard the notion of "planned obsolescence," and build products that are meant to last longer. Many manufacturers are also designing their products with less amounts of hazardous material and making them easily recyclable.

Manufacturers aren’t the only organizations that can take action. Travis mentioned in his thread about local communities organizing a "recycling day" that gives residents another option to recycle their old electronics. However, these events are only held a few times a year. Major retailers can also contribute. Best Buy already offers a "buy back" program. Imagine how much e-waste could be recycled if all Wal-Marts across the country offered a recycling or "take-back" program in their stores!

What laws, if any, do you think are necessary to address this problem? Why?

I think there should be laws to provide incentives for companies to manufacture their products with fewer hazardous materials. There could also be laws to provide incentives to consumers that recycle their old electronics. The government has offered such incentives in the past to taxpayers who have made their homes energy-efficient. Why not expand those incentives to encourage recycling electronics products?

Make or Buy?

What are some advantages and disadvantages of purchasing versus developing software?

The main advantage to purchasing software versus developing it is the cost savings to design, develop, and test the software. If a company – or a consumer – purchases software, there is a reasonable expectation that it has been tested and functions the way the developer intends. However, this is not always the case. Conversely, no pre-packaged software ever does what every user wants. As a result, users have to change settings, add customization options, or resort to purchasing additional software to accomplish their goals.

Developing software has its advantages, too. If a company develops its software in-house, it can be sure the software meets expectations. One unexpected advantage is if the software benefits the company – and could benefit a company's customers – the company may be able to sell that software and realize an additional profit.

Another advantage to companies developing their own software is the concept of "dogfooding," where companies use their own product in production to demonstrate its capabilities.

As an aside, I think free and open-source software have an advantage over proprietary software when it comes to companies developing their own software. Companies can reap the benefits of having pre-packaged software, which saves on the development and design costs, and customize that software to fit their business processes.

What is important to include in the contract with a software developer?

Some important things to include in the contract with the software developer include:

1. Service and support – If my software does not function correctly under certain circumstances, or there is a bug discovered, what are the developer’s responsibilities? Should they make a fix available at no cost? What is the ideal response time for any support issues? How soon can I expect a resolution to any support issues? What would be the developer’s responsibility if any data loss or data integrity issues result through use of the software? What is considered an “inappropriate” use of the software or what would violate any licensing agreements?
2. Training – Will the software developer provide training or make any training available to the end users? Is the documentation on how the product is intended to function?
3. User Acceptance Testing or Trial periods – Does the software developer offer a trial of their software?
4. Is the software secure? It’s almost impossible to guarantee complete security as there will always be defects in the software and improvements in hacking methods. But does the developer respond to security concerns in a timely manner? Has the developer knowingly released the software with security issues?
5. How much does the software cost? This would include up-front and maintenance costs over the life of the software.

Leaving the Microsoft Ecosystem (Preview)

Inspired by this post from Brad Sams on Thurrott.com.

Shuttering the Microsoft Band/Health platform may be just the spur I need to exit the Windows ecosystem entirely, as I have been slowly leaving Windows behind. I've left the Lumia ICON on Verizon for a Nexus 6P on Project Fi and traded in my Surface for a Pixel C.

My Band has been refusing to charge, and neither Best Buy nor the nearest Microsoft Store have stock handy for a replacement. I've since bought a Fitbit Alta (and, later, a Charge 2) and resurrected an Asus ZenWatch for testing purposes.

The only remnants of Microsoft's ecosystem at this point are my desktop, personal laptop, and the few apps I still use on my phone.

When automation goes wrong

http://www.satisfice.com/blog/archives/559

This scenario came to pass for a co-worker and myself. Our attempts to automate some manual tests uncovered a configuration issue that resulted in test data being fed into the production environment. In this case, a patient, said patient's medical record, and a prescription order for a controlled substance – in this case Oxycodone – for said patient sent to a local Walgreen's pharmacy.

Another reason why automating tests at the GUI level is not as easy as it seems . . .

Microsoft Reader Redux

Courtesy of MSPowerUser by way of Paul Thurrott.

Microsoft has released an internal build for Windows 10 Mobile that shows off a new store for e-books. MSPowerUser stated that Microsoft "started building in features related to the Books store late last year" when ePub support was built into the Edge browser. However, Microsoft has been working on this for quite some time. In fact, Tom Warren of The Verge reported in 2014 that Microsoft was attempting to build an 'Xbox Reader' app. Also, Microsoft invested in Barnes & Noble's Nook business in 2013 amid rumors that the software giant would eventually purchase it. Until the deal fell through. In any case, this is long overdue and may give me incentive to return to Microsoft's ecosystem full time. Adding a book store gives me another reason to look forward to the upcoming Windows 10 Creators Update.

Technorati Tags: Microsoft,Windows 10 Insider Preview,Windows 10,Creators Update,Barnes and Noble,E-Books,E-Reader,ePub,Microsoft Edge

Looking ahead for Windows 10

Microsoft released build 15002 to its Insiders today, and it's a doozy. Among the changes are several improvements to the Edge browser and the Windows shell. Feel free to read the blog entry linked above. Also check out PC World's in-depth article and Paul Thurrott's impressions.

I'm not going to lie. This build has me looking forward to the upcoming Creators Update in the spring.

Technorati Tags: Windows 10 Insider Preview,Windows Insider Program,Windows 10,Creators Update