What designing Seabil taught us about recurring payments, offline workflows and keeping financial records under the user's control.
Many subscription management apps try to automate everything.
They connect to financial accounts, analyze transactions, synchronize information and attempt to identify recurring charges.
Those features can be useful. But they also introduce additional infrastructure, permissions and dependencies.
When developing Seabil, our Android subscription tracker at TSI Dev Studio, we explored a different approach:
What if tracking recurring payments didn't require access to a bank account, an online account or a remote database?
The result is a local-first application designed around manual control, renewal visibility and practical financial organization.
Here are several important design considerations behind that approach.
1. Start With the Actual User Problem
A subscription tracker doesn't necessarily need access to financial transactions to be useful.
For many people, the immediate problem is simpler:
- Which subscriptions are still active?
- How much does each service cost?
- When will the next payment happen?
- Which free trials are about to expire?
- How much am I committing to recurring expenses?
These questions can be answered with information provided directly by the user.
In Seabil, a subscription record includes details such as its service name, price, currency, billing frequency and renewal date.
This keeps the primary workflow understandable.
The application organizes information. It doesn't need to initiate payments, read bank transactions or interact with subscription providers.
That separation also makes the product's limitations clearer: Seabil cannot automatically cancel a service or detect a payment that the user hasn't recorded.
2. Local-First Is a Product Decision, Not Just a Storage Decision
Storing information locally changes the relationship between an application and its users.
In a cloud-first system, the service may be responsible for authentication, synchronization, remote storage and account recovery.
In a local-first subscription tracker, the developer can avoid many of those dependencies.
Seabil does not require a Seabil account or bank connection. Its subscription database remains on the Android device, without automatic cloud synchronization.
This approach provides several benefits:
Reduced external dependencies. The primary subscription-management workflow doesn't require a developer-operated backend.
Less information shared. The user doesn't need to provide banking credentials.
Control over recorded data. Users decide which services and payment details they enter.
Offline availability. Core subscription records can remain accessible without a network connection.
However, local-first also creates responsibilities.
Losing the device or deleting application data can mean losing records unless a usable backup exists.
A privacy-focused design must explain that tradeoff instead of pretending local storage eliminates every risk.
3. Reminders Are More Complicated Than They Look
A subscription tracker becomes more useful when it helps users act before a payment occurs.
But Android notifications require careful design.
The application needs to manage renewal dates, user-defined reminder preferences and the operating system's background execution restrictions.
A notification scheduled for a particular date is not a guarantee that every Android device will deliver it at the exact expected moment.
Battery optimization, notification permissions and device-specific restrictions can influence delivery.
Seabil provides local reminders for renewals, free trials and upcoming charges, while acknowledging that Android controls final notification delivery.
The broader engineering lesson is straightforward:
Never promise precision that the operating system cannot guarantee.
For time-sensitive workflows, clear expectations are part of good UX.
4. Multiple Currencies Should Not Produce Misleading Totals
Imagine a user tracking three subscriptions:
| Subscription | Monthly cost |
|---|---|
| Software service | $9.99 USD |
| Cloud storage | €4.99 EUR |
| Membership | £7.99 GBP |
A simplistic implementation might add these numbers and display a total of 22.97.
But 22.97 of what?
These amounts use different currencies and cannot be meaningfully combined without exchange rates and a clearly defined conversion method.
Seabil keeps currency-specific totals separate rather than inventing exchange rates.
This is a useful principle for financial interfaces:
An incomplete but accurate financial picture is better than a complete-looking but misleading one.
Not every feature needs maximum automation.
Sometimes correctness means refusing to present a number that lacks a defensible meaning.
5. Smart Input Without Continuous Data Collection
Manual entry offers control, but it can become repetitive.
One way to reduce friction is to help users process information they deliberately provide.
Seabil includes Smart Paste, which examines text manually pasted into the application and identifies likely subscription details.
Depending on the input, those details may include a service name, amount, date or billing frequency.
The processing takes place locally.
Users verify the suggested information before saving it.
Smart Paste does not continuously monitor the clipboard or upload pasted text to a Seabil server.
This creates a useful middle ground between completely manual data entry and extensive background collection.
The general design principle is:
Assist with the information the user chooses to provide, rather than collecting more information than the task requires.
6. Separate Simulations From Real Financial Records
Another design challenge involves hypothetical financial decisions.
Users may want to know:
- What happens if I cancel two subscriptions?
- How much could I save by pausing a membership?
- What if a service increases its price?
- Would replacing one subscription with another reduce expenses?
These are simulations, not actual financial transactions.
Seabil's Scenario Lab allows users to explore potential changes without modifying their real subscription records, reminders or payment history.
That separation matters.
A hypothetical cancellation should never accidentally become a real cancellation record.
An experimental price change should not silently overwrite the price the user actually pays.
For developers, this illustrates a broader principle: separate exploratory operations from authoritative user data.
7. Backup and CSV Export Solve Different Problems
Local storage makes backup design especially important.
But backup and export are not interchangeable.
Seabil Lifetime provides password-protected encrypted backups, with restoration options that include Replace and Merge.
These operations are designed for recovering application records.
CSV export serves a different purpose.
A CSV file is useful for viewing information in a spreadsheet or performing separate analysis.
However, CSV is not an encrypted Seabil backup and cannot restore the application's database.
This distinction should be explicit in any application dealing with personal records.
Users need to understand which files support recovery and which files are intended for external viewing.
Good privacy design includes explaining what happens after information leaves the protected application environment.
8. Build a Sustainable Product Without Another Recurring Fee
There is also a product-design question.
Should a subscription tracker require its own subscription?
For Seabil, we chose a different model.
The free version supports up to three subscriptions, allowing users to explore the core workflow.
An optional one-time Lifetime purchase unlocks unlimited subscription tracking and additional features.
There is no recurring Seabil subscription fee.
This does not mean recurring pricing is inherently wrong for every software product.
Some applications have substantial ongoing infrastructure or service costs.
But for a local-first utility with no developer-operated subscription database, a one-time purchase can be a reasonable product choice.
The monetization model should reflect the value delivered and the operating model behind it.
9. The Broader Lesson: Good Software Doesn't Always Need More Access
Modern software development often focuses on adding capabilities.
More automation.
More integrations.
More synchronization.
More background processing.
But every additional capability should justify its complexity and data requirements.
Seabil demonstrates one possible approach to a narrower problem: helping people understand recurring expenses without building the workflow around bank connections or remote accounts.
It does not eliminate the need for user input or responsible backup habits.
Instead, it makes those responsibilities visible.
For developers, that may be the most useful lesson:
The right architecture is not necessarily the one that collects the most information. It is the one that solves the intended problem with appropriate complexity, reliable behavior and clear boundaries.
About Seabil
Seabil is an Android subscription and recurring bill tracker developed by TSI Dev Studio.
It includes local subscription records, renewal reminders, Smart Paste, spending insights, Scenario Lab and optional premium features.
Explore Seabil: https://tsidevstudio.com/apps/seabil
Complete documentation: https://tsidevstudio.com/apps/seabil/guide?lang=en
TSI Dev Studio: https://tsidevstudio.com
Developed by TSI Dev Studio — an independent Android software studio focused on practical, privacy-conscious applications.
This article discusses product-level design decisions and publicly documented behavior. It is not a disclosure of Seabil's private source code or undocumented internal implementation.
Top comments (0)