Assignment Submission with Android and Kotlin: A 2027 Project Guide

A teaching assistant needs a trustworthy answer to a small operational question: what is the highest submitted revision in the selected assignment? This Android and Kotlin project turns that question into a lifecycle-aware Android feature. The useful result is a traceable decision rule, a clear output and evidence that a change behaves as expected.

This is a 2027 study-edition project brief. All example records and operational situations are fictional. Start with basic Android and Kotlin knowledge, the ability to inspect structured data and a local practice environment. The complete first version should answer the stated question before adding accounts, real integrations or additional screens.

Define the project rule

Revision numbers are positive integers, but the maximum revision is a version indicator rather than a measure of student ability. A withdrawn submission must not become the current submitted revision. For this exercise, one row represents one submission. The stable key is record_id; assignment_name is the grouping or filtering label. The numeric revision_number field uses revisions. Accepted states are draft, submitted, withdrawn.

The summary selects status submitted and applies max to the selected numeric values. Keep this definition visible in the interface, response or report so another learner can reproduce it. Use positive finite values in the starter fixture and define any future zero or missing-value policy explicitly.

Choose the Android and Kotlin approach

Represent the screen as state rather than scattering updates across unrelated callbacks. Keep domain operations separate from UI rendering and state clearly which values should survive recreation. Start with a local fake repository and add networking only after validation works. Test interrupted interactions so a recreated screen does not show a success that never happened.

The three design decisions to explain in your project notes are:

• Screen state ownership. Apply this choice to submission records and explain its effect on revision_number.
• Lifecycle-aware work. Apply this choice to submission records and explain its effect on revision_number.
• Repository boundaries. Apply this choice to submission records and explain its effect on revision_number.

Work through a small sample

The three records below are deliberately small enough to inspect by hand. They are a compact specification for the data shape and expected result, and can later be expanded into a larger synthetic fixture.

[
  {
    "record_id": "assignment-submissions-01",
    "assignment_name": "Validation Exercise",
    "revision_number": 1,
    "status": "submitted",
    "recorded_on": "2027-01-04"
  },
  {
    "record_id": "assignment-submissions-02",
    "assignment_name": "Query Review",
    "revision_number": 3,
    "status": "draft",
    "recorded_on": "2027-01-05"
  },
  {
    "record_id": "assignment-submissions-03",
    "assignment_name": "Interface Prototype",
    "revision_number": 2,
    "status": "submitted",
    "recorded_on": "2027-01-06"
  }
]

Only the first and third records match submitted. Their revision_number values are 1 and 2; the full-fixture result is 2 revisions, with 2 matching records. Selecting assignment_name = Validation Exercise leaves the first record, so the result becomes 1 revisions, with 1 match. This provides two independent checks for the filter and aggregation.

The full-fixture output contract is:

{
  "matching_count": 2,
  "operation": "max",
  "value": 2,
  "unit": "revisions"
}

Check the result by assignment_name

The overall figure answers the all-records version of the question. Grouping by assignment_name produces the following separate expectations, using the same submitted rule. The middle group has a record in the source fixture but no qualifying observation.

Use this breakdown when answering the group-level question. Compare like-for-like units and keep the matching count visible, especially for averages. A different filter changes which records enter the calculation; it does not change the meaning of the metric.

The code blocks describe sample data and an expected result. Implement the surrounding feature using the installed version of your chosen tools, then save the actual run evidence separately from these expectations.

Build the feature in three passes

1. Design the smallest usable screen

Show the submission list, a assignment_name choice and a summary labelled in revisions. Keep the primary action reachable with the keyboard open. Use the same fixture in a fake repository before introducing network or persistence dependencies.

2. Separate state from the calculation

Represent loading, ready, empty and error states explicitly. Derive the max from submitted entries in one domain function. Keep the user selection stable when the screen redraws and make a pending save visibly different from a confirmed save.

3. Test interruption and recovery

Change the filter, leave the screen, return, and repeat a save action. Decide what should survive navigation or recreation. A failed operation needs a retry path that preserves useful input while preventing accidental duplicate submission records.

Find the mistake before polishing the result

A useful defect to introduce deliberately is: The screen reports the number of rows as the latest revision. First reproduce it against the fixture, then identify the smallest rule or state transition that explains the mismatch. Fix that boundary and rerun the full-fixture and selected-label examples. This creates a stronger explanation than changing several unrelated parts until the screen looks right.

The scenario-specific acceptance check is: Add a second revision and check the maximum rather than the row count. Preserve before-and-after evidence. Add a missing assignment_name, a negative revision_number, an unrecognised status and a duplicate record_id as separate invalid cases. Define the rejection or duplicate-handling policy before testing, and verify that invalid input does not silently change valid existing records.

Check the Android and Kotlin concerns as well:

• Recreating a screen must not duplicate an operation.
• A cancelled request must not show success.
• Restored filters must match the visible result.

For an empty filter match, the expected max value is undefined (no matching observations). Keep matching_count at zero. This distinction prevents an empty dataset from being interpreted as a measured observation.

Explain the finished work in a portfolio

Show the teaching assistant question, the record definition and the expected calculation first. Then demonstrate a assignment_name filter and the acceptance check. Include the fixture, setup instructions, chosen tool versions, actual test output and one remaining limitation in the repository. If you show a screenshot, pair it with the input that produced it. Another learner should be able to repeat the same result from a clean checkout.

For a focused extension, add a second assignment_name selection and compare the two groups using the same rule. Specify how missing groups appear and keep the original fixture as a regression case. Expand scope only after the current calculation, state handling and recovery path remain understandable.

Questions learners often ask

Which submission records belong in the result?

Select records whose status is exactly submitted and that satisfy the chosen assignment_name filter. Other states remain in the source data and can have separate summaries. Follow the domain rule above when a record changes state.

What should happen when no records match?

Treat the empty result as undefined and show a clear no-observations message. Keep the applied filter visible so the user can change it. Avoid using a loading indicator for a completed request that simply has no matching data.

How can I prove the revision_number result is correct?

Reconcile the first and third sample records, then repeat the calculation for Validation Exercise alone. Save both expected and actual outputs, and rerun the scenario-specific acceptance check after making a change.

Continue learning with Groot Academy

Use this exercise as a concrete discussion point when choosing a learning path. Browse the current Groot Academy course directory and ask about the current syllabus, learning mode and project practice. Course availability and batch details should be confirmed directly with the academy.

For implementation details, consult the official Android and Kotlin documentation matching the tools you install. This project defines an original practice brief; it does not depend on a forecast about 2027 software releases.

Continue with Project Milestone using Android and Kotlin, or compare Assignment Submission using iOS and SwiftUI. These companion practice guides are part of the 2027 learning collection.