Xand3r
My feedback
5 results found
-
501 votes
Splitwise has some basic support for this now, depending on what you’re looking for. We now support multiple email addresses for a single account, so you can more easily share one account with multiple people.
However, we won’t automatically adjust how much you should owe as a “couple”. For example, if “Bob” adds an expense with “Sue and John’s Couple Account”, then the bill will be split 50/50 between those two Splitwise accounts. I can definitely see how it would be useful to automatically make Sue and John pay for 2 shares, but we’re unlikely to add that feature in the near future. For now, you can still work around this by manually using the “Split by shares” option when adding a bill, and assigning 2 shares to the relevant account.
-
133 votes
Updating our response since it’s been a long time since the idea was opened. Even though saving the type of unequal split feels like something that would obviously be nice to have (I certainly would use it myself every so often), it requires a change to our data structures, and is therefore a bunch of difficult work to fix, especially since it would need to be fixed separately across iPhone, Android, and web.
If you have a specific use case where not having this feature is really bothering you a lot, please email support@splitwise.com, or comment below to let us know why it’s important to you. The original poster’s meal example is clear and I’m wondering if there are other reasons why it is needed, or any easier way for us to fix it.
In terms of the priorities of our small team, most bills on Splitwise are split…
An error occurred while saving the comment -
203 votes
Thanks for the suggestion. Makes sense, sorry it’s not there already. I’m going to leave it open for further voting.
Best,
Jon -
14 votes
Sorry for the trouble! For now, you can always convert into a different currency by temporarily changing your default currency to something else, using the “convert” function, and then changing your default currency back.
-
14 votes
Thanks for your suggestion! We’re not currently planning any significant changes to the itemized bill form, but I see how this would be a useful addition. I’ll leave this open for further voting and pass along the suggestion.
Lack of this feature feels very annoying to me as well. Even more, I believe that a lot of people uses only equal split, because unequal is so difficult to maintain. And while equal split in most cases is "save and forget" thing, when you go for unequal split, this means you are taking this expense seriously and will want to revise or fine-tune it later.
We use splitwise to share expenses in a trip with group of 10-20 friends. We have a lot of expenses that ideally should be splitted in unequal shares. Typically this is required for Food, Drinks, Rent. Let's say we go to a supermartket and buy a lot of groceries for the whole group of people. First, we need to enter this expense quickly, to record the fact that someone spent a lot of money for all this stuff. Next, later, we can discuss and agree how we split the shares (we can put smaller share for a kid, or for a person who doesn't eat much, doesn't drink alcohol, etc.). Important thing here, is that these discussions and fine-tuning of shares are an iterative process. We agree on a share with one person, save it. Next, we need to align with other person, and save his/her share, and so on.
Also, at the end of the trip we usually revise all expenses. Could be that sharing concept have been changed during the trip, and we need to adjust older expenses. Or we may notice that forgot to include someone into the specific expense, or someone included by mistake. Actually, when opening an unequal shared expense, we cannot see which shares or percentages were entered - only exact amounts for each person. This makes revising a nightmare.
Because editing is so difficult, sometimes we have to forget this fine-tuning, and just do an equal split. Sometimes this feels unfair for some people, who wants an easy and transparent way to record and see his/her share.
I understand that this change may be difficult for you, because you do all the calculations on the frontend, and save exact amounts to the database. I'we worked with Splitwise API, and know that it doesn't provide any shares/percentages, meaning you do not have them in the backend. But I believe that you can start making this change gradually, by adding additional information to the data model (type of split, shares, percentages), and still keeping backward compatibility with old frontends and API. You can save BOTH split amounts and shares to the DB, and if any frontend app is not updated yet, it will just work as before.