Swift verification
374 tests
Across 46 suites in the latest reviewed snapshot.
Subscriptly is an iOS app for subscriptions and other recurring payments. Its value is not a decorative dashboard; it is the care taken with dates, currencies, imports, backup, recovery, and the choice between local-only and private iCloud data.
Swift verification
374 tests
Across 46 suites in the latest reviewed snapshot.
Shared-core verification
247 checks
Run against both JVM and iOS Simulator arm64 targets.
UI release checks
9 tests
Focused on release-critical user journeys rather than vanity coverage.
Distribution
Internal TestFlight
Not a public beta and not an App Store release.
Recurring payments become difficult at the boundaries: a renewal anchored near month-end, a currency conversion that must not drift, or a restore that must preserve both money and history.
I modelled those rules directly instead of spreading them across views. The iOS product uses a shared Kotlin domain core for billing rules, while the interface, local persistence, and optional private iCloud path remain native to Apple platforms.
Amounts use integer minor units and explicit currency handling, avoiding floating-point values in billing logic.
Anchor-based renewals and time-zone-free calendar days prevent an ordinary date from shifting because a device crosses a time zone.
Backup, restore, conflict handling, and the local-versus-private-iCloud choice are explicit product paths rather than hidden implementation details.
For recruitment review, I can show how the product rules connect to release verification while keeping the source repository private.
Subscriptly is intentionally presented as substantial work in progress.
I can walk through the domain model, architecture, recovery paths, and selected test evidence during a genuine recruitment process. The repository itself remains private.