CREATE · CHANGE · RUN
A trip expense app.
With your own rules.
Describe an app in one sentence, ask for a different way to split the bill, and use the result inside Etono’s native phone app.
THE IDEA
Take a familiar need.
Make a small personal tool.
Shared trip expenses are a familiar use for Splitwise. We used that need as the starting point for an original Etono case called Trip Balance.
An independent example
Trip Balance is not affiliated with or endorsed by Splitwise, and is not a complete replacement. It uses an original name, interface and fictional data. It does not process payments, connect to banks or establish shared cloud accounts.
1 · CREATE
Describe the people,
expenses and balances.
Create a new app in Etono and enter this exact request from our trial. Keep Etono open while it works. Generation needs an internet connection and Credits; results and usage vary.
Our first generation ran out of Credits after saving a working app. We added test Credits before continuing. This was a real trial with repairs, not an instant or uninterrupted generation.
Create a trip expense app called Trip Balance where I can add people, record who paid each expense, split the total equally, and see each person’s balance.
2 · CHECK
Start with numbers
you can check by hand.
Open the generated app. In People, add Alex, Blair and Casey. Record Lodging: $120 paid by Alex; Dinner: $60 paid by Blair; and Taxi: $30 paid by Casey. Include all three people in each expense.
Our app showed a total of $210 and an equal share of $70 each. Check the balances before changing the rules.
Observed equal-split balances
- Alex paid $120: gets back $50.
- Blair paid $60: owes $10.
- Casey paid $30: owes $40.
Positive means the person paid more than their share. The net balances sum to zero. Check the sign convention in your generated version.
3 · CHANGE
Ask for different shares.
Keep the saved expenses.
Return to the conversation and send this follow-up. After the change, our app had share controls in People and a By shares option when editing expenses.
The first attempt needed a repair: the new controls appeared, but changing a share failed. We stopped a long checking cycle, sent the focused request below, then tested the actual controls ourselves.
Let me assign a share count to each person instead of splitting everything equally, and keep all my existing people and expenses.
IF A CHANGE FAILS
Describe the failure.
Protect the data.
This was our actual repair request. Use your own visible error and data in a similar request. Wait for generation to finish, or stop it normally, before manually editing test records. We learned that overlapping these steps can interfere with the checks.
The share controls appear after refreshing, but tapping Alex’s + button shows “Unknown endpoint” and leaves shares at 1. Please fix this in the running app, restarting its app service if needed. Keep Alex, Blair, Casey and all three expenses unchanged. Complete a focused check that changing shares works and persists; do not spend another long cycle rewriting the test harness.
4 · SET YOUR RULE
Two shares for Alex.
One for everyone else.
In People, set Alex to 2 shares and leave Blair and Casey at 1. Our controls move in half-share steps. These are defaults for new expenses; changing them does not rewrite old bills.
For each existing expense, tap Edit, choose By shares, set Alex to 2 and the others to 1, then save. Keep the original amount and payer. In our trial, the three expenses and their names remained intact.
Observed 2:1:1 result
- Lodging $120 → $60 / $30 / $30.
- Dinner $60 → $30 / $15 / $15.
- Taxi $30 → $15 / $7.50 / $7.50.
- Total share → Alex $105; Blair $52.50; Casey $52.50.
Balances showed Alex +$15, Blair +$7.50 and Casey −$22.50. The suggested settlement was Casey paying Alex $15 and Blair $7.50. These are calculations; no money moves in the app.
5 · RUN & REOPEN
Use it in Etono.
Check that it stays.
Open Run to use your app. Leave and reopen the same project, then check the people, expense count, amounts and balances again. We also reopened Etono during the trial: all three weighted expenses and their amounts remained. After the generation checks stopped, Alex’s default of 2 also remained when the project was reopened.
Checks completed in the actual interface
- Equal and 2:1:1 calculations matched the hand calculation.
- A $30 preview at 1.5:1:1 rounded to $12.86 + $8.57 + $8.57 = $30.
- A zero-amount draft was rejected and was not saved.
- The final total stayed $210, with three people and three expenses.
This is one tested example, not a guarantee for every generated app. Automated checks alone were not treated as proof.
SCOPE & ACCESS
Check your result
before relying on it.
Etono is in early access. This case was tested in the native Etono app on an iOS Simulator, not a physical phone or Android device. “Run in Etono” does not mean exporting a standalone App Store app.
This example uses one currency and local records. Shared live editing, bank connections, payments, cloud sync and currency conversion were not implemented or tested. Generated results can differ and may need repairs. Use fictional data while checking calculations and persistence, and keep separate backups of important records.
Creation and modification need internet access and Credits. Availability and payment options vary by platform and region; see current downloads and testing access and Credits and pricing. Published USD website prices apply to the Android website edition outside mainland China, not to every iOS installation.