M3MILESTONE THREE

DAVID KROFELHCI 598X | IOWA STATE UNIVERSITY

SPRING 2013

bikeBUILDER

2

CONTENTS

1. SUMMARY ............................................................................................................................................................... 3

2. REQUIREMENTS ..................................................................................................................................................... 3

3. DESIGN SPACE ......................................................................................................................................................... 5

3.1 Design Tradeoffs ................................................................................................................................................53.1.1 High Cognitive Load vs Low Cognitive Load ..........................................................................................53.1.2 Usability vs Functionality ......................................................................................................................53.1.3 Aesthetics vs Function ..........................................................................................................................53.1.4 Unlabeled Graphics vs Labeled Graphics ..............................................................................................5

3.2 Harder Requirements to Support .....................................................................................................................63.2.1 The Fitting System .................................................................................................................................63.2.2 User Knowledge-Base ...........................................................................................................................63.2.3 Product Reviews ....................................................................................................................................6

4. THE DESIGN ............................................................................................................................................................. 6

4.1 Accessing BikeBuilder .......................................................................................................................................7

4.2 The Build Baseline & Management Center ......................................................................................................74.2.1 Start New Build (Path 1) ........................................................................................................................74.2.2 Saved Builds list (Path 2) .......................................................................................................................8

4.3 The Build Configuration & Information Center ...............................................................................................84.3.1 Title Bar .................................................................................................................................................94.3.2 Component Category List ......................................................................................................................94.3.3 Manufacturer’s Product Gallery ...........................................................................................................94.3.4 Selected-Product Information Guide ....................................................................................................94.3.5 Build Information Panel - Progress, Summary & Saved Builds .............................................................9

4.4 Screen Overlays ...............................................................................................................................................10

4.5 Sketches ...........................................................................................................................................................10

4.6 User Scenarios .................................................................................................................................................154.6.1 User Scenario 1: First Custom Build using BikeBuilder .......................................................................154.6.2 User Scenario 2: Duplicating an Existing Build ....................................................................................15

5. FUTURE TECHNOLOGIES & SOCIAL IMPLICATIONS .................................................................................... 15

5.1 Future Technologies ........................................................................................................................................15

5.2 Social Implications ..........................................................................................................................................16

6. REFERENCES .......................................................................................................................................................... 16

3

1. SUMMARY

The BikeBuilder system is a web-based tool that utilizes a step-by-step process to guide the user through picking the components necessary to build a custom bike. The system provides a robust set of tools that allows the user to name and save builds, edit saved builds, compare builds, track build progress, seek fitting advice, browse through component lists tailored for the type of bike being built, choose the components necessary to complete a build, ask questions build-related questions, and search a user-contributed knowledge base.

The bike building process typically involves seeking assistance from a local bike shop or spending a significant amount of time online to gain the necessary knowledge required to successfully complete a custom build. Online bike stores carry an extensive range of cycling components, but generally provide no assistance in identifying component compatibility or necessity. While these issues can be alleviated by making an effort to educate oneself, the time commitment can become too overwhelming and may deter some cyclists from ever attempting to build a custom bike on their own.

The BikeBuilder system aims to provide an online tool that is feature-rich, enjoyable to use, and satisfies the needs of those building a custom bike who are more interested in riding than spending time online.

2. REQUIREMENTS

The User Needs and System Requirements are outlined in the table below (pages 3-4).

USER NEED SYSTEM REQUIREMENT

The user needs to be able to choose the type of bike to build.

The system shall provide two types of bikes to choose from: road or mountain.

When building a mountain bike, the user should be able to choose the type of frame (suspension type).

The system shall provide two frames choices: hardtail or full suspension.

If the user doesn’t understand the differences be-tween suspension systems, a detailed explanation should be available.

The system shall provide a popup overlay that explains the technical differences in suspension systems.

The user needs to be able to choose the wheel size for their bike.

