pro-never-gates-the-core-loop

Summary

Adding expenses, splitting them any of the four ways, settling up and exporting your data are free without limit, permanently.

Why it matters

It is the reason somebody leaves Splitwise for this. A "10 expenses a day" row was once in the paywall table and had to go: it is the exact limit this app exists to not have. How a bill divides is part of splitting it, so a paywall between "equally" and "Arjun ate twice as much" would sit in the middle of the core loop.

Implications

• Pro reaches exactly three places in the UI: the insights-history veil on spending, the currency row on account and group-new, and the recurring rules plus receipt photos.
• Export is never Pro and covers the WHOLE ledger. An export that silently stopped at 200 rows would be worse than none, because the user would believe they had their data.
• Pro lapsing PAUSES recurring rules rather than silently not running them — rent quietly going unlogged is a worse outcome than a paywall.
• A row in the paywall table may only describe something the app does today. It is shown to somebody about to pay, so a row for an unbuilt feature is a false claim, and one the stores reject builds over.

Related

• pricing — the canonical table
• plans — the screen that renders it
• recurring — what a lapse looks like
• spending — the only veil

Sources

• src/app/pricing.tsx
• src/app/account.tsx