worldmate app final report - wordpress.com...produce an organised itinerary which will certainly...

WorldMate

Ahmad Uzair Bin Ahmad

Juanda

Universiti Teknologi Malaysia

SPACE, KL.

[email protected]

Azizi Bin Ali Aziz


SPACE, KL.

[email protected]

Ahmad Shamizan Bin Md Nor


SPACE, KL.

[email protected]

‘Afifah Binti Nasir


SPACE, KL.

[email protected]

Mohd Zaidi Bin A Samad


SPACE, KL.

[email protected]

ABSTRACT

In this paper, we describe the process of designing a mobile

application to assist travelers when travelling overseas and

even domestic. This is an overview of how we made design

choices, implemented those choices in various stages of

prototyping, and evaluated the usability of the application at

each step in the process.

Author Keywords

HCI; Human-Computer interaction; travelling; mobile

applications

ACM Classification Keywords

C.5.3:iPhone;

General Terms

Human Factors; Design;

INTRODUCTION

The WorldMate application was designed to make the task

of a traveler even easier. Most traveler choose to arrange or

organize their trip by their own. But most of the time they

will be ended doing them inefficiently. We wanted to tackle

the most important challenges that arise when travelling,

such as hotel booking, flight booking, limo reservation and

others. All you have to do is enter your various information

details (such as flight / hotel bookings, restaurant

reservations and tickets to events etc) and the app will

produce an organised itinerary which will certainly ease the

pressure off you and make for a more relaxed trip. It

couldn’t be easier This process was concerned with the user

interface design of the mobile application as opposed to the

back-end programming aspect of the application.

PROBLEM

We found that a common issue that we all shared was that

when organizing a trip especially overseas, is often an

inconvenient and frustrating task. Many people find it hard

to keep track of the itinerary of their trip, most of them

choose to use travel agencies and event tour guide to

manage their trip accordingly. If you are constantly

travelling, keeping tabs on where you suppose to be and

when can be quite tricky. If you do not fancy forking out

for a personal assistant to arrange your travel schedule. The

WorldMate application is a great replacement for a personal

assistant. It can also be frustrating to alert yourself of your

flight time, it gets even tricky when there are time changes

such as flight delays and others. We wanted to design an

application that addressed these various problems and made

the process of going on travelling a more convenient and

efficient one.

USERS

Our target users for this application was anyone who travel

and wants to better manage their trip itinerary or their time.

Our primary focus was targeting this application towards

tourist since they are new to the trip location. This apps

will prevent them from getting lost from their track, as well

as business traveler who are trying to plan the quickest and

most cost efficient business trip because they need to fulfill

their business schedule and avoid delays and related

problems that can ruin their business. Other than that there

are travel agencies. This is the most targeted user since they

are common and used to make money from other users. Our

mailto:[email protected]

personas ranged from age 20 to age 50, but our most

accessible user was tourist, since we have plenty of those in

our TM Network Operation Centre available for user testing

at any time.

TASKS

There were many tasks that we thought would be useful for

this application, but there were a handful of essential tasks

that were absolutely necessary. First was adding & sharing

your trip information. Because it is important to keep track

of our trip information before going to our trip destination.

We can choose to share or not to share our trip info via

LinkedIn social media application. This application also

featured function such as flight booking, flight search, and

it also shows current flight status. You can search flight

schedules for over 800 airlines worldwide Other than that it

also has a pushed flight notification which means traveler

will always keep on tab with their flight schedule. Another

element to the list task was hotel booking, so having the

ability to book your accommodation from a really huge

database of hotels across the world. You can pick hotels

with special deals which has a separate tag/filter so you can

find them faster. The application also pushes notifications

of new price alerts and counter offers as and when they

arrive. The next task the application can do was providing

car rental in which place you are travelling. Another

important task like local search powered by Yelp, helpful

pointers like tip calculators, currency converter based on a

country, weather information/forecast, and even limo

reservation in select cities.

DESIGN

Our design went through several stages but the following

discussion will emphasize our original design sketches and

