FIT5046 Mobile and Distributed Computing Systems
The Complete Study & Assessment Guide · S2 2026FIT5046 Overview
- Monash Faculty of Information Technology
- Semester 2, 2026
- a postgraduate Level 5 unit
- 6 credit points
- a mobile and distributed systems development unit
FIT5046 covers Kotlin, Jetpack Compose, navigation, Room, Retrofit, mobile UI, ubiquitous and context-aware computing, sensors, IoT, location awareness and ethics. It is taught within Monash Faculty of Information Technology. It is a postgraduate Level 5 unit. It carries 6 credit points.
- State has an owner UI defects multiply when mutable state has no explicit source of truth.
- The network will fail A distributed mobile design must specify loading, timeout, retry, cache and stale-data behaviour.
- Context needs consent Location and sensor value must be balanced against permission, privacy and user control.
- No final exam S2 assessment culminates in an app and individual interview.
What you get in the full FIT5046 Study & Assessment Guide
- 11 chapters, 30 pages — every assessed topic, week by week
- 14 original practice questions, each with a model answer
- 11 worked examples, solved the way FIT5046 marks
- 20 computed figures, redrawn from the course’s own numbers
- Before-you-submit checklist for the Android App Development and Individual Interviews (40%) — what markers reward, what costs marks
Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full study & assessment guide.
How FIT5046 is assessed
| Component | Weight | Format |
|---|---|---|
| Research Paper Presentation | 15% | Due 21 August 2026 at 11:55 pm |
| Android Application Design Proposal and Skeleton | 20% | Due 11 September 2026 at 11:55 pm |
| In-Class Quiz | 25% | Week 9; due 2 October 2026 at 11:55 pm |
| Android App Development and Individual Interviews | 40% | Due 16 October 2026 at 11:55 pm |
S2 has a 15% research-paper presentation due 21 August, a 20% Android design proposal and skeleton due 11 September, a 25% Week 9 in-class quiz due 2 October, and a 40% Android app development task with individual interviews due 16 October. No final examination or component hurdle is published.
What other students are asking about FIT5046
- Where can I find lecture notes or study guides for FIT5046 at Monash?
- The FIT5046 study guide in AskSia Library covers Mobile and Distributed Computing Systems in 11 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
- Is there a final exam in FIT5046?
- No final exam is listed in the offering this AskSia Library guide is built from; FIT5046 is assessed by Research Paper Presentation 15%, Android Application Design Proposal and Skeleton 20%, In-Class Quiz 25%, Android App Development and Individual Interviews 40%.
- What does FIT5046 cover on kotlin types, functions and null safety?
- In AskSia Library's FIT5046 guide, the Kotlin Types, Functions and Null Safety chapter explains static type · nullable type · higher-order function · encode data invariants and absence explicitly rather than through unchecked state.
- What does FIT5046 cover on jetpack compose state and recomposition?
- In AskSia Library's FIT5046 guide, the Jetpack Compose State and Recomposition chapter explains composable · recomposition · state hoisting · design UI as state plus events with predictable recomposition.
- What does FIT5046 cover on ubiquitous and context-aware computing?
- In AskSia Library's FIT5046 guide, the Ubiquitous and Context-Aware Computing chapter explains ubiquitous computing · context · context inference · use contextual signals without treating inference as fact.
Current FIT5046 dates
| Date | Item | Control |
|---|---|---|
| 21 August 2026 at 11:55 pm | Research Paper Presentation | 15% group-of-two presentation. |
| 11 September 2026 at 11:55 pm | Android Design Proposal | 20% proposal and skeleton prototype. |
| 2 October 2026 at 11:55 pm | In-Class Quiz | 25% Week 9 quiz. |
| 16 October 2026 at 11:55 pm | Android App and Interviews | 40% final major task. |
Dates are as published in the current course materials. Confirm exact deadlines and submission settings in the live LMS.
What FIT5046 covers
Start with Mobile and Distributed System Boundaries; use Mobile User-Interface Design and Accessibility as the turning point; finish by bringing the course together in Ethics, Privacy and Mobile-System Accountability.
Mobile and Distributed System Boundaries
mobile computing · distributed system · system boundary · map device, service, data and failure responsibilities before implementationDefine mobile computing
The course material gives this chapter a concrete anchor: Week 1 introduces mobile and distributed concepts together with Android setup.
- mobile computing
- distributed system
- system boundary
- Applying mobile computing
- Limits of distributed system and system boundary
Kotlin Types, Functions and Null Safety
static type · nullable type · higher-order function · encode data invariants and absence explicitly rather than through unchecked stateDefine static type
The course material gives this chapter a concrete anchor: Week 2 develops Kotlin foundations before deeper Compose work.
- static type
- nullable type
- higher-order function
- Applying static type
- Limits of nullable type and higher-order function
Jetpack Compose State and Recomposition
composable · recomposition · state hoisting · design UI as state plus events with predictable recompositionDefine composable
The course material gives this chapter a concrete anchor: Weeks 2-3 develop Compose from basics to state and interaction.
- composable
- recomposition
- state hoisting
- Applying composable
- Limits of recomposition and state hoisting
Ubiquitous and Context-Aware Computing
ubiquitous computing · context · context inference · use contextual signals without treating inference as factDefine ubiquitous computing
The course material gives this chapter a concrete anchor: Week 4 introduces ubiquitous and context-aware computing before the app platform sequence continues.
- ubiquitous computing
- context
- context inference
- Applying ubiquitous computing
- Limits of context and context inference
Navigation and Android Lifecycle
navigation graph · back stack · lifecycle · preserve state and destination semantics across navigation and recreationDefine navigation graph
The course material gives this chapter a concrete anchor: Week 5 focuses on Jetpack Navigation within the Android lifecycle.
- navigation graph
- back stack
- lifecycle
- Applying navigation graph
- Limits of back stack and lifecycle
Mobile User-Interface Design and Accessibility
mobile affordance · responsive layout · accessibility semantics · design and test touch, layout, feedback and semantics for diverse users and devicesDefine mobile affordance
The course material gives this chapter a concrete anchor: Week 6 focuses on mobile UI design before persistence and networking.
- mobile affordance
- responsive layout
- accessibility semantics
- Applying mobile affordance
- Limits of responsive layout and accessibility semantics
Room Persistence and Offline Data
Room database · entity · transaction · model entities, relationships and operations that survive process and network failureDefine Room database
The course material gives this chapter a concrete anchor: Week 7 introduces Jetpack Room for local persistence.
- Room database
- entity
- transaction
- Applying Room database
- Limits of entity and transaction
Retrofit Networking and Repository Design
HTTP API contract · Retrofit · repository · translate network responses into stable app state with cache and retry policyDefine HTTP API contract
The course material gives this chapter a concrete anchor: Week 8 covers Android networking and Retrofit.
- HTTP API contract
- Retrofit
- repository
- Applying HTTP API contract
- Limits of Retrofit and repository
Wireless Sensors and IoT Data
sensor measurement · Internet of Things · sampling policy · design sensing, communication and interpretation with calibration and energy limitsDefine sensor measurement
The course material gives this chapter a concrete anchor: Week 9 introduces wireless sensors within the mobile and distributed system.
- sensor measurement
- Internet of Things
- sampling policy
- Applying sensor measurement
- Limits of Internet of Things and sampling policy
Location-Aware Computing and Geofencing
location estimate · geofence · permission scope · connect accuracy and permission state to user-visible location behaviourDefine location estimate
The course material gives this chapter a concrete anchor: Week 10 focuses on location-aware computing after sensors and networking.
- location estimate
- geofence
- permission scope
- Applying location estimate
- Limits of geofence and permission scope
Ethics, Privacy and Mobile-System Accountability
informed consent · data minimisation · accountability · evaluate data, autonomy, inclusion and remedy across the app lifecycleDefine informed consent
The course material gives this chapter a concrete anchor: Week 12 closes the unit with ethics and mobile computing.
- informed consent
- data minimisation
- accountability
- Applying informed consent
- Limits of data minimisation and accountability
It is positioned as a mobile and distributed systems development unit.
Assessment moves from research interpretation to a designed and implemented Android app, ending with individual interviews rather than a final exam.
Assessment in fit5046 is distributed as follows: a 15% research presentation, 20% Android design proposal and skeleton, 25% in-class quiz, and 40% Android app plus individual interviews
The operational assessment conditions matter here.
No final examination appears in the current S2 structure; the final major task is the app and interview assessment.
What makes fit5046 demanding is concrete: maintaining correct state and user experience across Compose recomposition, navigation, persistence, network latency, device lifecycle and permission changes
Treat the fit5046 hurdle status as unconfirmed.
Check the current Monash Handbook and learning site for any component-level pass rule before relying on the overall mark.
For enrolment planning, For specified Software Engineering students, the current Handbook lists FIT2099, FIT3171 and FIT4165.
Start with Mobile and Distributed System Boundaries; use Mobile User-Interface Design and Accessibility as the turning point; finish by bringing the course together in Ethics, Privacy and Mobile-System Accountability.
Worked example · free
Design resilient venue loading
- 1Define remote, local and UI state owners.
- 1Represent loading, success, empty, stale and error states.
- 1Persist favourites transactionally in Room.
- 1Handle retry, rotation and process recreation.
- 1Audit permission, accessibility and privacy.
Key terms
- mobile computing
- Computation shaped by portable devices, variable connectivity, constrained resources and changing user context. This chapter uses the concept when students map device, service, data and failure responsibilities before implementation.
- distributed system
- Independent components communicating over a network without shared memory or a single failure-free clock. It helps explain the reasoning required to map device, service, data and failure responsibilities before implementation.
- system boundary
- Explicit division of responsibilities among device, platform, remote service, sensor and user. Its limit matters because a mobile app is not self-contained when identity, data or decisions depend on remote components.
- static type
- Compile-time description constraining values and operations accepted by a program expression. This chapter uses the concept when students encode data invariants and absence explicitly rather than through unchecked state.
- nullable type
- Kotlin type that explicitly permits absence and requires controlled handling before non-null use. It helps explain the reasoning required to encode data invariants and absence explicitly rather than through unchecked state.
- higher-order function
- Function that accepts or returns functions to express reusable behaviour. Its limit matters because non-null assertions and broad mutable types can bypass the language protections the design depends on.
- composable
- Declarative function describing UI from inputs and observable state. This chapter uses the concept when students design UI as state plus events with predictable recomposition.
- recomposition
- Selective re-execution of composables when observed state changes. It helps explain the reasoning required to design UI as state plus events with predictable recomposition.
- state hoisting
- Moving mutable state to a caller so ownership and events become explicit and components remain reusable. Its limit matters because mutable copies and side effects inside composition can create stale, repeated or contradictory behaviour.
- ubiquitous computing
- Computing embedded across everyday environments and interactions rather than concentrated in one visible device. This chapter uses the concept when students use contextual signals without treating inference as fact.
- context
- Information characterising user, device, activity, location, time or environment relevant to system behaviour. It helps explain the reasoning required to use contextual signals without treating inference as fact.
FIT5046 FAQ
Where do students usually lose marks in fit5046?
maintaining correct state and user experience across Compose recomposition, navigation, persistence, network latency, device lifecycle and permission changes
How is fit5046 assessed?
a 15% research presentation, 20% Android design proposal and skeleton, 25% in-class quiz, and 40% Android app plus individual interviews
What is the fit5046 final assessed-task format?
No final examination appears in the current S2 structure; the final major task is the app and interview assessment.
Does fit5046 have a hurdle or component-level pass rule?
Treat the fit5046 hurdle status as unconfirmed. Check the current Monash Handbook and learning site for any component-level pass rule before relying on the overall mark.
Which offering does this fit5046 guide cover?
It is aligned to Semester 2, 2026; confirm your enrolled class and timetable in the current institutional system.
What prerequisites or restrictions apply to fit5046?
For specified Software Engineering students, the current Handbook lists FIT2099, FIT3171 and FIT4165.
Questions students ask in each FIT5046 chapter
- What is the main task in Mobile and Distributed System Boundaries?
- Map device, service, data and failure responsibilities before implementation. Chapter 01 · Mobile and Distributed System Boundaries
- What is the main task in Kotlin Types, Functions and Null Safety?
- Encode data invariants and absence explicitly rather than through unchecked state. Chapter 02 · Kotlin Types, Functions and Null Safety
- What is the main task in Jetpack Compose State and Recomposition?
- Design ui as state plus events with predictable recomposition. Chapter 03 · Jetpack Compose State and Recomposition
- What is the main task in Ubiquitous and Context-Aware Computing?
- Use contextual signals without treating inference as fact. Chapter 04 · Ubiquitous and Context-Aware Computing
- What is the main task in Navigation and Android Lifecycle?
- Preserve state and destination semantics across navigation and recreation. Chapter 05 · Navigation and Android Lifecycle
- What is the main task in Mobile User-Interface Design and Accessibility?
- Design and test touch, layout, feedback and semantics for diverse users and devices. Chapter 06 · Mobile User-Interface Design and Accessibility
- What is the main task in Room Persistence and Offline Data?
- Model entities, relationships and operations that survive process and network failure. Chapter 07 · Room Persistence and Offline Data
- What is the main task in Retrofit Networking and Repository Design?
- Translate network responses into stable app state with cache and retry policy. Chapter 08 · Retrofit Networking and Repository Design
- What is the main task in Wireless Sensors and IoT Data?
- Design sensing, communication and interpretation with calibration and energy limits. Chapter 09 · Wireless Sensors and IoT Data
- What is the main task in Location-Aware Computing and Geofencing?
- Connect accuracy and permission state to user-visible location behaviour. Chapter 10 · Location-Aware Computing and Geofencing
- What is the main task in Ethics, Privacy and Mobile-System Accountability?
- Evaluate data, autonomy, inclusion and remedy across the app lifecycle. Chapter 11 · Ethics, Privacy and Mobile-System Accountability
How to prepare for the assessments
Retrieve the course map, practise the recurring method—define the mobile user journey, lifecycle and distributed data boundary, implement state through Kotlin, Compose and Jetpack components, then test process death, offline failure, permissions, privacy and device diversity—on changed scenarios, and verify every operational assessment detail in the live institutional system.
Your AI Mobile Computing tutor for FIT5046
Stuck on a hard FIT5046 question? Sia is AskSia’s AI Mobile Computing tutor — ask any FIT5046 Mobile and Distributed Computing Systems question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.