Coursework Title:

COMP1661 Application Development for Mobile Devices -

Due date: 12th April 2018

Student Name: Nguyen Ngoc Chan

Student ID: GT60826

1
Section 1

Features Implementation
A Full Implementation on native app and hybrid app
B Full Implementation on native app and hybrid app
C Full Implementation on hybrid app
D Full Implementation on hybrid app
E Full Implementation on hybrid app
F Full Implementation on hybrid app
G Adding feature get photos from gallery, zoom in, zoom out photo on hybrid
app

Section 2
Weakness of my applications:
Native App:
o The UI is well in material design.
o Location still not show in the map.
Hybrid App:
o The photo feature, in some cases, does not work correctly.
o Location still not show in the map.
Section 3
Based on the requirements of the scenario, I build an application called iVolunteer. This
application can help users in storing their information, these information is stored in the SQLite
database and they can retrieve them at any time they want.
Main features

 Create new activity: In this feature, the application will show a screen with a form for users
to insert their information such as activity name, location of that activity, date, time and
volunteer activity. Three fields activity name, time and volunteer activity is required, users
must insert information on these field, if not, the application will show a warning notification
and not insert to database. Moreover, these input fields also do not accept input which has
length over fifty characters, if users insert input over fifty characters, the application will show
a warning notification, users must check their input again. Finally, if all inputs are correct,
these information will be stored into database when users click “Submit” button on the
screen and an successful alert is shown to inform users that their activity is stored.

2
 View all activities: In this feature, when users click “All Activities” button on the screen, the
application will list all activities that are stored in the database. Users can click on any activity
to view detail information and also make a review about this activity or remove it.
 View one activity: In this feature, the application will show all information about one specific
activity. In this screen, users can make a review about this activity by adding review and taking
picture. When users click on “Submit Report”, the application will store their report to the
database. Moreover, in this screen, users can also remove activity if they want. When users
click on “Remove Activity”, a popup confirmation will be shown for users to confirm their
action, if they wish, the application will remove activity from database.
 Search activity: In this feature, the application will show a screen with an input for users to
enter their activity’s name which they want to search. After users enter input and click on
“Search” button, the application will list all activities which have activity’s name contains
letters of users’ input. On this result list, users can click on any activity to view its detail
information as they wish.

3
Section 4
a) Design app screens - Basic details input screen

Home Screen

4
Input Screen – Add New Activity

5
b) Implement forms validation and check for duplicate events

Validate Activity’s Name Field - Required

6
Validate Date Field - Required

7
Validate Volunteer’s Name - Required

8
Validate Activity’s Name – Too Long (50 Chars Maximum)

9
Validate Volunteer’s Name – Too Long (50 Chars Maximum)

10
Validate Location – Too Long (50 Chars Maximum)

11
c) Store, view and delete the basic details

Notification When New Activity Added To Database

12
List All Activities Screen

13
Activity Detail Information Screen - A

14
Activity Detail Information Screen - B

15
Confirmation Removing Activity

16
d) Search

Searching Screen

* Users can click on any activities in result list to view detail information

17
e) Add a report input screen

Activity Report Screen

* User can write a report about an activity and take picture at that time. On review input field,
maximum characters is 200 and not required. Picture after being taken will be shown on the
screen, user can zoom in that picture by clicking on it. After entering review and taking photo,
user click on button “Submit Report” to store to database.

18
Validate Review Field – Too Long (200 Chars Maximum)

19
Notification When Review Added To Database

20
f) Features a) and b) are to be implemented as a native Android app coded in Java

Home Screen – Input Form

21
Validate Activity’s Name Field – Required

Validate Date Field – Required

22
 Validate Volunteer’s Name Field – Required

Validate Location Field – Too Long (Maximum 50 Characters)

23
 Validate Activity’s Name Field – Too Long (Maximum 50 Characters)

Validate Volunteer’s Name Field – Too Long (Maximum 50 Characters)

24
Second Screen – Detail Information

25
g) Add additional features to either or both the Android or PhoneGap version of the app
I added additional features Take Photo and show Location on Map in Hybrid App

* When user click on “Camera” button, the application will launch device’s camera and take
picture and show the picture on the screen. When user click on “Submit Report” button, the
application will store report and picture to local database.

26
* The application will show location from user’s input on map

27
Section 5
Evaluation of the application
a) Advantages
o All activities’ information are stored into local database exactly.
o Users can insert new activity to database easily.
o Users can view all activities which are stored in database.
o Users can do searching activities smoothly. They just need entering a letter or some
letters to search activities having name contains those letters.
o Validation on each form is correctly performed.
o The application’s style is designed by Boostrap.
o Using well known icons that make users easy to use the application.
o The application can view location from users’ input on map correctly.
o The application can use device’s camera to take picture, show on screen and store it into
local database.
b) Disadvantages
o The user interface is not well at material designed.
o Having error when viewing picture in some cases.
c) Human computer interaction
The application is well designed with a friendly user interface:
o The background – color is mainly used bright blue hue that would make users feel
comfortable when using the application.
o Buttons’ background – color is designed suitable for every each function that they do. It
will make these button distinctive, and users will not have any mistake between them.
o On every button, there is a specific icon for each feature. Submit button’s icon is different
with remove button’s icon. These icons are well known icons, users can easily use them
without any mistake.
o Layout is designed logically. Button submit on the right side of the screen, button back,
button home is on the left side. Button close application is on the bottom of the screen.
o In the main screen, there are instructions for users when first use the application.
d) Security
My application does few security implementation. This application works locally, all detail
information is store into local database. However, in the inputs I make sure that every field must
be validated exactly to ensure the database’s integrity. Such as what field is required to enter, if
users do not enter anything, the application will raise a notification to users. Moreover, if users
enter too long text, the application will prevent that input to insert to database.
e) Maintainability

28
 To get more users’ belief and satisfaction in using the application, it needs to be maintained
frequently. In my case, I have to test the application carefully in order to increase performance,
check validation on every form input, fix errors and bugs occur, prevent any unexpected errors.
Moreover, I have to maintain it in order to cope with the new environment in the future.
f) Changes – Future work
o Applying material design to the application.
o Develop online database to store data, users can login with Social Network account such
as Facebook, Google, etc.
References
(1) "Android Language Breakdown". Open Hub. October 25, 2017. Archived from the original
on December 14, 2017. Retrieved December 15, 2017.
(2) Morrill, Dan (September 23, 2008). "Announcing the Android 1.0 SDK, release 1". Android
Developers Blog. Google. Archived from the original on March 5, 2017. Retrieved March
11, 2017.
(3) "Android P". Android Developers. Google. March 9, 2018. Archived from the original on
August 17, 2015. Retrieved March 9, 2018.
(4) PhoneGap License". Phonegap.com. Retrieved 2013-10-09.
(5) "FAQ | PhoneGap Build | Edge Tools & Services | Adobe & HTML". Html.adobe.com.
Retrieved 2013-10-09.
(6) "Adobe Announces Agreement to Acquire Nitobi, Creator of PhoneGap". Adobe.com.
2011-10-03. Retrieved 2012-04-07.
(7) Jose Fermoso (April 5, 2009). "PhoneGap Seeks to Bridge the Gap Between Mobile App
Platforms". GigaOM. Retrieved 2012-04-07.

29