The system shall provide 3 choices in wheel sizes: 26”, 650b (27.5”), and 29”.

If the user doesn’t understand the differences between wheel sizes, a detailed explanation should be available.

The system shall provide a popup overlay that explains the technical differences between wheel sizes.

The user needs a way to determine what size compo-nents they should choose.

The system shall provide a link to a separate fit sys-tem that will help the user determine proper sizing for components.

The user needs a way to get answers to questions that commonly arise when building a custom bike.

The system shall provide an indexed searchable knowledge base that contains answers to technical questions that past users have asked. This database will include general bicycle information as well.

Table continued on next page...

4

USER NEED SYSTEM REQUIREMENT

The user needs an organized, easy way to get informa-tion on each available component.

The system shall provide detailed textual and photo-graphic information for available components.

The user needs to be able to select a component to add to their build list.

The system shall provide a select button that chooses the component and moves it to the Build Summary list.

The user needs to be able to change items in the build list. The system shall allow for editing of the Build Summary List.

The user needs to be able to choose the size of com-ponents (where applicable).

The system shall list available sizes to choose from when component sizing options are available.

The user needs to be able to choose component color. The system shall list available colors to choose from when component color options are available

The user needs to be able to save their progress. The system shall use persistent cookies to save a user’s progress whenever a change is made to their build.

The user needs to be able to edit a previously started bike build.

The system shall display previous complete or incom-plete bike builds when returning to BikeBuilder at a later time. Clicking on the name of a previous build will open the build.

The user needs to be able to remove unwanted bike builds from the build list.

The system shall provide the option to delete any bike build that the user chooses.

The user needs to be able to save multiple builds. The system shall allow for multiple builds to be saved.

The user needs to be able to name their builds. The system shall provide a method for naming bike builds when creating a new build.

The user needs to be able to compare multiple builds. The system shall allow for side by side build compari-sons of up to 3 builds in a popup overlay.

The user needs to be able to ask the retailer product questions.

The system shall provide a form for asking product-related questions. The form will contain a field for user name, email, and question.

The user needs to be able to purchase the compo-nents in their Build Summary List.

The system shall provide a button that moves items in the Build Summary List into a shopping cart.

5

3. DESIGN SPACE

3.1 Design Tradeoffs

3.1.1 High Cognitive Load vs Low Cognitive LoadAll queried users stated that a system that was overly simple may be perceived as being less useful than a more complex system. Users felt that a “simple” tool may trivialize the bike building process and result in deterring more experienced riders from using the tool. What exactly did the users mean by “simple”? They explained that a “simple” tool is one that is not only limited on features but also limits the amount of information presented on screen at any one time. Access to most (if not all) of the BikeBuilder features at any time during the build process was considered to be a highly desirable attribute of the system. However, designing the system in this manner will undoubtedly require more cognitive load as a user will be presented with several layers of information simultaneously.

3.1.2 Usability vs FunctionalityUsers generally prefer feature-rich products and are initially willing to surrender usability in favor of excessive functionality (Sutcliffe, 2002). However, after using such products user mindsets reveal that usability is equally important as functionality. Enough features need to be offered to generate user interest in the product, while avoiding a featureset that bloats the product, resulting in compromised usability. A balance between usability and functionality is vital to the success of BikeBuilder.

3.1.3 Aesthetics vs FunctionAn interface that is too beautiful may be distracting and interfere with the product’s core function, ultimately resulting in a lack of user focus. As such, a balanced level of aesthetics should be maintained to help improve the users’ initial perception of the product and increase the likelihood of repeat use (given that the product is well designed aside from its aesthetic qualities). When elements such performance, seamless interaction, and familiarity are combined with a clean structure and layout, the end product can result in achieving a high level of usability and beauty (Butnaru, 2013).

