App Review — PRODTECH Assignment

Becoming

A life companion app for people figuring themselves out in their 20s

Loaded SRC_URL

https://producingtechnology.com/65-apps/tangerica_31877_15200420_becoming_json_app.html

App Behavior

Becoming is a JSON-powered mock life-companion dashboard aimed at people in their early 20s. The page loads a user profile (Erica, qt48) from built-in mock data. The UI is split into two columns: Identity Snapshot on the left and Mocked Features on the right, which contains interactive panels for a daily check-in, a memory anchor, and a growth timeline.

Identity Snapshot

Displays static profile data from JSON: preferred name, NetID, location, current life phase, academic background tags, themes, and a core question ("Who am I becoming?").

Daily Check-In

Lets the user set a mood (text field), energy level (slider 1–10), stress level (slider 1–10), and a short reflection (textarea). Prefilled with example values from the JSON.

Save Check-In

Clicking "Save check-in" updates the status bubble under the app title to confirm the saved values (e.g., mood "helpless", energy 1, stress 10). The Mood field in the Daily Check-In panel also updates to reflect the saved input.

Reset Example

Resets all Daily Check-In fields back to the original JSON example values.

Memory Anchor

Displays a static memory entry from the JSON: a title ("Heytea milk tea"), a type ("comfort"), and a meaning ("Consistency during uncertainty."). No user editing available.

Growth Timeline

Shows JSON-seeded timeline entries (e.g., 2026 New York, 2023 Undergrad NYC). An "Add current reflection" button appends the current Short Reflection as a new timeline entry — but only if the field is non-empty.

Things That Didn't Work As Expected

Growth Timeline is not sorted in descending chronological order. New reflections added via "Add current reflection" are inserted between the most recently added entry and the original 2023 sample entry, rather than always appearing at the top. The timeline should consistently show the most recent entries first.
"Add current reflection" button is visually disconnected from the input. The button appears far below the Short Reflection textarea, with the Growth Timeline section in between. This makes the spatial relationship between the input and its action button unclear — users may not immediately understand that the reflection text feeds into the timeline.
Identity Snapshot and Memory Anchor are fully static. Neither panel allows any user editing or input. While this may be intentional for a mock, there is no affordance or explanation telling the user these fields are read-only, which could create confusion about what is interactive.

Prompt to Improve the App

You are improving a JSON-powered life companion app called Becoming, designed for people in their early 20s navigating identity and growth. Please make the following improvements: 1. TIMELINE SORT ORDER: Always insert new Growth Timeline entries at the top of the list (most recent first). When "Add current reflection" is clicked, prepend the new entry above all existing ones, using the current year and a placeholder location (e.g., "Now") if no location is available. 2. LAYOUT — ADD REFLECTION BUTTON: Move the "Add current reflection" button to be directly beneath the Short Reflection textarea, before the Growth Timeline section begins. Add a subtle visual connector (e.g., a small arrow or label "↓ Adds to your timeline") to make the relationship between input and action explicit. 3. READ-ONLY INDICATORS: Add a subtle "view only" or lock icon label to the Identity Snapshot and Memory Anchor panels so users understand immediately that these sections are populated from their profile data and cannot be edited here. 4. MEMORY ANCHOR — BASIC EDITING: Allow the user to edit the Memory Anchor fields (title, type, meaning) inline, with a "Save" button that updates the in-memory JSON state and reflects the change in the status bubble (similar to how Save check-in works for the Daily Check-In panel). Keep the existing warm, muted earth-tone visual design, the two-column layout, and the JSON-driven architecture. Do not remove any existing features.