Shared Tabs are slow for large lists (n+1)?

Shared tabs seem to get slower the larger they get.

Could you not just get a joint account? Sounds like it would be far simpler and less of a huge chore in administrating your mega list.

2 Likes

We use our Shared Tab exactly like this, it works so well for us.
The joint account is for set house bills that we pay a set amount in each month.
The Shared Tab is our monthly discretionary spending, groceries, eating out etc.
It’s a great system.

And I agree, the longer it gets the slower the tab gets. We’ve found if we ā€˜settle up’ once a week it gets quicker.

Interesting that yours appears to get quicker if you settle up. We’re quite regularly back to level but rarely zero. I wonder how settling up might change the speed :thinking:

We just overshoot and then later correct.

I’m wondering if its not an n+1 query / doing the sums from the beginning, but perhaps sending all the data and letting the device do the maths. I expect that’d be a big blob of data to send in my case.

I just noticed it was one or two seconds longer when on a mobile connection.

Either way I’d love a chance to hear thoughts from anyone technical or product at Monzo. Even if a fix or iteration is a way off.

Definitely try settling up and seeing if it’s quicker.
I’m guessing it’s like you say, once you settle up there’s no ā€˜maths’ to do.
Our Shared Tab has been open for over two years, I can scroll back through them really quickly and smoothly, so settling up every now and then definitely fixes it :+1:

Perhaps, and calculating from the last time things were zero might make sense. Though you can edit the history, so I could imagine that getting complicated (it would need to update that reference point on how far to go back upon an edit).

I think in some ways though, that makes the technical issue here worse.

I can understand how a large data transfer or calculation over transactions back to 2018 could lead to slowness in the app. However we have settled up numerous times since then, including this year.

Which would imply it is still doing something beyond that point, or that it gets slow with much fewer transactions.

Out of interest, do Monzo Devs / product folk come by these forums much? I was directed here from the apps help. Perhaps I should raise a bug report directly with them?

We do have a joint account too, we use it for fixed costs like bills and direct debits.

I disagree actually, this method offers us less work and complication and, I think greater financial freedom for both parties. Broadly instead of having to put salaries into one account and transfer personal money out, or to work out ā€œhow much we might need for variable spendingā€ in advance, we can play it more by ear, but can ensure things remain equal.

Irrespective it’s worked well for us and uses a feature that is built into the app, but appears to be broken due to unacceptably slow load times (10s+ is bad in the web / app world).

2 Likes

It was just a suggestion. Everyone does things differently so you’re allowed to disagree :rofl:

We just put a fixed amount of our salary into our joint account each month. Not the entire thing. A simple standing order each month and job done :raised_hands:

So we use the joint account for all household bills, groceries, joint direct debits and each of our personal account for personal expenses. Like our cars, phone contacts etc.

This way it allows us to set budgets, as well as clearly analyse spending and summary for each of our personal and joint expenses.

:100: yeah sounds good too, whatever works, right?

Mostly my concern for this thread is that there’s a part of monzo’s offering which is offering poor performance. Potentially in a way that’s difficult to spot, as it seems to require quite a few transactions!

1 Like

i second this issue I have a shared tab open since many months and it is not possible to add any more items. It just gets stuck in the ā€œsplit billā€ screen.

I agree there’re workarounds (in my case I started a new shared tab with the same person0 but I think this is a bad implementation of something that is meant to be simple and quick and it shouldn’t stop working/be unresponsive after xx months or xxx added items.