3.1.4 Unlabeled Graphics vs Labeled GraphicsThe BikeBuilder system is intended to be a tool that is fun and easy to use, while providing a visually rich experience for the user. Since product descriptions and photos will require a large portion of the screen real estate within the system, icons alone were to be used extensively to represent component categories. Users have been shown to think that the use of icons results in an easier-to-use application (Wiedenbeck, 1999), but icons generally only work well when they represent universally known items, such as those depicting a trash can, printer, or shopping cart. Several component categories within BikeBuilder would require abstract or difficult to identify images to represent their corresponding content. An icon containing the image of a bicycle frame or wheel would be easy to identify. However, smaller parts, such as headsets or cable housings, would be difficult to identify with just an icon.

Research findings from investigational studies of icon usage with and without text labels led to the adoption of a new default display in 1997 in Microsoft’s Outlook Express to include icons with text labels (Anderson, 2010). In keeping accordance with this practice, any icon usage in BikeBuilder will always be accompanied by text labels. The combination of icons with text labels will require more on-screen space, but should allow for quicker recognition of component categories and help maintain an element of visual interest.

6

3.2 Harder Requirements to SupportThe system requirements gathered during user interviews were compiled into a rather lengthy list of features/functions. Several functions were suggested as being “nice to have, but not absolutely necessary”. These functions, along with several that were suggested by single users, are questionable in regards to whether they are vital to making BikeBuilder a useful tool. Querying a larger user pool would prove beneficial in helping to establish a more cohesive set of commonly requested features.

3.2.1 The Fitting SystemOne feature that all users suggested was the inclusion of a fitting system. A fitting system is an extremely useful tool for determining proper sizing of several components. An ill fitting bike contributes to rider discomfort and loss of efficiency, resulting in a riding experience that is not enjoyable. Frame size, stem length, handlebar width, crank length, and even wheel size to some degree, are vitally important factors that must be addressed in order to build a bike that properly fits the rider.

Although the inclusion of a fit system within BikeBuilder is a great idea, the accuracy of such a system is highly dependent on the self-measurements that the user would be responsible for attaining. These self-measurements would need to be entered into another system that calculated the measurements and provided the results/recommendations to the user. Results from this type of system are size recommendations that are marginally accurate and should only be considered as generalized estimates. A professional fitting service provided by a local bike shop uses specialized fitting equipment and several processes that a do-it-yourself fitting simply cannot provide.

3.2.2 User Knowledge-BaseWhen building a bike, several questions may arise that pertain to the advantages of one type of system over another. For example, the braking systems on today’s mountain bikes are generally of the disc type. Disc brakes are offered in two types of sub-systems: hydraulic (liquid-actuated) or mechanical (cable-actuated). Each has its own advantages/disadvantages, but for the lesser-informed cyclist, how would they know that? The User Knowledge-Base would be used as a means for seeking answers to common questions that other users have asked in the past. In order to make this feature functional, a database of questions and answers would need to be built. Such a task would require a significant amount of time and resources.

3.2.3 Product ReviewsQueried users explained that they frequently read reviews for many types of products and rely on them regularly to help make purchasing decisions. As such, BikeBuilder will provide reviews on all products offered within the system. This feature may be difficult to implement due to the sourcing of the actual product reviews. Ideally, the reviews would be sourced from the host site’s own database of user-submitted reviews. However, what happens if the host site does not collect product reviews? The answer may be to get reviews from another online bike shop or even better, a biking forum. Moreover, adding this functionality would require significant resources and cooperation with an outside 3rd party.

4. THE DESIGN

Although the task of building a custom bike may appear to be a straightforward process, several decisions early on in the process play critical roles in determining proper component choices and compatibility with each other. In its full implementation, BikeBuilder would be able to be used for building either a road or mountain bike. For the sake of this project only the mountain biking aspect of the tool will be implemented. A non-functioning road bike option will be present in the system’s design to demonstrate how it would fit into a complete system.

7

The system is comprised of two sections, a Build Baseline & Management Center and a Build Configuration & Information Center. The Build Baseline & Management Center serves as the opening screen for BikeBuilder where users may start new bike builds or access previously saved builds. The Build Configuration & Information Center serves as the heart of BikeBuilder and is where the component choosing process is performed.