how they evolved into the final design. Initially the original

design did not have the function to book the flight directly

from the application itself. Other than that when booking

your hotel, they will direct you to a fairly standard

information form but there’s no option to login to an

existing account so you have to enter your detail manually.

Other issues that need to be improve are the application

cannot generate it’s own itinerary. You have to e-mail all

your booking reservation detail to WorldMate dedicated

email and they will generate them and sent the itinerary to

your application later. Therefore our team tried to come out

with solutions for all of this matter so that user will have at

least an almost complete travelling applications.

However, several of our test users found this confusing, so

the final design of our interface incorporates a home screen

with links to each of the major functions. The home page

also incorporates a header with WorlMate logo and the

name of our app. These elements help to orient new users as

to the purpose of the app. Bottom of the app are list of

functions presented in a common iOS style. Activating each

function brings up a screen dedicated to the given function.

Throughout the interface we keep a consistent navigation

bar at the bottom of the app and home buttons. We use

black and blue for most text content and use blue and grey

for buttons, and other graphical content. Our initial design

used blue more heavily but after the heuristic evaluation it

was clear that it was distracting and hard to read in places.

We use black text on a white box with a caret to the right to

indicate a link or transition to more detailed information.

Figure 1: Final designs of our “welcome” & “home”

screen

The home screen remained substantially similar to the app

original design. The biggest change was putting all the

missing “function” in the app & “action” buttons on the

bottom, and reserving the footer for general navigation.

After user complaints, we decided to include a back button

at top right of the app. We adjusted the order of the buttons

on the bottom to line up and put the most common tasks

first. From the home page, trips, booking and other tools.

Users can share their trip data, which will be displayed in

LinkedIn social media.

Figure 2: Add trip & share trip data via LinkedIn

our TM Network Operation Centre available for user testing

at any time.

TASKS

There were many tasks that we thought would be useful for

this application, but there were a handful of essential tasks

that were absolutely necessary. First was adding & sharing

your trip information. Because it is important to keep track

of our trip information before going to our trip destination.

We can choose to share or not to share our trip info via

LinkedIn social media application. This application also

featured function such as flight booking, flight search, and

it also shows current flight status. You can search flight

schedules for over 800 airlines worldwide Other than that it

also has a pushed flight notification which means traveler

will always keep on tab with their flight schedule. Another

element to the list task was hotel booking, so having the

ability to book your accommodation from a really huge

database of hotels across the world. You can pick hotels

with special deals which has a separate tag/filter so you can

find them faster. The application also pushes notifications

of new price alerts and counter offers as and when they

arrive. The next task the application can do was providing

car rental in which place you are travelling. Another

important task like local search powered by Yelp, helpful

pointers like tip calculators, currency converter based on a

country, weather information/forecast, and even limo

reservation in select cities.

DESIGN

Our design went through several stages but the following

discussion will emphasize our original design sketches and

how they evolved into the final design. Initially the original

design did not have the function to book the flight directly

from the application itself. Other than that when booking

your hotel, they will direct you to a fairly standard

information form but there’s no option to login to an

existing account so you have to enter your detail manually.

Other issues that need to be improve are the application

cannot generate it’s own itinerary. You have to e-mail all

your booking reservation detail to WorldMate dedicated

email and they will generate them and sent the itinerary to

your application later. Therefore our team tried to come out

with solutions for all of this matter so that user will have at

least an almost complete travelling applications.

However, several of our test users found this confusing, so

the final design of our interface incorporates a home screen

with links to each of the major functions. The home page

also incorporates a header with WorlMate logo and the

name of our app. These elements help to orient new users as

to the purpose of the app. Bottom of the app are list of

functions presented in a common iOS style. Activating each

function brings up a screen dedicated to the given function.

Throughout the interface we keep a consistent navigation

bar at the bottom of the app and home buttons. We use

black and blue for most text content and use blue and grey

for buttons, and other graphical content. Our initial design

used blue more heavily but after the heuristic evaluation it

was clear that it was distracting and hard to read in places.

