Mobile Application 1

Chalani Tharanga Wanigasekara (0329562)
Mobile application 1
Lectures, Exercises and Assignments

---

Week 1
The lecturers gave a brief introduction and explained module outline. 

Lecture 1

1. Native app development

A Native App is an app developed essentially for one particular mobile device and is installed directly onto the device itself.
ios-project is c 

android- project is java 

windows- the project is c++(not sure)
it is good, and have fewer disadvantages

2. web app(mobile)

Internet-enabled apps that are accessible via the mobile device’s Web browser.
They need not be downloaded onto the user’s mobile device in order to be accessed. Basically, it is working with HTML and Java.
it doesn't matter the device that you're using ( either ios or android)
Ex: Facebook

3. Hybrid (ionic, PhoneGap, Sencha)
connect it to the devices.

Week 2
Lecture 2
The lecturer gave 2 articles which are relating usability, and its attributes.

Usability-
Lecerof et al. (1998) provided usability definition by addressing relevance of a system to users’ needs, efficiency, users’ subjective feelings, learnability, and system’s safety feature, such as granting users the right to undo actions that may lead to errors.

attributes:
1. Effectiveness- achieve the goal of an app for a user, user's goal (Ex: adobe capture)
2. Efficiency- how the button respond, how efficient the system
3. Flexibility
4. Learnability-easy to access
5. Memorability- the user is able to return to the

system after some period of not having used it, without having to relearn everything

6. Satisfaction- users are subjectively satisfied during use

Week 3

The lecturer was given 2 articles to read relating to the 'usability'.

usability definition- addressing the relevance of a system to users’ needs, efficiency, users’ subjective feelings, learnability, and system’s safety feature, such as granting users the right to undo actions that may lead to errors. (Lecerof et al. (1998)

attributes:
1. Effectiveness- achieve the goal of an app for a user, user's goal (Ex: adobe capture)
2. Efficiency- how the button respond, how efficient the system
3. Flexibility
4. Learnability-easy to access
5. Memorability
6. Satisfaction

(you should try the usability testing every time. While you make the concept of the app to before you release the app to the public)

Exercise 1
Group work- members (Regina, Vivien, Paulina, Aryna and me)

the lecturer divided the class into 3 groups and found out a good app and a bad app.

My group chose shopping apps for good and bad apps. and chose 'Zalora' as a good app. Because,  it is easy to find out what you want to order, it has  visual search (you should take a picture of the product what you want, and the app is showing same product or similar product), clear information with the image, the order tracking is easy and straight-forward, you don't need to login to do online shopping.

However, this app has some improvements to do. 

We chose 'Chilindo' as a bad app. Because it doesn't have the search engine. So it is difficult to find what the user wants to bid. Suddenly, the page is getting refresh automatically, when you scroll down and not showing the previous items. Quite confusing to understand, bidding time is keep looping, and they didn't add the customer service. The design is not attractive especially the photos that taken. The bid history also confuse. There are 3 sections in the history part; they can make it into 2 section, so it looks simple.

Feedback

Zalora app has to do some improvements. Especially, the information part.

Exercise 2

Group work- members (Paulina, Aryna and me)

The lecturer gave a boarding pass to find out (un)important details and remake it.

the boarding pass that lecturer gave to us

Our group followed Sri Lankan airlines boarding pass and Garuda Indonesia airlines boarding pass. 

We came up with 2 boarding pass.

We removed the food advertisement because usually, should order foods through online. 

Feedback
Should add two barcodes on the first paper. Should insert the advertisement. we cannot remove anything if the clients want, but designer thinks it is not necessary.