Campus Parcel Desk with Android and Kotlin: A 2027 Project Guide

The starting point for this Android and Kotlin exercise is a campus desk volunteer working with parcel records. Their question is specific: How many packages were collected by collection zone? Building a lifecycle-aware Android feature around that question gives the project a manageable scope and makes the result possible to verify.

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

Collected package counts describe completed handovers in synthetic data. Returned packages are separate, and no real addresses or recipient details belong in this practice fixture. For this exercise, one row represents one parcel. The stable key is record_id; collection_zone is the grouping or filtering label. The numeric package_count field uses packages. Accepted states are received, collected, returned.

The summary selects status collected and applies sum 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 parcel records and explain its effect on package_count.
• Lifecycle-aware work. Apply this choice to parcel records and explain its effect on package_count.
• Repository boundaries. Apply this choice to parcel records and explain its effect on package_count.

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": "parcel-desk-01",
    "collection_zone": "Main Desk",
    "package_count": 2,
    "status": "collected",
    "recorded_on": "2027-01-04"
  },
  {
    "record_id": "parcel-desk-02",
    "collection_zone": "Library Desk",
    "package_count": 1,
    "status": "received",
    "recorded_on": "2027-01-05"
  },
  {
    "record_id": "parcel-desk-03",
    "collection_zone": "Hostel Desk",
    "package_count": 3,
    "status": "collected",
    "recorded_on": "2027-01-06"
  }
]

Only the first and third records match collected. Their package_count values are 2 and 3; the full-fixture result is 5 packages, with 2 matching records. Selecting collection_zone = Main Desk leaves the first record, so the result becomes 2 packages, with 1 match. This provides two independent checks for the filter and aggregation.

The full-fixture output contract is:

{
  "matching_count": 2,
  "operation": "sum",
  "value": 5,
  "unit": "packages"
}

Check the result by collection_zone

The overall figure answers the all-records version of the question. Grouping by collection_zone produces the following separate expectations, using the same collected 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 parcel list, a collection_zone choice and a summary labelled in packages. 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 sum from collected 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 parcel records.

Find the mistake before polishing the result

A useful defect to introduce deliberately is: Returned packages are shown as successful collections. 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: Return one entry and verify that it never increases collected-package totals. Preserve before-and-after evidence. Add a missing collection_zone, a negative package_count, 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 sum value is 0. 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 campus desk volunteer question, the record definition and the expected calculation first. Then demonstrate a collection_zone 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 collection_zone 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 parcel records belong in the result?

Select records whose status is exactly collected and that satisfy the chosen collection_zone 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?

Return a zero total with a matching count of zero and a clear empty-result 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 package_count result is correct?

Reconcile the first and third sample records, then repeat the calculation for Main Desk 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 Bicycle Parking Register using Android and Kotlin, or compare Campus Parcel Desk using iOS and SwiftUI. These companion practice guides are part of the 2027 learning collection.