We use black text on a white box with a caret to the right to

indicate a link or transition to more detailed information.

Figure 1: Final designs of our “welcome” & “home”

screen

The home screen remained substantially similar to the app

original design. The biggest change was putting all the

missing “function” in the app & “action” buttons on the

bottom, and reserving the footer for general navigation.

After user complaints, we decided to include a back button

at top right of the app. We adjusted the order of the buttons

on the bottom to line up and put the most common tasks

first. From the home page, trips, booking and other tools.

Users can share their trip data, which will be displayed in

LinkedIn social media.

Figure 2: Add trip & Optional sharing trip data via

LinkedIn

The browsing function also stayed close to the original

design sketches. The main differences stemming from the

decision use a back button and a home screen for navigation

rather than ever present links on the bottom. The browse

works via a sequence of progressively narrow categories

that the user selects until the level of user preference was

reached. At this point selecting a flight detail brings up a

info screen about the flight with available actions such as

currency converter & confirmed booking action button.

This screen went though minor revision: star and plus icons

were replaced with less ambiguous text labels, and the

action buttons were moved to the bottom of the screen for

consistency.

Figure 3: Hotel, Flight & Limo booking functionality

We have added the currency converter and flight booking

function which was not available from the original app.

User now can finally book flight directly from the app itself

as for the hotel booking function, user did not need to fill in

any form anymore since the app already save the user detail

from their first time using booking and flight function. This

isa straight forward process. From our survey, most user

tend to agree that this is a big improvement from the

original app. Evaluation from our team showed that the app

already have many function but it still lack important

function as we already stated above.

Figure 4: Complete trip itinerary will be generate directly

from the app once all booking confirmation being done by

user.

This function was being enable after our group evaluation

with public that most of them prefer the app to generate the

itinerary itself rather than they had to e-mail them to a

dedicate channel.

Figure 5: The app provide weather forecast for our trip

destination

Figure 6: Local search are link with yelp app

If traveler chooses to user local search function, the app

presents a Google Maps-style map with icons indicating

nearby restaurants. Selecting a restaurant brings up a screen

with details including store hours, and aggregate price level.

This function was unproblematic and no significant changes

were made from the sketches.

The restaurant locator was in many ways the most

challenging section to design because it have been linked

with yelp application. Our initial design and paper

prototype was similar in some ways to our final

implementation but different other important ways. Firstly

the decision was made after our paper prototyping session

to throw out our attempt at a cure metaphor, the Local

Search Positioning System, as it was confusing, and users

didn’t understand what it was for. Instead we went for a

group search which is more straight descriptive “local

search locator.” Secondly, the initial vision was that users

would click on items directly on the map to indicate

whether that area has any local attraction or not, and to have

the map update with other local attraction is pretty decent.

User understand the paper prototyping very well, yet we

also have a computer based prototype, so we decided to

move the interaction into a separate list of items. This was

the last section of the interface implemented, so we have

detailed user testing results of this revised design

IMPLEMENTATION

We used a mobile app prototyping tool called Balsamiq to

implement our application prototype. Balsamiq is a

browser-based, drag and drop development environment,

with support for multiple mobile operating systems. It

allows for multiple collaborators on a single project,

provided they don't all use the editor at the same time. It

supports continuous live testing of each saved version of

your app, and also creating a published version for external

testing at any time. While it offers a great deal of

interactivity for its various built-in forms, it isn't

particularly good at dynamically displaying content; many

of the ‘dynamic’ aspects of our prototype had to be

implemented by creating several slightly modified copies of

static pages, and seamlessly switching between them to

maintain the illusion of a single page.

Given that dynamic interactions were difficult to render,

our prototype ended up dropping several of them between

the paper and computer stages. Several pages had pop-up

windows which would link to further pages in the paper

stage, but many of these were replaced with direct page to

page transitions in the computer version.

Figure 7: Improvement had been done to enable direct

flight booking and hotel confirmation without having to fill

any sort of registration form.

Our initial design for the app of course called for a

completely traveling app, letting users to add or remove any

