Support of weight with nextcloud cospend

[Bonome]

In the nextcloud ui, we can set a weight on a user and the balance is updated according this weight.
It seems that this weight is not supported in PayForme, the amount per user in members list matches the weight 1.

[Hustenbonbon]

Hey, this is right, weight is not supported yet. We needed to focus our capabilities on the core features for now, so we decided to ignore weight. If anyone would be into introducing weight into the app, I would highly appreciate it.
Otherwise it is on the roadmap, but probably not the next thing

[retiolus]

Any update with this?

[benjamindahl]

still no update?

[Hustenbonbon]

Hi, no there is no update nor will one come, as the app is not actively developed anymore :(

[benjamindahl]

Would love to see an iOS App for Cospend. I recently had a good experience with Splitwise, but would like to convince my friends of an open source solution which is easy and convenient to handle.

[fealXX]

@InteractionEngineer why the wontfix label? Seems like an important part of cospend compatibility to me.

[InteractionEngineer]

Hi @fealXX, could you think of some Use Cases or even User Stories for me to better understand the feature's value for users and reevaluate the need to implement it (soon-ish)? For me, the main motivation to use something like Cospend is to split expenses in a fair manner which, in my mind, is always evenly. That's why I think the basic functionality with a weight of 1 already satisfies most scenarios a user would want to use this app for.

[maxus-git]

Also important for me. I use the different weight for me and my girlfriend. We have different incomes and this is also taken into account in our expenses.

If I want to see who owes how much to whom, I have to look in Nextcloud.

[fealXX]

Hi @InteractionEngineer - the current example that led me to comment on this issue is my wife and I going on a vacation trip with my sisters. We have a joint account, so only had one User in the Cospend called "Felix + Wifesname" and one for each of my sisters. Since we're 2 persons, we had 2x weight on our user. That way, we don't have a situation where Sister 1 owes Felix Amount X and also Sister 1 owes Wifesname Amount Y - but sending both of those amounts into the same account. So more a convenience thing I was used to from moneybuster / android, which supports the weights in Cospend.

Other usecases I had in the past are similar to the one maxus-git mentioned: When traveling with friends with different income levels or eating out with friends that don't drink alcohol etc it is helpful to just lump sum reduce their amount by applying a multiplier smaller than 1.

[InteractionEngineer]

Hm, I see! Thank you @fealXX and @maxus-git for providing these valuable insights. I am going to implement the weight-feature during the redesign of PayForMe. This will not just be a visual overhaul but a focus on usability and User Experience - therefore I need to understand the details of PayForMe-user's usage. But that's something for end of 2025!

For now, I want to focus on the most important functionalities of PayForMe, especially it's stability and compatibility with different setups of backends. This is why the won't fix label is going to stay… until the redesign process begins.