Murphy's CountDown is the kind of software whose value is obvious only after performing the underlying task repeatedly. Closing a cash register requires simple arithmetic, but the repetition, denomination handling, and need to leave the correct starting drawer make small mistakes easy.
Employees enter the count of each bill and coin denomination in a drawer; the app calculates the total and explains what to remove or keep for the next shift. Its purpose is to remove repetitive cash-register arithmetic from a real workplace routine.
The question behind Murphy’s CountDown
The app was designed from inside that workflow. Instead of behaving like a general calculator, it asks for the count of each bill and coin, totals the drawer, and converts the result into exact instructions about what should be removed or retained. Cash-handling employees doing a standard register countdown. The project is independent and should not imply endorsement by Papa Murphy’s.
How Murphy’s CountDown took shape
The earliest version was prototyped in Python and then translated into a SwiftUI iOS application through an early ChatGPT-assisted workflow. That progression matters because the app predates integrated coding agents: Josiah defined and tested the behavior while moving code, errors, and corrections between tools. Josiah identified the workflow, defined the calculation and instructions, iterated the interface, tested it at work, and shipped the application.
What the evidence supports
The app reached the App Store and was used by some coworkers for a period of time. Its scale is modest, but its product logic is strong. It replaced a repetitive workplace calculation with a purpose-built instruction, reached the App Store, and was used by coworkers—evidence that a very small tool can still complete the full path from observed friction to real handoff.
Current usage and listing status are unknown, and the exact relationship between Murphy’s CountDown and an older Register Countdown artifact needs to remain merged and clearly explained. A fuller retrospective will preserve the listing, screenshots, major build decisions, current status, and the boundary between the independent app and the employer brand.