trip they wished. Users could then use the list to generate an

itinerary for their trip, plotting out the most efficient way of

navigating the app when gathering all of their booking

confirmation. We were able to convey this idea in the app

with a single fixed in-store map and item list, but again

dynamic generation of content eluded us. We had also

planned to have a fully interactive map of nearby stores,

with scrolling and zooming on par with most modern map

sites, but that too ended up being not a behavior supported

by this tool; our map ended up being a static image with

location markers placed on it.

Figure 8: WorldMate will be keeping all your detail so that

you can user as default when booking anything in the app

Another major drawback of Balsamiq was its lack of

support for simultaneous collaboration on a project; while it

allowed multiple accounts access and editing privileges,

more than one user working at a time would cause pesky

notifications about overwriting another user’s work, and

several times even resulted in corrupted saves that we were

unable to edit or preview (fortunately we could revert to an

earlier copy whenever this happened). We eventually

settled upon a system where everyone would check with the

group before they opened the editor, so that nobody else's

work would be overwritten.

On the upside, Balsamiq provides a great number of

standard forms and buttons for various mobile platforms,

including Android and multiple iPhone iterations. To add

an item to the prototype, users drag it from the item toolbox

on the right of the interface to the working area. Users can

then modify various attributes, such as its width, height,

color, displayed image, number of options, and screen

location. They can then add interactions to item types that

allow for them, such as buttons or lists. Interactions allow

the app to change state when a user clicks, taps, or swipes

the area with the interaction attached. The interaction can

cause items to change their visibility, animate, be

highlighted, it may play video or audio, or it can cause the

app to navigate to a different screen. Multiple results from a

single user input can be implemented by adding one or

more callback actions after the initial one; for example, a

user tapping a button might have an initial action of an

object being highlighted, with a callback to a play audio

action, giving the overall result of a single 'highlight with

sound' interaction. One of the few built-in functions that

was even remotely dynamic came to light here, as you can

set a screen navigation interaction to return the user to the

previously viewed screen, no matter where in the app's

organizational hierarchy it's located.

EVALUATION

We as a team conducted user testing and evaluations

separately on officemate, traveler, business travel & travel

agencies near Cyberjaya area. Especially those who work at

TM NOC Cyberjaya. Because of the small amount of

resources, we felt this was the only way that we could fully

test users on the product. We designed sample steps for

these users to complete, having them working through it on

their own. Once they did complete these steps, we had them

take a survey, and interviewed them on what they thought

of the design. Both forms of feedback were used for us to

determine what to fix in the final product that would make

WorldMate app that much more reliable, complete and

easy-to-use.

SUBJECTIVE MEASUREMENTS

From the data above, we got the below results;

Based on the mean (average) rating of each attribute, the

data collection as below :

on average, the prototype is “not annoying at all”

(Mean = 1)

on average, the prototype is “not so challenging”

(Mean = 1.44)

on average, the prototype is “confusing” (Mean =

1.78)

on average, the prototype is “entertaining” (Mean

= 3.33 )

on average, the prototype is “very attractive”

(Mean = 4.44)

on average, the prototype is “extremely helpful”

(Mean = 4.89)

As a developer, we are extremely satisfied with our project

since it is more helpful to our target users. Our main

objective and goal are only one which is to help our target

users to use this application as easy as they want. Besides, it

is suitable to our group vision “meet user requirements”.

As we can see on all the data collection attributes by Mean,

we can see that the attributes for Helpful is the highest

among all the attributes which rates Mean by 4.89 while the

lowest attributes Mean are on Annoying attributes which

rates Mean by 1.00. From here we are already achieved our

main goal and target to help users. Furthermore, from our

observation on video test usability are also shown positive

feedback. All our usability users are very glad and

extremely happy that our application are really helpful to

them.

Figure 9

Based on Figure 9, clearly shown that the Helpful Attribute

is the highest mean which is 4.89, Attractive Attributes

mean are 4.44 come second, Entertaining Attributes mean

