Keeping track of where your money goes shouldn't mean giving away your financial soul. When I started building Subra, I noticed a frustrating trend in the "FinTech" space. Every subscription manager wanted one thing: my bank login. While Plaid and similar integrations are powerful, they often feel like overkill for someone who just wants to stop getting hit by a $40 "surprise" annual charge for a tool they forgot they subscribed to.

Building Subra was an exercise in intentional simplicity. I wanted to create a tool that was fast, privacy-first, and felt like a native app without the friction of the App Store. Here’s how I tackled the technical hurdles of building a modern subscription detective.

The average person now loses hundreds of dollars a year to "vampire subscriptions"—trials that never got canceled or annual renewals that slip through the cracks. Most people don't need a complex budgeting engine; they need a dead-simple reminder system that works across all their devices.

My goal with Subra was to make adding a subscription as fast as sending a text message, while keeping the user's data entirely under their own control.

1. The PWA vs. Native App Dilemma

I wanted Subra to be accessible with one tap, but I didn't want to deal with the 30% "Apple Tax" or the week-long approval cycles of the App Store.

The Solution: I built Subra as a Progressive Web App (PWA). By leveraging service workers and a manifest file, Subra installs directly to the home screen. It works offline, updates automatically, and bypasses the store entirely.

The Benefit: Users get a "native" feel (no URL bar, splash screens) while I maintain the ability to ship updates in seconds.

2. Privacy-First Data Architecture

The biggest technical challenge was proving to users that I don't want their bank data. In most apps, the "sync" is the feature. In Subra, the lack of sync is the feature.

The Solution: I focused on a manual-entry flow that is actually faster than waiting for a bank API to load. By using Convex as the backend, I could ensure that data remains encrypted and isolated. Instead of "fetching" transactions, I built a predictive "Search & Suggest" engine that identifies common subscription brands (Netflix, SaaS tools, etc.) to minimize typing.

Insightful Data Visualization

Raw numbers are boring. To make Subra useful, I needed to turn a list of costs into Spending Insights.

The Approach: I used a "Spending Patterns" dashboard that breaks down costs by category and frequency. This allows users to see not just what they are paying for, but when the biggest hits to their bank account are coming. Seeing a "Total Annual Cost" vs. a "Monthly Cost" is often the "Aha!" moment that leads a user to hit the cancel button.

Building the pricing model for Subra was as much of a technical decision as the code itself. In a world of monthly fees, I wanted Subra to be a Lifetime Access tool.

I learned that users value ownership. By offering a "Pay Once, Own Forever" model, I aligned Subra's business goals with the user's goal: to stop paying recurring fees they don't need.

Subra isn't just about saving money; it's about digital hygiene. By starting small and focusing on a specific pain point—the "hidden subscription"—I was able to build a tool that has already helped over 1,000 users track millions in spending.

If you’re tired of the subscription treadmill, check out Subra.app and take control of your cash.