If the embed does not load, the video is also available directly on YouTube.
What the review covers
The artifact under review is Mere Metrics: Weight Tracker, a native Android application originally developed in Java during a mobile architecture and programming course. It is a small but complete application: it supports account creation with hashed credentials, persistent storage of users and goals, daily weight entries with full create, read, update, and delete behavior, a history screen, and a runtime-permission SMS workflow that notifies the user when a goal is reached.
The review is structured in three parts, following the standard code-review shape of what exists, what is wrong with it, and what I intend to do about it:
Existing functionality
A guided walkthrough of the application’s features as they exist today: authentication, data entry and editing, the history view, and the goal-notification flow. It also covers the underlying architecture and persistence layer.
Code analysis
An honest look at the parts of the codebase that do not age well. The most significant issues are structural: user-interface fragments hold responsibilities that do not belong to them, dates are stored in a display-friendly format (MM/dd/yyyy) that has to be re-parsed at runtime to sort history correctly, and the history screen constructs its rows manually instead of using a list-recycling component. The persistence layer is functional but minimal, with a schema upgrade path that drops and recreates tables rather than migrating their data.
Planned enhancements
For each of the three portfolio categories, the review describes the intended enhancement at a level of detail suitable for a peer or a manager to evaluate the plan. The three planned directions are an architectural refactor, an analytics-focused upgrade of the history feature, and a migration to a typed, versioned persistence layer. These are the three pieces of work documented in the narratives that follow.