are 3.33 come third, Confusing Attributes mean are 1.78

come forth, Challenging Attributes mean are 1.44 come

fifth while the lowest Attributes means are 1.0 which goes

to Annoying Attributes.

From here, we know that Attribute Helpful get the higher

record mean because from the observation on usability

testing, majorities are comment by shown the expression of

delight while using our application. We can show the most

rating on helpful attributions on our application interface as

below screenshot interface as example.

From the app, all the itinerary that users needed already

shown with complete data needed. As example, we can

know all the activities either for our trip, our connectivity

on media social, our flight reminder, our GPS locator,

weather forecast and many more in only one single

application. So, our users just need to install single

application rather than install differentiate application. It

just waste our users time, money even their travelling trip.

For more clearly our introduction video, appreciate to visit

https://www.youtube.com/watch?v=30tY3DozD0U. So our

project are very easy to understand and very helpful on

travel trip. There are no application that built like our

project.

Based on our observation testing to users, we are not

received any bad, or annoying comment which make the

lowest Attribution are Annoying. Since our project are

completely function with requirement need, we can see the

attribution Annoying is the lowest. From earlier, we already

did not expect any bad or annoying comments from user

and that the results that we get are same. We can conclude

that our project are very good to used for.

For Attractive Attribution, the mean are the second highest

after helpful Attribution. From observation, we know that

most of the users are extremely delighted on our application

especially for flight and hotel interface. This because, these

two interface offer users to make booking through one

single application. Before this, our testing users must

booking their flight n hotel separately either by phone call

or through website. But for this application, all application

can be made on by single registration booking as below

screenshot. The most attractive and entertaining part is, the

background picture on the interface will turn to slide

presentation while waiting us to make any selection

confirmation.

Figure10

0

5

1 2 3 4 5 6

Mean 4.44 1.78 3.33 1 4.89 1.44

Attractive

Confusing

Entertaining

Annoying

HelpfulChallengi

ng

Mean

Mean

https://www.youtube.com/watch?v=30tY3DozD0U

From this data, we also get little bit shocked since we did

capture Attribution Confusion which is 1.78 data mean.

From here we can assume that our user maybe confused on

how third party appeared (example review from yelp).

Supposedly this yelp will be not affected too much on

customers experience since all the users need are already

given. As example as below screenshot.

As you can see on the right corner of the interface shown

the yelp icon. When our user click on more details and

review, the yelp interface will appear and will ask users to

sign up with yelp to review more details. This make our

users feel bad. Supposedly there will no third party review

interface. Next, the either confusion part is social media

connectivity. As our user know, they can connected their

interaction into social media by using linked connection.

This linked application are a little bit hard to use since it is

hard to connect worldMate Application with linked

account. There are not many users that have linked account

but there are preferred to use Google, Yahoo or Facebook

account. Thus, this are the point why our users are

confusing to use it. Below are the linked interface.

Figure 11

As we can see screenshot on interface example , its shown

that 29% selection are made by our users are “Helpful”

while only 6% selection are “Annoying”. This is the biggest

advantages to our group by doing this project since its meet

our user requirement. Based on the pie chart in Figure 11,

it is clearly shown that all this attributes are in-needed by

our users group. From this percentage, we can conclude that

our project are facing win-win situation on Challenging and

Confusing Attributes. Both of this attributes are complete

for each other. This means, when our users facing

confusion while running our application, they are running

hard on challenging to solve it. All of this confusion with

challenging resolution, we already resolved it as below

screenshot. We resolved it from our observation meet with

user testing. From there, we compile all the users need and

try to resolved it

Figure 12

Figure 12 shown Standard Deviation for usability test.

Attribution Challenging is the highest which is 1.0138 and

Attribution Annoying is the lowest which is 0.0. Besides,

Attribution Entertaining are 1.0 get the second highest after

Challenging, Attribution Attractive is 0.7265 come the third

highest, while Attribution Confusing is 0.6667 and

Attribution Helpful is 0.3333.

Figure 13

As we can see, by looking at Mean only, Attribution

