I built subskunote — a family subscription tracker PWA (Japanese-first)
Hi IH đź‘‹
I just launched subskunote, a small PWA for keeping a family's subscriptions from sprawling out of control.
The problem I had: in our household, Netflix is shared, Apple Music is on my kid's own account, a couple of services are under my partner's name, and one I genuinely couldn't remember who was paying for. Per month it looks small; per year it was over ¥100,000 across 4 people — with no single place to see "who pays for what."
Budgeting apps exist (Money Forward, Zaim), but they're built for full household accounting. I only wanted subscriptions and fixed costs, grouped by person.
What subskunote does differently:
Member slots — create person labels (dad / mom / kid / shared) and attach each subscription to one. You see who pays for what, and the yearly total, in one screen.
Payment-method-aware cancel links — when you cancel, the right path differs by how you subscribed (card → the service's page, App Store → iOS settings, Google Play, carrier billing). subskunote stores the payment method per subscription and jumps you straight to the correct cancellation page, so you don't have to google it every time.
Renewal reminders 3 days and 1 day before a subscription renews (Web Push + email), so "it renewed before I noticed" happens less.
Stack: Next.js 15 (App Router) + Supabase (RLS) + Stripe + Serwist for the service worker. iOS PWA Web Push was the fiddliest part — it needs the app added to the home screen on iOS 16.4+.
Pricing: free for up to 3 member slots; ÂĄ380/mo (tax incl.) for Pro. 14-day trial, no card required.
It's Japanese-first for now (the target users are Japanese households), but the build notes are things I'd love feedback on from anyone who has shipped a PWA with Web Push.
Live: https://subskunote.dev-tools-hub.xyz
Happy to answer anything about the member-slot data model or the iOS Push setup — and I'll be hanging around the forum returning the favor on other folks' launches.
This is a strong niche because it is not just “track subscriptions.” The real pain is household ownership confusion: who pays, which account owns it, and where to cancel when the payment path is different.
I’d probably lean harder into that in the positioning. “Family subscription tracker” is clear, but the sharper promise feels closer to: “see who pays for every subscription before another renewal slips through.”
The member-slot idea is the strongest part because it makes this less like a budgeting app and more like a household subscription control panel.
For early users, I would not target broad budgeting people. I’d target Japanese parents or couples already managing shared streaming, kids’ app subscriptions, mobile carrier billing, and App Store/Google Play renewals. That is where the pain is specific enough to pay ¥380/mo.
If you test one thing next, I’d test whether the homepage makes the yearly waste feel obvious fast. The ¥100,000/year angle is strong because it turns a small monthly annoyance into a real household money problem.