Public beta on TestFlight · iOS 26.2+

Finely

Know what your month is really costing you.

Join the TestFlight beta
Finely Home screen showing the current period
  • Finely Home screen showing the current period
    Home Balance, available-to-spend context, upcoming commitments, and one useful signal for the month.
  • Finely Month Review screen
    Month Review A reusable review turns recorded activity into income, spending, savings, and category context.
  • Finely Activity screen listing transactions
    Activity Recorded transactions and due commitments share one chronological surface with full-history search.
  • Finely Statistics screen for the year
    Statistics Categories, merchants, savings, and period comparisons expose patterns without changing the underlying facts.
  • Finely New Transaction form
    Transaction One-off and recurring movements enter through an editable native form with explicit financial meaning.
  • Finely Profile screen with privacy controls
    Profile Accounts, privacy controls, export, appearance, entitlement, and sync status stay visible.
  • Finely Analysis screen answering a spending question
    Analysis A question in plain language is routed to app-owned calculations that produce the answer.

A balance explains today. A period explains the decision.

Personal finance becomes useful when past activity and future commitments stop competing for attention. Finely keeps both visible and works out what they leave you for the current period, without asking you to reconcile raw accounting data.

Recorded money, what already happened (income, expenses, and transfers), plus committed money, what is already planned (subscriptions, fixed charges, and expected income), gives the current period: what is still available. On the period's timeline, recorded money fills the days up to today and committed money the days until the period ends.

From input to understanding

Each screen answers a different question, but none keeps its own version of the ledger. One path runs from capture to an explainable decision.

Five steps: 1. Capture, from manual entry, recurring declarations, or CSV import. 2. Consolidate, through one write path for every change. 3. Project, recorded and future movements in one order. 4. Understand, in Home, Activity, and Statistics. 5. Ask and act, a plain-language question answered by exact, app-owned calculations.

One source of truth, several ways to read it

Screens never merge stored and scheduled money on their own. Every change goes through one write path into SwiftData, and one read projection builds the picture every screen shares.

Manual entry, recurring setup, CSV import, and Siri and Shortcuts all write through one write path, which owns every change. It stores facts in SwiftData: recorded transactions and recurring rules, kept separate. A read projection merges recorded and forecast movements once, in order; Home, Activity, Statistics, and Analysis all read from it. Projected rows are never stored.

How a transaction is written once and read back everywhere is the subject of The Ledger Behind Finely.

Forecast the future, never rewrite the past

A recurring charge is useful before it happens, but it only becomes history when it is due. Finely keeps projection and persistence apart, so planning stays current while completed periods stay trustworthy.

A monthly subscription of 9.99 euros rises to 12.99 euros. Charges from March to June were written once when they fell due, and their amount never changes. From today, July to October are derived from the recurring rule each time a period is read, at the rule's current price, and are never stored. Today falls in June: editing June's charge updates the series from here on, while earlier charges can no longer be edited.

The difficult work sits between the screens

  • Local financial truth

    SwiftData stores facts and domain services derive meaning, so balances, periods, projections, and comparisons stay deterministic and testable.

  • Controlled import

    Column mapping, category inference, and duplicate detection happen before one batched save.

  • Paid access

    StoreKit 2 transaction updates and current entitlements drive Pro features, not optimistic purchase UI state.

  • Privacy and continuity

    Amount masking, an optional app lock, export, and sync status stay visible to the person using the app.

End-to-end ownership

I set the product direction, design the interaction, model the financial domain, build the UIKit architecture, define persistence and monetization boundaries, test difficult calendar behavior, and prepare the app for release. Finely is in public beta on TestFlight; its evidence is the completeness and coherence of the system being built.

Articles about Finely

Finely

The Ledger Behind Finely

How Finely stores only transactions and recurring rules, writes each charge exactly once, and gives every screen the same list of past and upcoming money.

8 min read
Finely

An On-Device Assistant That Never Makes Up a Number

How Finely answers questions about your money on the iPhone: Apple's on-device model only works out what is being asked, and Finely calculates every amount from your own transactions. Without Apple Intelligence, simple rules take the model's place.

7 min read
Finely

Adding Transactions to Finely from Siri and Shortcuts

How Finely turns a spoken sentence or an Apple Pay payment into a transaction: it never guesses the amount, reads a spoken transaction back before saving it, and only says it was added when the save really worked.

5 min read

Finely privacy policy