Helpful shown that the highest 4.89 rather than Attribution

Annoying at only 1.0 but while focus on Std Dev, the

highest are Attribution Challenging which is 1.0138 rather

than the lowest is Attribution Annoying 0.0. It means that

our users are actually facing more challenging rather than

Helpful attribution from our apps. Besides, from our

consent form, there are some point at the same choices

answer. This will also effect on the Std Dev data. Below are

our collective data answer.

Figure 14

From figure 14 already prove that many answer are selected

by users are same. For example, all users (user 1,user 2,user

3) are selected same answer on Annoying Attribution.

Although the Attribution Annoying is the smallest point

among other attributions, we take it as our challenging to

make it turn to zero and we will also fulfil their requirement

need on our observation form. Although we already made

changes based on our users need, there are still missing

some new add-on function as below data collected.

Figure 15

Based on above information, although we are still missing

those needs, we just continued with our current project.

This because, if we follow all the needs in Figure 11, we

can’t completed our project based on time given. Our time

is very limited to fulfill all the needs. Even our product

activity will be more great if we can follow all the need but

we can’t. Time management is very important for us to

build up a perfect application.

PERFORMANCE MEASUREMENT:

S=PC

T

S = performance score for user

T= time spent by user on specified task

P= percentage task completed

C= arbitrary constant based on fastest possible task solution

User 1

Task 1 (Finding restaurant)

100 (35) / 43

=81.4%

Task 2 (Calculate Tip)

100 (30) / 37

=81.1%

Task 3 (Search Flight Schedule)

100 (35) / 43

=81.4%

Figure 16

Based on figure 16, shown that user 1 performance are

81.4% for Finding Nearest Restaurant, 81.10% for

Calculate Restaurant Tip and 81.40% for Search Flight

Schedule.

User 2


100 (35) / 48

=72.9%


100 (30) / 31

=96.7%


100 (35) / 53

=66%

Figure 17

Based on Figure 17, shown that users 2 performance are



Schedule.

User 3


100 (35) / 53

=66%


100 (30) / 35

=85.7%


100 (35) / 41

=85.4%

Figure 17

Based on Figure 17, shown that users 2 performance are



Schedule.

Usability

test / Task

Find Nearest

Restaurant

Calculate

Restaurant

Tip

Search

Flight

Schedule

User 1 81.4% 81.1% 81.4%

User 2 72.9% 96.7% 66.0%

User 3 66.0% 85.7% 85.4%

Figure 18

Figure 19

Figure 18 & Figure 19 shown overall performance for all

our users testing. Based on results above, we can conclude

that our application are easy to use and easy to understand.

The biggest different between all those task are because on

our user ability that glad nor lack to use the application.

Overall its meet our expectation for time being used by our

test users. Its nor far or long time to take to settle it. The

lowest percentage is for Finding Nearest Restaurant and

Search Flight Schedule. This because the process flow to

complete the task is too long rather than complete task for

calculating tip which composed the highest percentage

among all task because the step flow is quite simple and

very easy. All our users can complete to finish the task

given and that mean our project is successful and meet all

users requirement.

REFLECTION

Through our entire project, we ran into various issues.

Upon reflection, it became evident that some of these issues

could have been foreseen. while others were as a result of

limitations of our prototyping tools. These are the following

issues we ran into, and what we would do differently in

future projects in order to make the design process easier

and more successful.

ISSUES

Our first problem we were tasked with was deciding upon a

prototyping tool to utilize to best represent our application.

We tested many and they had various limitations, and we

ran into a prototyping tool called Balsemiq. It had many

customizable features, and looked visually pleasing for

what could be a potential IOS application. We were pleased

to find that we could all log in at the same time and work on

it, and after spending countless hours working we all saved.

To our horror, every page except for one was erased. After

so many hours of work we had to start all over. Why would

a prototyping tool that supported multi user login on a

single project not allow working on the prototype

simultaneously?

The next issue we ran into which we didn't realize until

after our first prototype was that we originally didn't have a

currency converter and confirmed booking action button.

