What I’m building next.

A growing expense history should become more useful, not harder to navigate. I’m adding search and practical filters to Overview first, then carrying the same way of finding things through the rest of Spenso.

• Search expenses by their description or tags
• Filter by date, category, tags, and amount
• Combine filters without turning the screen into a control panel
• Keep the same search experience wherever expenses appear

Spenso can already import and export expenses as CSV. The next pass is about making that foundation dependable when the file is large, something is interrupted, or the data came from somewhere less tidy.

• Preview proposed changes and catch duplicates before anything is saved
• Handle large expense histories without making the app feel stuck
• Keep the export format stable as Spenso evolves
• Make row and column problems clear enough to fix quickly

Spenso can now record one expense or several with Siri, confirm the result, and move a batch into the app for review. That part has shipped.

Next, I want to build on that foundation with more useful ways to bring Spenso into everyday Apple workflows.

• Expand the useful actions available in Shortcuts
• Home Screen and Lock Screen widgets
• Glanceable information without squeezing the whole app into a tile

Spenso should quietly notice expenses that show up on a rhythm, then get out of the way. This is about useful signals, not another budgeting system to maintain.

• Suggest likely subscriptions and repeating payments
• Point out when the usual amount changes
• Let you confirm or dismiss a signal in one step
• Keep reminders gentle and entirely optional

Shared expenses need a little more structure, but not a miniature accounting department. I’m thinking through spaces that are simple to join, clear about who added what, and easy to leave when the trip or project is done.

• Invite the people who actually need access
• Keep personal and shared expenses clearly separate
• See who added or changed something
• Make temporary spaces work just as well as long-running ones

This one is deliberately further out. The models and platform APIs are still moving, and I would rather wait for useful, private features than add an AI button just because everyone else has one.

• Prefer on-device work wherever it can do the job well
• Help clean up, search, and understand expense data
• Build on document capture instead of duplicating it
• Keep every suggestion visible, optional, and reversible