4.1 Accessing BikeBuilderUser access to BikeBuilder is provided by a link placed on the hosting website’s header menu, allowing access to the tool from anywhere within the host site.

4.2 The Build Baseline & Management CenterThis section of BikeBuilder is primary text-based and is the first screen a user encounters after launching BikeBuilder. The user is presented with two options or paths from which they may choose to proceed.

4.2.1 Start New Build (Path 1)The first path would allow the user to start a new bike build which entails a progression through several steps that are necessary to establish a baseline bike. The baseline bike is used as a reference for the system for determining the products to be offered in each component category. In other words, if the user was building a mountain bike, all road bike components would be removed from each component category, thereby making it impossible to mistakenly pick road bike components for the mountain bike build. The baseline steps include:

• Start New Build

• Name Build - naming will allow the bike build to be viewed/edited at a later time. Upon naming the build, the build name will appear in the Saved Build list. Users felt this was important to help identify builds.

• Choose type of bike: ROAD or MOUNTAIN

□ If choosing ROAD, the baseline process will be complete

• If choosing MOUNTAIN, additional steps are required:

□ Choose frame type (Suspension system): Hardtail (HT) or Full-Suspension (FS)

□ Choose Wheel Size: 26”, 27.5” (650b), or 29”

After completion of the baseline, the user will be presented with a baseline summary. This short summary is used as a stopping point where previous choices will be confirmed before entering the heart of BikeBuilder. Three options will be offered to the user:

1. CONTINUE - choosing CONTINUE will advance the user to the next portion of the bike building process.

2. CANCEL - choosing CANCEL will delete all baseline choices, remove a saved (named) build from the Saved Builds list, and restart the baseline process from the beginning.

3. START OVER - choosing START OVER will delete all baseline choices, but the saved (named) build will remain in the Saved Build list. This could be useful when creating several builds that use an identical baseline as a starting point - see “duplicate builds” in Saved Builds list in section 4.2.2 for more information.

8

4.2.2 Saved Builds list (Path 2)The Build Baseline & Management Center also serves as a gateway to access previously saved bike builds via the Saved Builds list. The list can be sorted in several ways: by activity (road first or mountain first), by build date (newest-oldest or oldest-newest), and by price (low-high or high-low). When sorting by activity, builds are sub-sorted by build date (newest first). Default list sorting is by build date (newest first).

The Saved Builds list also allows the user to:

• choose up to 3 builds to compare

• delete builds

• duplicate builds - a user may want to change portions of several similar builds to see how these changes affect price or weight

• rename builds

4.3 The Build Configuration & Information CenterThis section of BikeBuilder is where the majority of the build process will be completed. A quick visual scan of the screen’s layout reveals a structure that is broken down into 5 distinct areas of information (see Figure 1). As a result of the amount of information being made available on-screen, this portion of BikeBuilder may require

Figure 1. Structural division of the Build Configuration & Information Center. Information flow in this section of BikeBuilder is indicated by the red arrows.

Title Bar

ComponentCategory

List

Manufacturer’s Product Gallery

Selected Product Information

Build InformationCenter

9

a heavy cognitive load. In order to reduce this cognitive load, unnecessary steps in the build process were eliminated (identified during sketching), related items were grouped together (i.e. components, build lists, etc), and consistent naming and labeling of items will be maintained throughout BikeBuilder (Matz, 2012). As a result of the efforts to reduce cognitive load, it is believed that users will quickly become familiar with how to accomplish tasks in this portion of BikeBuilder.

4.3.1 Title BarThe Title Bar block runs horizontally across the top of the entire application. A link is provided on the left side of the Title Bar to enable the user to start over. The BikeBuilder name/logo is centered in the Title Bar space and on the right side there is a search field for the Knowledge Base, a link to the Fit System, and a link that opens a form that allows the user to submit a question regarding their build.

