Product / Mobile
2026 · ACTIVE DEVELOPMENT
PROJECT / 03
RECURRING PAYMENTS · MOBILE PRODUCT
A recurring-payment app with persistent billing state, payment tracking and synchronized reminders.
Drift persistence · synchronized reminders
Product / Mobile
2026 · ACTIVE DEVELOPMENT
Active development · Android-first recurring-payment application
Case study / 2026
The application is designed around recurring financial commitments such as subscriptions and regular payments. The goal is to make billing state, amount, currency, payment timing and reminder behavior explicit instead of treating every recurring charge as an isolated list item.
The application uses explicit add and update flows for recurring payments rather than allowing arbitrary state changes. Optional values such as payment nicknames are normalized, while currency input is validated before persistence so invalid changes do not enter the stored payment state.
Recurring-payment data is persisted through a Drift-backed repository layer. Repository behavior and round-trip updates are tested so edits, cleared optional values and stored payment state remain predictable across application and persistence boundaries.
The recurring-payment workflow also coordinates notification behavior. Valid payment changes can propagate to persistence and reminder scheduling, while rejected changes are stopped before they create additional repository or notification side effects.
CASE EVIDENCE

DASHBOARD
The dashboard highlights the next payment, quick actions and grouped monthly totals across tracked subscriptions.

SUBSCRIPTIONS
The subscriptions screen presents active services such as ChatGPT, Disney+ and Netflix in a clear list view.

RECURRING PAYMENT
The recurring payment form captures title, amount, cycle and currency in a focused creation flow.

SUBSCRIPTION DETAIL
The detail screen shows billing amount, cycle, category and the core attributes of an individual subscription.