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…
I just don't understand why this is still open for so long.
It is absolutely nothing to do with your data structure, I am 100% sure because it is to do with UI/UX fix. This fix would just need <100 lines of code. In the UI, while switch "split by.." tabs, first time user already split it by share, ok, so this UI needs to remember this, and when I switch tag to "split by amount", then the amount should be calculated based on the previous select on "split by shares", and same with "split by %.. and other options". That's it, no rocket science here. The very clear bug here is, the developer just resetting the "split by shares" to "1" by default whenever I switch to its tab, a blunt direct error!!
Veeresh
I just don't understand why this is still open for so long.
It is absolutely nothing to do with your data structure, I am 100% sure because it is to do with UI/UX fix. This fix would just need <100 lines of code. In the UI, while switch "split by.." tabs, first time user already split it by share, ok, so this UI needs to remember this, and when I switch tag to "split by amount", then the amount should be calculated based on the previous select on "split by shares", and same with "split by %.. and other options". That's it, no rocket science here. The very clear bug here is, the developer just resetting the "split by shares" to "1" by default whenever I switch to its tab, a blunt direct error!!