Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due
Hong Kong Baptist University
College of International Education (CIE)
ELSS2112 Mobile Computing
Assignment 2
Create a multiple-screen task management app. A task consists of the following information items: task name, due date, priority level, task details, and task status.
- Priority levels can be categorized as “High”, “Medium”, or “Low”.
- The task status can be “pending” once it is created or “completed” after completion.
- A sample task may have:
- Task name = “Project Report”
- Due date = 15 Nov 2023
- Priority level = “High”
- Task details = “Complete the final report for the project.”
- Task status = “pending”
You must save the task data using a local table data source. The app must provide the following functions:
1. Add a task: Users add a task by entering all the information. The initial status is “pending”.2. Browse the tasks: Users can browse through all the tasks or filter the tasks by priority level or task status.3. Complete a task: Users can mark the status of a task from “pending” to “completed,” but not the other way around.4. Delete a task: Users can delete a task.5. Edit a task: Users can edit any details of an existing task, provided the task is not “completed.”
General requirements
- Design your own interface for the app. The app should be easy to use and display appropriate instructions and information.
- Perform error checking with the input values or limit the input values by suitable component settings.
Assignment submission and deadline
- Share the project of your assignment using the icon. Generate the link to access your project. Submit the link to Moodle.
- Test your app with the web previewer. Capture testing screenshots of your app’s interface and submit the images to Moodle.
- The deadline is 11:59 pm, 19 Nov 2024 (Tue).
The assessment criteria are as follows:
|
Criteria |
Exceptional |
Good |
Satisfactory |
Needs Improvement |
Unsatisfactory |
|
User Interface / User Experience Design (35%)
|
The app has an exceptional, intuitive, and aesthetically pleasing interface. The user
experience is seamless, with easy navigation and logical flow.
|
The app has a good interface with mino issues. User experience is generally good, with a few areas that could be improved.
|
The app's interface is satisfactory but lacks some polish. User experience is passable, but several areas could be improved.
|
The app's interface is clumsy and not userfriendly. User
experience is
poor, with
difficulty in
navigation and
understanding
the app flow.
|
The app's
interface is
poorly
designed or
non-existent.
User
experience is
severely
compromised.
|
|
Functions Correctness and Errors Checking (55%)
|
The app
functions
perfectly and
meets all the
specified
requirements.
Error checking
is thorough
and robust,
ensuring a
smooth user
experience.
|
The app
functions well,
meeting most
of the
specified
requirements.
Error checking
is present but
misses a few
cases.
|
The app
functions
satisfactorily,
meeting some
of the
requirements.
Error checking
is present but
not
comprehensive.
|
The app barely
functions,
meeting only a
few
requirements.
Error checking
is minimal or
ineffective.
|
The app
doesn't
function as
expected or
doesn't meet
any
requirements.
No effective
error checking
is present.
|
|
Component naming and Comments (10%)
|
All
components
are
appropriately
and
consistently
named.
Comments are
clear, concise,
and explain
the code
effectively.
|
Comments are
extensive,
offering a solid
understanding
of code
functionality
and
component
naming.
|
Most of the
components
are
appropriately
named.
Comments are
mostly clear
and helpful,
with a few
areas lacking
explanation.
|
Few
components
are
appropriately
named.
Comments are
sparse and do
not effectively
explain the
code.
|
Components
are not
appropriately
named. No
comments are
present or
comments do
not contribute
to
understanding
the code.
|