This was an issue because it did not allow us to go book

directly using the app itself

After identifying this issue, we also found that as users hit

the back button multiple time, we ran into verification

screens again as well as loading screens which should not

have occurred. The next issues we had were related to font

and color scheme. The fonts were deemed to be too small

and illegible, and the color scheme we used utilized blue

and white.

Finally, the last issue was that we found our process to be

incredibly tedious because we thought by implementing the

pages statically it would be easier, however in reality it

ended up being very time consuming, and we had an

incredibly large amount of pages.

WHAT WE WOULD DO DIFFERENTLY

For our next revolutionary prototype, we would utilize a

more common, or even paid prototyping tool. This would

ensure a more problem free experience, and we could even

be offered customer service in the case that we run into any

issues. It could also be a prototyping tool that has more

options in creating other interfaces such as android, which

wasn't really an option in this prototyping tool.

Next, we realized how important back and home page

buttons are. We would be sure to include a back option

from the beginning, as well as a home button to prevent

frustration of users, and lack of navigability. In addition,

back and home buttons are essential to any mobile

application.

In regards to font size and color, we would be sure to a font

that is legible based upon how far the prototype should be

held away from the eyes, and we would avoid colors such

as green and red, and also provide a contrast between the

background and text colors.

Finally, we would actually code the prototype and make it

dynamic rather than static. This would let us avoid many

issues we encountered, and it would actually be functional

rather than literally just a model.

CONCLUSION

The design process was incredibly informative and the

experience was a excellent one. We learned a lot, not only

technically related, but also in regards to time management

and teamwork. We learned about Usability and how

important it is in the design process, as well as imagining

ourselves in the place of the users. Through our project we

found that what we necessarily thought was important and

needed in an application wasn't exactly what the user

wanted and needed. This showed us how important

prototyping is because a company that dives into a project

without actually taking the time to make a prototype may

end up with catastrophic sales if there is a certain feature

that either is inconvenient to use, doesn't do what it is

intended to, or isn't included at all

Feedback from user testing (High Fidelity)

Add on selection tip for each country region

Brilliant weather graphics

Automated flight status

Sharing connectivity in social media via

Facebook, Twitter

Hotel price alerts

Calendar synchronization

Priority Customer Support

Provides pushed notifications of flight delays,

cancellations and gate changes

Add on feedback button

ACKNOWLEDGEMENTS

All in all, it was a pleasure to be in this class, and we

learned a great deal of information regarding HCI. It is

extremely valuable because many of us will be applying

these concepts to our future lives and our technical fields.

Thank you Allah S.W.T for giving us chance to participate

in this valuable experience, We would also like to thank Dr

Noranita bt Fairos, our classmates, officemates and to all

participants who helped us along the way in this iterative

process by providing feedback and input along the way. We

hope you have an excellent vacation. Happy new year!.

Application Software Requirements (WorldMate

App)

1. Balsamiq software (built up Mock-up)

2. Camtasia software (recording video for target

user)

3. CamStudio software (recording screenshot

video – introduction video)

4. Freemake software (convert video recording)

5. VideoScribe software(creating animation

video)

6. Microsoft visio (create up diagram/UCD

process)

7. clipConverter software (convert resolution

video)

REFERENCES

1. https://developers.worldmate.com/home.php

2. http://www.worldmate.com/

3. https://play.google.com/store/apps/details?id=com.

worldmate

4. https://itunes.apple.com/us/app/worldmate-travel-

plans-flight/id317821764?mt=8

5. https://www.facebook.com/WorldMate/

6. https://www.microsoft.com/en-

us/store/apps/worldmate/9wzdncrdnqm3

7. https://twitter.com/worldmate

8. http://www.igeeksblog.com/worldmate-iphone-

app/

9. https://www.worldmatelive.com/features.html

http://www.igeeksblog.com/worldmate-iphone-app/

http://www.igeeksblog.com/worldmate-iphone-app/

worldmate app final report - wordpress.com...produce an organised itinerary which will certainly...

Documents