Skip to content


My feedback

1 result found

  1. 133 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  General  ·  Admin →

    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, 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
    Kyle commented  · 

    For what it's worth, I agree that this is an annoyance. I am splitting a rental house based on how long each person is staying at the house. While planning, some people agree to 3 nights, but later change to 5 nights. When I edit the split, I have to re-enter all 14 people's shares just to make this one change.

    Or, a husband wants to pay for his wife. Rather than updating her share to zero and his to add 3 more, I have found it simpler to stay in the "split unequally" view and zero out her bill and adjust his for the difference.

    Maybe this use case will help you all see the value of this feature.

Feedback and Knowledge Base