THE CHALLENGEWhere the simple version breaks.
A monthly price does not tell the whole story: an annual plan charges in one payment, a weekly plan can bill five times in a month, and a trial may require cancellation before its renewal date. Renew brings these different timelines together so people can review a plan before the next charge.
THE WORKFLOWA clear path through the task.
Choose a starting currency and add a subscription with its price, billing cycle, renewal date, category, and cancellation lead time. The overview separates monthly averages from charges actually due this month. Search and filter active plans, trials, cancelled records, and a review list; use the calendar to inspect a specific day; then open a plan to edit it or follow its provider management link. Settings provide budgets, native reminders, and a JSON export through the system share sheet. A separate demo space supports exploration without replacing personal records.
ENGINEERING DECISIONSThe details that make it hold.
01Separate monthly cost from cash due.
Prices are stored as integer minor units. Annual and weekly plans are normalized for monthly comparisons, while calendar forecasts enumerate actual billing dates. Currency totals remain separate rather than implying an exchange rate that the app does not provide.
02Preserve the original billing anchor.
A January 31 monthly plan moves to the last valid day in February and returns to March 31. An annual February 29 plan returns to leap day when possible. These cases are covered by automated recurrence tests.
03Protect saved records before rendering.
AsyncStorage holds subscriptions and preferences on the device. Snapshot validation checks dates, billing cycles, prices, currencies, reminder settings, and duplicate IDs. Invalid snapshots stop loading and further writes, preserving the original data instead of silently replacing it.
04Make review useful without claiming cancellation.
People can flag plans for review, record a cancellation status, and open an HTTPS provider link. Renew explains that changing a record does not cancel billing. Demo records are held separately from personal subscriptions.
05Schedule reminders around the decision deadline.
Native notifications use the earlier of the renewal reminder and cancellation deadline, at 9 AM local time. The queue is bounded to the earliest 60 eligible reminders and refreshes when the app is reopened. Browser previews do not deliver native reminders.
06Prepare a repeatable release path.
Expo Router provides URLs for the main app sections while preserving in-memory state. EAS profiles cover development, internal preview, and production builds. A release guide records the remaining signing, store metadata, privacy policy, and physical-device checks.
VERIFICATIONBehavior, checked.
Local validation passed Expo lint, TypeScript, and 11 automated tests covering recurrence, invalid dates and prices, cancelled plans, saved-data corruption, duplicate IDs, and safe defaults. A production web bundle also exported successfully. Physical-device reminder delivery, native cloud builds, and App Store or Google Play submission have not yet been verified.
CURRENT SCOPEWhere this project stands.
A development preview with local device storage and manually entered billing details. No bank connection, automatic subscription discovery, payment processing, cloud sync, or automatic cancellation is implemented. The cover remains labelled illustrative artwork. There is no public distribution link, and no user adoption or savings metrics are claimed.