Overview
This unit is devoted to the design and implementation of Android and iOS mobile applications. Native mobile programming languages will form the basis upon which programming techniques and design patterns will be developed for creating standalone applications. Commonly used mobile tools and frameworks for mobile application development are used. All stages of software development from the initial idea, through to development and testing will be covered. Consideration will be given to the business case from the developers' point of view. Some examination of how to market mobile apps is also undertaken. Research skills will be introduced as a means of keeping up to date with the changing mobile development landscape.
Details
Pre-requisites or Co-requisites
Pre-Req: COIT20268 Responsive Web Design
Important note: Students enrolled in a subsequent unit who failed their pre-requisite unit, should drop the subsequent unit before the census date or within 10 working days of Fail grade notification. Students who do not drop the unit in this timeframe cannot later drop the unit without academic and financial liability. See details in the Assessment Policy and Procedure (Higher Education Coursework).
Offerings For Term 3 - 2026
Attendance Requirements
All on-campus students are expected to attend scheduled classes - in some units, these classes are identified as a mandatory (pass/fail) component and attendance is compulsory. International students, on a student visa, must maintain a full time study load and meet both attendance and academic progress requirements in each study period (satisfactory attendance for International students is defined as maintaining at least an 80% attendance record).
Recommended Student Time Commitment
Each 6-credit Postgraduate unit at CQUniversity requires an overall time commitment of an average of 12.5 hours of study per week, making a total of 150 hours for the unit.
Class Timetable
Assessment Overview
| Assessment Task | Part Weighting (% of assessment) |
Assessment Security Level | Gen AI Guidance Levels |
|---|---|---|---|
| 1. Assessment 1 - Design (20% of unit ) | |||
| Application Design (Presentation) | 100% of 20% | Medium | AI-Assisted (Guided Collaboration) |
| 2. Assignment 2 - Prototype (30% of unit ) | |||
| Application Prototype (Practical Assessment) | 100% of 30% | Medium | AI-Assisted (Guided Collaboration) |
| 3. Assignment 3 - Usability Goals (20% of unit ) | |||
| Application Usability Goals (Practical Assessment) | 100% of 20% | Medium | AI-Assisted (Guided Collaboration) |
| 4. Assignment 4 - App (30% of unit · 2 parts ) | |||
| Part 1 – Final Application (Practical Assessment) | 70% of 30% | Medium | AI-Assisted (Guided Collaboration) |
| Part 2 – Demonstration Video (Oral Examination) | 30% of 30% | High | No Gen AI Use |
Assessment Grading
This is a graded unit: your overall grade will be calculated from the marks or grades for each assessment task, based on the relative weightings shown in the table above. You must obtain an overall mark for the unit of at least 50%, or an overall grade of 'pass' in order to pass the unit. If any 'pass/fail' tasks are shown in the table above they must also be completed successfully ('pass' grade). You must also meet any minimum mark requirements specified for a particular assessment task, as detailed in the 'assessment task' section (note that in some instances, the minimum mark for a task may be greater than 50%). Consult the University's Grades and Results Policy for more details of interim results and final grades.
All University policies are available on the CQUniversity Policy site.
You may wish to view these policies:
- Grades and Results Policy
- Assessment Policy and Procedure (Higher Education Coursework)
- Review of Grade Procedure
- Student Academic Integrity Policy and Procedure
- Academic Progression Policy and Procedure
- Student Refund and Credit Balance Policy and Procedure
- Complaints Policy and Procedure
- Information and Communications Technology Acceptable Use Policy and Procedure
This list is not an exhaustive list of all University policies. The full list of University policies are available on the CQUniversity Policy site.
Feedback, Recommendations and Responses
Every unit is reviewed for enhancement each year. At the most recent review, the following staff and student feedback items were identified and recommendations were made.
Feedback from Student Feedback in class
Students requested additional walkthrough video recordings for setting up the development environment prior to Week 1 practical labs.
Short, pre-recorded video guides on software installation and initial project setup will be made available to students on Moodle.
- Design and implement native mobile applications
- Describe and be able to develop critical parts of a native mobile system programming interface
- Use an integrated IDE to build, debug and test native mobile applications
- Determine the business impact of a given mobile solution and critically assess the implementation of an app and its likely marketability and profitability
- Critically analyse a research issue in mobile computing.
The Australian Computer Society (ACS) recognises the Skills Framework for the Information Age (SFIA). Organisations, governments, and individuals in many countries adopt SFIA, which provides a widely used, consistent definition of ICT skills. SFIA is increasingly being used when developing job descriptions and role profiles.
ACS members can use the tool MySFIA to build a skills profile at https://www.acs.org.au/professionalrecognition/mysfia-b2c.html
This unit contributes to the following workplace skills as defined by SFIA 9 (the SFIA code is included):
- Systems Design (DESN)
- System Integration (SINT)
- Program ming/Software Development (PROG)
- Data Analysis (DTAN)
- Database/Repository Design (DBDS)
- Testing (TEST)
- Network Support (NTAS)
- Release and Deployment (RELM)
- Applications Support (ASUP)
Alignment of Assessment Tasks to Learning Outcomes
| Assessment Tasks | Learning Outcomes | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
|
1.
Assessment 1
(20% of unit )
Presentation
|
|||||
|
2.
Assessment 2
(30% of unit )
Practical Assessment
|
|||||
|
3.
Assessment 3
(20% of unit )
Practical Assessment
|
|||||
|
4.
Assessment 4
(30% of unit · 2 parts
)
Part 1 -
Practical Assessment
Part 2 -
Oral Examination
|
|||||
Alignment of Graduate Attributes to Learning Outcomes
| Graduate Attributes | Learning Outcomes | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1 - Knowledge | |||||
| 2 - Communication | |||||
| 3 - Cognitive, technical and creative skills | |||||
| 4 - Research | |||||
| 5 - Self-management | |||||
| 6 - Ethical and Professional Responsibility | |||||
| 7 - Leadership | |||||
| 8 - First Nations Knowledges | |||||
Textbooks
There are no required textbooks.
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- Visual Studio Code (recent e.g. 1.105)
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
f.sanati@cqu.edu.au
Week 1
Begin Date: 09 Nov 2026Module/Topic
1 Introduction
Chapter
- Mobile design challenges
- Mobile UI guidelines
- (Bailey & Biessek 2023, Chp 1)
Events and Submissions/Topic
Week 2
Begin Date: 16 Nov 2026Module/Topic
2 Layout
Chapter
- Toolbar and Menus
- (Bailey & Biessek 2023, Chp 5)
Events and Submissions/Topic
Week 3
Begin Date: 23 Nov 2026Module/Topic
3 Adaptive
Chapter
- Adaptive layouts
- (Windmill 2020, Chp 4)
Events and Submissions/Topic
Week 4
Begin Date: 30 Nov 2026Module/Topic
4 Intro to Navigation and State
Chapter
- (Bailey & Biessek 2023, Chp 8)
Events and Submissions/Topic
Week 5
Begin Date: 07 Dec 2026Module/Topic
5 Advanced Navigation
Chapter
- (Windmill 2020, Chp 8)
Events and Submissions/Topic
Week 6
Begin Date: 14 Dec 2026Module/Topic
6 Shared State
Chapter
- Passing data
- (Tyagi 2021, Chp 18)
Events and Submissions/Topic
Mid-Term Break
Begin Date: 21 Dec 2026Module/Topic
Chapter
Events and Submissions/Topic
Week 7
Begin Date: 04 Jan 2027Module/Topic
7 Gestures
Chapter
- Swipe
- Drag
- (Bailey & Biessek 2023, Chp 6)
Events and Submissions/Topic
Week 8
Begin Date: 11 Jan 2027Module/Topic
8 Testing
Chapter
Events and Submissions/Topic
Week 9
Begin Date: 18 Jan 2027Module/Topic
9 Forms
Chapter
- (Windmill 2020, Chp 5)
Events and Submissions/Topic
Week 10
Begin Date: 25 Jan 2027Module/Topic
10 Themes
Chapter
- Colours
- Typography
- (Adefioye 2024, Chp 4)
Events and Submissions/Topic
Week 11
Begin Date: 01 Feb 2027Module/Topic
Unit review
Chapter
Events and Submissions/Topic
Demonstration Video Due: Week 11 Monday (1 Feb 2027) 11:45 pm AEST
Week 12
Begin Date: 08 Feb 2027Module/Topic
Chapter
Events and Submissions/Topic
Exam Week
Begin Date: 15 Feb 2027Module/Topic
Chapter
Events and Submissions/Topic
Lecture / Unit coordinator:
Dr. Farzad Sanati
f.sanati@cqu.edu.au
1. Assessment 1 - Design ( 20% of unit )
Presentation
You are to design a mobile application and justify your design decisions using scholarly sources in a presentation
Week 5 Monday (7 Dec 2026) 11:45 pm AEST
Mid-Term Break Monday (21 Dec 2026)
• Analysis of existing applications and solutions, their limitations, and your proposed improvements
• Persona: research-informed identification of the intended user groups and how well you justify that their needs are met by your solution
• Privacy and Ethics: management of Australian Privacy Principles (APPs) and identification of ethical risks including dark-pattern risks, persuasive or behavioural influences and accessibility inequities
• Strength of peer-reviewed scholarly sources including how well these sources justify your persona, task analysis (activity diagrams), ethical analysis and design choices; and quality of your referencing
• Technology-agnostic design: cross-platform applicability, relying on universal design principles rather than, e.g. a specific platform's guidelines
• Usability goals: measurable and relevant to the persona and the solution.
- Describe and be able to develop critical parts of a native mobile system programming interface
- Critically analyse a research issue in mobile computing.
2. Assignment 2 - Prototype ( 30% of unit )
Practical Assessment
You will develop a Flutter implementation for the mobile application you designed in Assignment 1, focusing on user interface design and adherence to specified design constraints. You will produce a
screen-based prototype that demonstrates the key tasks outlined in the provided activity diagrams. Your interface must follow the Material3 UI design guidelines and Flutter APIs. All screens must be
implemented and accessible within a single application. Your prototype is intended to showcase layout, structure and interaction patterns rather than full application logic. Accordingly, your screens may be
hardcoded, and you are not expected to implement complex transitions, gestures, state management, or advanced navigation.
Week 6 Monday (14 Dec 2026) 11:45 pm AEST
Week 7 Monday (4 Jan 2027)
• Quality of static screen design: clear visual hierarchy including a responsive, adaptable layout, adherence to prescribed UI guidelines and required APIs; appropriate use of usability design
patterns such as navigation structures
• Completeness of implementation: are screens implemented for all major steps represented in the activity diagrams from your Assignment 1
• Code quality: correct use of coding conventions, adequate commenting, lack of deprecated code and overall code readability. In this unit, you are expected to use variable naming to self-
document code and provide comments in code to explain design aspects that would not be self-evident to an average student in the unit.
• Per-screen mobile heuristic evaluation including quick and easy interaction, micro-usage design, and consistency.
• Management of users’ privacy and ethics, and • Presentation content and quality.
- Design and implement native mobile applications
- Use an integrated IDE to build, debug and test native mobile applications
3. Assignment 3 - Usability Goals ( 20% of unit )
Practical Assessment
In this assignment, you will evaluate your mobile app by testing the usability goals you defined in Assignment 1. You will recruit participants and record videos of each participant attempting the tasks
associated with your usability goals. After collecting your data, you will analyse the results, identify patterns in user performance, and develop recommendations for improving your mobile app's design.
Week 9 Monday (18 Jan 2027) 11:45 pm AEST
Week 11 Monday (1 Feb 2027)
• Completeness of usability goal testing: all usability goals have been performed by all participants and there is sufficient evidence to evaluate each usability goal
• Quality of results and recommendations. Your recommendations should be actionable but framed at the design-principle or design-pattern level, e.g. navigation or error prevention, rather than low-level cosmetic suggestions, e.g. changing a colour.
- Describe and be able to develop critical parts of a native mobile system programming interface
- Determine the business impact of a given mobile solution and critically assess the implementation of an app and its likely marketability and profitability
4. Assignment 4 - App ( 30% of unit · 2 parts )
Part 1 - Practical Assessment
In this assignment, you will complete the second iteration of your mobile application's development. You will develop and deploy a fully functioning Flutter/Material3 mobile app. Your interface must follow the
Material3 UI design guidelines and Flutter APIs. All functionality must be implemented and accessible within a single dartpad.dev application.
This iteration extends beyond static design: you are expected to incorporate behavioural elements including advanced navigation techniques, gestures, state management, persistence and transitions, to
create a responsive, adaptive, and predictable user experience.
Week 11 Monday (1 Feb 2027) 11:45 pm AEST
• Behavioural interaction quality including the quality of state management, persistence, navigation routing, gestures and transitions
• Quality of screen design: visual hierarchy including layout, spacing, typography and colour usage, adherence to prescribed UI guidelines and required APIs; appropriate use of usability design patterns such as navigation structures
• Completeness: all features implemented
• Code quality: design-level comments in code, coding conventions, lack of deprecated code and code readability
• Heuristic evaluation quality, e.g. interaction, micro-usage, readability, simplicity, consistency, errors, responsiveness, learnability, personalisation and continuity; and privacy and ethics
• Management of users’ privacy and ethics
• Deployment
- Design and implement native mobile applications
- Use an integrated IDE to build, debug and test native mobile applications
- Determine the business impact of a given mobile solution and critically assess the implementation of an app and its likely marketability and profitability
Part 2 - Oral Examination
Record a 10-minute video presentation that includes:
• Demonstration of your apps responsive and adaptive screen layout (0 slides)
• Demonstration of your gestures and transitions (0 slides)
• Explanation of state management, navigation routing, gestures, transitions and responsive and adaptive screen layouts at the code level (0 slides)
Week 11 Monday (1 Feb 2027) 11:45 pm AEST
Video demonstration of features, explanation of the code, and application execution.
- Design and implement native mobile applications
- Use an integrated IDE to build, debug and test native mobile applications
- Determine the business impact of a given mobile solution and critically assess the implementation of an app and its likely marketability and profitability
As a CQUniversity student you are expected to act honestly in all aspects of your academic work.
Any assessable work undertaken or submitted for review or assessment must be your own work. Assessable work is any type of work you do to meet the assessment requirements in the unit, including draft work submitted for review and feedback and final work to be assessed.
When you use the ideas, words or data of others in your assessment, you must thoroughly and clearly acknowledge the source of this information by using the correct referencing style for your unit. Using others’ work without proper acknowledgement may be considered a form of intellectual dishonesty.
Participating honestly, respectfully, responsibly, and fairly in your university study ensures the CQUniversity qualification you earn will be valued as a true indication of your individual academic achievement and will continue to receive the respect and recognition it deserves.
As a student, you are responsible for reading and following CQUniversity’s policies, including the Student Academic Integrity Policy and Procedure. This policy sets out CQUniversity’s expectations of you to act with integrity, examples of academic integrity breaches to avoid, the processes used to address alleged breaches of academic integrity, and potential penalties.
What is a breach of academic integrity?
A breach of academic integrity includes but is not limited to plagiarism, self-plagiarism, collusion, cheating, contract cheating, and academic misconduct. The Student Academic Integrity Policy and Procedure defines what these terms mean and gives examples.
Why is academic integrity important?
A breach of academic integrity may result in one or more penalties, including suspension or even expulsion from the University. It can also have negative implications for student visas and future enrolment at CQUniversity or elsewhere. Students who engage in contract cheating also risk being blackmailed by contract cheating services.
Where can I get assistance?
For academic advice and guidance, the Academic Learning Centre (ALC) can support you in becoming confident in completing assessments with integrity and of high standard.
What can you do to act with integrity?