4.3.2 Component Category ListThis block runs vertically along the left side of the application. The component categories are listed within this space and when clicked on expand to reveal the available manufacturers for the chosen component category. The items presented in the Manufacturer’s Product Gallery (see section 4.3.3) are derived from selections made in the Component Category List. Upon expanding a component category, all corresponding components will be listed in the Manufacturer’s Product Gallery. The default behavior is for the system to display all category products in the Manufacturer’s Product Gallery. This can be overridden by unchecking boxes located to the left of each manufacturer’s name (see Figure 2).

4.3.3 Manufacturer’s Product GalleryThis block is positioned in the middle-top portion of the Build Configuration & Information Center. Products in this space are displayed showing a small photo of the item with the manufacturer’s name, product name, and price listed beneath the image (see Figure 3). Clicking on an item will allow the user to view more detailed product information in the Selected-Product Information Guide.

4.3.4 Selected-Product Information GuideThis block is positioned in the lower-middle portion of the Build Configuration & Information Center directly below the Manufacturer’s Product Gallery. This part of the system provides the user with detailed product information in the form of a photo gallery, a product overview, detailed product specifications, and user reviews that are parsed from popular biking forums.

4.3.5 Build Information Panel - Progress, Summary & Saved BuildsAs the user progresses through BikeBuilder, all component choices will be detailed in the Build Information Panel. The Build Information Panel provides the user with information regarding the progress level of their current build, a Build Summary list detailing their component choices, and a point of access to saved builds. After choosing all the components, the user will review the Build Summary list and make component changes if necessary. If the user is satisfied with their choices, they may submit the build to the host site’s shopping cart.

Figure 2. Enlarged view of the contents found in the Component Category List. Check boxes are used to filter the display of manufacturers listed in the Manufacturer’s Product Gallery.

FRAMES

BMCEllsworthIbisNinerPivotSanta CruzYeti

FORKS

-

BRAKES

DERAILEURS (Front)

DERAILEURS (Rear)

CRANKS

+++++

10

A button beneath the Build Summary list will allow access to the Saved Builds list. Clicking on this button will open a popup window overlaying the BikeBuilder that will contain a Saved Builds list that retains the same format and functions as the list found on the Build Baseline & Management Center. However, it should be noted that the user will NOT return to the Saved Builds list found on the Build Baseline & Management Center.

4.4 Screen OverlaysSeveral links in BikeBuilder open screens that overlay on top of the application. These include the following:

• Knowledge Base

• Fit System

• Question Form

• Save Builds list (located in the Build Information Panel section of the Build Baseline & Management Center)

• Photo gallery located in the Selected-Product Information Guide

Overlays such as these are common on modern websites today and are frequently used when displaying expanded photo galleries. Each screen overlay can be closed by clicking outside the overlay’s main content or clicking on the “X” in the upper right corner of the overlay. It should be noted that these overlays are not pop-up windows that would be blocked by a browser’s pop-up blocker. Rather, they are a combination of an opaque information-containing box centered on top of a larger dark-colored semi-transparent background that overlays the entire BikeBuilder application.

4.5 SketchesAccording to Warfel (2009), the goal of sketching is to generate numerous ideas as quickly as possible. With this mind, a series of pencil sketches were made during design brainstorming. This process provided a method to

NinerOne 9 Frame

$899

NinerAir 9 Frame

$849

NinerXXXXXX Frame

$749

NinerXXXXXX Frame

$829

NinerJet 9 Frame

$1849

NinerRip 9 Frame

$1849

NinerWFO 9 Frame

$1899

NinerAir 9 Carbon Frame

$1899

Figure 3. Manufacturer’s Product Gallery displaying Niner’s frame product line.

11

Figure 4. Early sketches of the Build Baseline & Management Center.

12

Figure 5. The prototype for the Build Baseline & Management Center will be based on this design.

Figure 6. Rough sketch of the Compare Builds overlay.

