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 equally, so we haven’t been able to make this a priority. We’re not likely to roadmap this feature unless we see a big groundswell of support from the community.
Thanks for your patience and sorry that this has been open so long. We also have some ideas for work-arounds, so feel free to email support if you are stuck with a particular situation.
Best,
Jon
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…
This is not an idea but what seems like a small bug.
When dividing an expense in a group by shares (i.e. one person has 1 share, the other 3, etc.), the expense amount cannot be updated. In other words, when I try to update an expense which is divided by shares, I get the following error message:
"The following errors occurred:
- The total of everyone's owed shares ($XX.XX) is different than the total cost ($YY.YY)"
Gustave
This is not an idea but what seems like a small bug.
When dividing an expense in a group by shares (i.e. one person has 1 share, the other 3, etc.), the expense amount cannot be updated. In other words, when I try to update an expense which is divided by shares, I get the following error message:
"The following errors occurred:
- The total of everyone's owed shares ($XX.XX) is different than the total cost ($YY.YY)"
I hope this is clear :)