[FEAT] Subcategories for Better Expense Flow (Inspired by MoneyFlow)

[yhpq5tt5fv-png]

Description

Hi there,
I wanted to share my appreciation for your app. It’s rare to find a product that is both extremely simple to use and so well designed. The interface feels clean, consistent, and very polished. Great work.

I’d like to suggest a feature that could further improve the expense tracking experience: support for subcategories.

For example, similar to how it’s implemented in the MoneyFlow app (see attached screenshot), where you can have:

  • Home
        • Rent
        • Electricity
        • Furniture
        • Renovation
        • Household items
• Shopping
       • Shoes
       • Accessories
       • Underwear

This kind of structure makes it easier to:

• keep categories organized and readable

• analyze spending with more precision

• avoid having too many flat main
categories

I believe subcategories would add real value, especially for users who want deeper insights without cluttering the main category list.

Thank you for your work and for considering user feedback.

Additional Context

No response

[sadespresso]

Hello there! Thank you for sharing!

The thing is, I really don't want to add subcategories, it's been requested many times, but it will add one extra tap, and right now, we already have to perform a lot of actions to record a single transaction.

Recently, Flow got tags, which further adds a way to organize your transactions.

I can tell you it's not coming anytime soon. I already have pile of things that are need to be done, and I don't have much time at the moment :( . I will consider it in the future.

Let's keep the issue open so more people might add in weight.

[yhpq5tt5fv-png]

Thank you for the detailed and honest reply, I really appreciate the transparency.

I completely understand your concern about adding extra taps and keeping the transaction flow fast and simple. That philosophy is actually one of the reasons I like Flow so much.

Tags are definitely a good step and already help with organization. My thought with subcategories was more about structuring the category list itself rather than adding complexity during transaction entry. Ideally, this could be optional or handled in a way that doesn’t affect the speed of adding a transaction for users who don’t need it.

That said, I fully respect your current priorities and workload. It’s good to know your reasoning and the direction you’re aiming

Thanks again for taking the time to respond and for continuing to work on Flow.