13

Figure 8. Two variants of the Selected-Product Information Guide.

Figure 7. Early design of the Selected-Product Information Guide. Horizontally scrolling bar near the top of the sketch was eliminated in later designs.

14

Figure 9. Sketches of elements from the Build Information Center.

Figure 10. Sketch of the design that will be used as the basis for the prototype of the Build Configuration & Information Center.

15

visually communicate thoughts and ideas for BikeBuilder and resulted in the emergence of several useful concepts. Elements from each concept were later combined to form the design that I plan to move forward with.

Prior to sketching, I was confident that I had the design already worked out in my head. Unbeknownst to me, I had subscribed to two myths that Bill Buxton (2007) believes are commonly practiced in user experience design today... “That we know what we want at the start of a project”, and “That we know enough to start building it.”

4.6 User Scenarios

4.6.1 User Scenario 1: First Custom Build using BikeBuilderJohn has just returned from his local bike shop where he was looking at the new 2013 mountain bikes that had just arrived. He’s interested in a few models, but each of them has components that he would most likely swap out soon after purchasing the bike. John’s not comfortable with the idea of having to spend more money after the initial purchase to get his bike set up to his liking. John explained this concern to his friend Matt, who is also a mountain biker. Matt told John about an online custom bike building tool that he recently found that was tied into an online bike shop which offered competitive prices. Although John had never built a custom bike, the idea was intriguing. After John’s children went to sleep, he sat down at his computer and navigated to the online bike shop that Matt had told him about earlier in the day. A link to BikeBuilder was prominently displayed on the website’s home page. John clicked on the link and launched the application. The first thing John noticed on the opening BikeBuilder page was the Start New Build button. He clicked on the button and began the process of naming his build, picking the type of bike to build, picking the suspension system, and picking the wheel size. Upon completing the first few wizard-driven steps, John entered a second section of BikeBuilder where he quickly chose all of the components for his new build.

4.6.2 User Scenario 2: Duplicating an Existing BuildDale is in the process of building a custom mountain bike and used BikeBuilder to create two similarly-equipped bikes that have been saved in the system. Dale decides that he wants to create one more build that is similar to the last build he created, but wants to change a few of the components. Instead of creating a new build using the Start New Build option, Dale locates his previous build in the Saved Builds list and creates a duplicate of that build using the build editing tools. He renames the duplicate build and proceeds to make the component changes on this third build.

5. FUTURE TECHNOLOGIES & SOCIAL IMPLICATIONS

5.1 Future TechnologiesThe design of BikeBuilder isn’t heavily reliant on any technology that doesn’t currently exist today. However, since BikeBuilder is essentially a portion of a website and not a native application, its future development is dependent on advances in internet technologies.

As HTML5 gains wider acceptance and use, it is likely to become a valuable tool in the further development of BikeBuilder. The shorter development times and cheaper development costs associated with HTML5 (Rashid, 2012) will help BikeBuilder keep pace with advances in internet trends and allow for improved efficiency in updating the system’s content. HTML5’s addition of a new video tag would also make it easier to add video content to future versions of BikeBuilder and would no longer require the use of Adobe’s resource-hungry Flash browser plugin (Chartier, 2011).

16

The Worldwide Web Consortium (W3C) has declared that HTML5 is “feature complete”, but it’s not slated to become an official web standard until 2014 (Goldman, 2012). Although compatibility issues with older browsers have slowed the widespread adoption of HTML5, the W3C reports that about 63% of web and app developers are using HTML5 to create new websites and software (Goldman, 2012).

