Feedback
Roadmap

Have something to say?

Tell us how we could make the product more useful to you.

Completed

OCR line item improvements

Following up on two small pains I noticed with the current itemization on the snap feature (by doing manual assignment of items to people): Missing quantity per line. OCR-generated items don't show quantity. In a claiming flow, this is critical — people need to know if an item is "1x" "2x" to know how many people to split that item. Line items inherit the invoice name instead of the item name. Everything currently shows up as e.g. "Xiringuito Beach Club Meal" instead of the actual item. People can't tell items apart when they are split by different people. Suggestion: Combine invoice name + item name, e.g., "Xiringuito Beach Club Meal - Sumo do dia". There 2 improvements could also be carried over to the collaborative item claiming feature if you decide to build it: https://bananasplit.featurebase.app/p/feature-idea-collaborative-item-claiming-for-large-groups :) For collaborative claiming to work well at scale, people need to clearly see what each item is and how many are available to claim — so these two fixes are especially important there.

Jorge da Costa Ferreira 20 days ago

2

Planned

Feature idea — collaborative item claiming for large groups

I'm excited to share a feature idea for group expense splitting. Context: splitting mechanics vary by group Different groups split bills differently: Equal split — most common, everyone pays the same share. Itemized by consumption — each person pays only for what they had. Hybrid — usually splits equally, but occasionally itemizes (e.g., one person just had dessert while another had a full meal). The gap: itemizing doesn't scale to large groups Recently I was in a group where consumption varied a lot — one full dinner, one small meal, one just a juice — so itemizing was clearly the right call. One person paid, and I used the Snap feature to go through each line item and assign it to the person who consumed it. This worked fine because the group was small. But for larger groups, manually assigning every line item to the right person becomes tedious and doesn't scale. Proposed feature: collaborative item claiming For large groups, let people "claim" their own items from a submitted invoice instead of one person assigning everything manually: Someone submits the invoice/receipt to the group. Group members collaboratively go in and claim the items they consumed. Once all items are claimed, the individual expenses are automatically submitted to the group. Monetization angle I'd suggest gating this so at least one person in the group needs a Pro subscription to enable it. This could also work well as a soft on-ramp — a way for non-paying users to experience a premium feature and get nudged toward upgrading. This is a similar monetization strategy as https://www.airconsole.com/

Jorge da Costa Ferreira 20 days ago

2

Completed

Export and import expenses from Splitwise

I was speaking with a friend and he was with some concerns to migrate from Splitwise because he has the history of expenses there. He uses Splitwise to manage expenses with his partner. Importing the history from Splitwise would remove the barriers to entry. Additionally exporting might be interesting to run analysis.

Jorge da Costa Ferreira about 1 month ago

2

Completed

Photo library permission handling

(This affects both "Snap it" and profile picture setup) In both places where the app needs photo access (scanning a bill/receipt via Snap it, and setting a profile picture) the flow shows an alert saying "Photo library permission is required to select photos" with just an OK button. It never actually triggers iOS's native permission prompt, so there's no way to grant access from either screen. It's a dead end in both cases. To grant these access is painful. Suggestion: build a single, reusable permission flow and use it everywhere the app needs photo access, rather than handling it separately per feature: A short in-app "priming" screen that explains, in plain language, why access is needed for that specific context, with a "Continue" button. Only after the user taps Continue, trigger the real iOS system permission dialog ("BanaSplit would like to access your photos") with the standard Allow Full Access / Select Photos / Don't Allow options. If permission was previously denied, detect that and deep-link to Settings instead of re-showing a prompt that won't work — iOS won't re-trigger the system dialog once it's been dismissed once. This would simplify the use of these photo required features.

Jorge da Costa Ferreira about 1 month ago

2

Completed

Manage expense data and time

I was adding an expense to my group and since I like to have things right in terms of dates in case I want to go back in time and review what expense is that, I was editing the date since it was a few days ago. I knew it was from Thursday but I didn’t have the calendar days mapped to the days of the week in my mind. Since the UI doesn’t showed me the days of the week I had 3 options: 1) make mental calculations to pick the right day 2) exit the app and check the day on a calendar 3) ignore and save with a wrong day. The balance is what matters the most anyway I opted by the third. But it was a small moment of frustration. Suggestion: add the week day visible on the UI when the user is picking the date. Suggestion 2: the time remains the current time when I go back in time. Probabilities are really low that the time is right when I’m adding a expense in a different day. Should it go empty in those cases and only if the user selects it it would be populated?

Jorge da Costa Ferreira 2 months ago

5

Completed

Allow default splits by group.

Im a PM so tacking my chance in sharing a user story you can try to implement direct if you agree 😝 User story: as a user that as a family budget in which different people pay different % I want to be able to set default of share of expenses to each group member So that I avoid editing manually each expense acceptance criteria: on group settings add a default split area List each member and have by default 1/ populated Allow the user to edit the % for each member Apply by default the saved percentages ok new expenses (new setting) Fix the experience on the current manual edition of % o by editing automatically the remaining group members if one is edited (e.g., today if I select 60% for one member in the group of 2, the other member keeps 50% - it should auto change to 40%). If the group has more than 2 members edit always automatically the non manually edited people by dividing the rest of the percentage by those not edited. Have this behaviour both for the manual editing of an expense and for the default split (new feature described here).

Jorge da Costa Ferreira 3 months ago

7