Recent research from Strategy Analytics suggests that 1 billion HTML5-capable phones will be sold in 2013, while ABI Research believes that 2.1 billion of these devices will be in the hands of consumers by 2016 (Perez, 2011). Gartner, Inc., the world’s leading information technology research company, predicts that by 2014 mobile devices will overtake personal computer’s as the most common method of accessing information on the internet (Thibodeau, 2012). Personal computer sales in 2012 have declined 1.2%, marking the first time in over a decade that PC sales have not remained steady or increased (Stegeman, 2012). With continual improvements in mobile technology and the increasing popularity of tablets such as Apple’s iPad, any future development of BikeBuilder would need to involve serious consideration for these types of devices. Despite these findings, I believe a traditional PC will still provide the best experience while using BikeBuilder.

5.2 Social ImplicationsAs with any e-commerce-related tool, the use of BikeBuilder is not without any social ramifications. On the positive side, the online availability of this tool allows for use at any time of the day, sparring its users from being bound by the business hours of a local brick and mortar store. Interruptions in social relationships with friends or family could be reduced or avoided as a result of the time savings made possible by removing the need to travel to a physical store. On the negative side, the value of human relationship is lost when purchasing goods online. Some consumers prefer the personal attention they may receive when shopping locally, especially in instances where a relationship has been forged with the retailer. The purchase of a custom bike is typically an expensive endeavor and one may feel more comfortable making decisions about their purchase when guidance is provided in a face to face manner. Also, trust is easier to build when physically interacting with another human being than when dealing with a faceless entity.

Since BikeBuilder is an extension of an online store, sensitive customer information could be jeopardized as a result of poor site security or unscrupulous actions taken by the site’s owner. However, it should be noted that a user account is not needed to use BikeBuilder. As such, the system does not collect any sensitive user information.

6. REFERENCES

Anderson, C. (2010, December 31). GUI Design: Icons or Text? | GUI Journal. GUI Journal. Retrieved February 19, 2013, from http://guijournal.com/2010/12/icons-or-text/

Buxton, B. (2007). In Sketching user experiences: Getting the design right and the right design (p. 77). San Francisco: Morgan Kaufmann.

Butnaru, C. (2013, January 18). Functional Beauty and User Experience | UX Magazine. UX Magazine | Defining and Informing the Complex Field of User Experience (UX). Retrieved February 15, 2013, from http://uxmag.com/articles/functional-beauty-and-user-experience

Goldman, D. (2012, December 17). HTML5: The future of the Web is finally here - Dec. 17, 2012. CNNMoney - Business, financial and personal finance news. Retrieved February 15, 2013, from http://money.cnn.com/2012/12/17/technology/html5/index.html

17

Perez, S. (2011, November 7). Forecast: 1 Billion HTML5 Phones By 2013 | TechCrunch. TechCrunch. Retrieved February 15, 2013, from http://techcrunch.com/2011/12/07/forecast-1-billion-html5-phones-by-2013/

Rashid, F. Y. (2012, December 9). What to Expect from HTML5 in 2013 | the HTML5 Center. The HTML5 Center by SourceForge and Microsoft. Retrieved February 15, 2013, from http://html5center.sourceforge.net/blog/What-to-Expect-from-HTML5-in-2013

Stegeman, J. (2012, October 11). PC Sales To Decline In 2012. The Inquisitr. Retrieved February 15, 2013, from http://www.inquisitr.com/360161/pc-sales-to-decline-in-2012/

Sutcliffe, A. (2002). User-centered requirements engineering. London: Springer.

Syed, F. (2012, February 21). HTML5: An open standard to rule them all? Network World. Retrieved February 15, 2013, from http://www.networkworld.com/news/tech/2012/022112-html5-256379.html

Thibodeau, P. (2012, October 23). Gartner’s Top 10 tech trends for 2013. Computerworld. Retrieved February 15, 2013, from http://www.computerworld.com/s/article/9232800/Gartner_s_Top_10_tech_trends_for_2013

Warfel, T. Z. (2009). In Prototyping: A practitioner’s guide (p. 31). Brooklyn, N.Y: Rosenfeld Media.

Wiedenbeck, S. (1999). The use of icons and labels in an end user application program: An empirical study of learning and retention. Behaviour & Information Technology, 18(2), 68-82.