Studio-owned product · Development case study
SabkiJeb: a Flutter app for shared expenses.
An example of turning a real-world workflow into a mobile product: recording shared costs, tracking loans and keeping balances clear between people.
- Project
- Josh Studio product
- Interface
- Flutter / Dart
- Backend
- Supabase / Postgres
- Local storage
- Drift
- Focus
- Shared expenses & loans
Product interface · example dataThe problem: a payment is only part of the story.
Flatmates and friends need to know who paid, how a cost was split and what is still owed. A message thread or spreadsheet can hold the numbers, but the record becomes harder to follow as expenses and repayments accumulate.
SabkiJeb brings shared spaces, expenses, personal loans and repayment confirmations into one product. The design challenge is to make the current balance understandable while keeping the actions behind it visible.
This is a studio-owned product. It is presented as implementation evidence, with no claimed client revenue or growth results.
Three decisions behind the build.
The useful part of a case study is why the implementation works the way it does.
- A shared UI with Flutter
- Flutter and Dart provide the app interface, with Riverpod for state management. The product brings expense records, balances and loan workflows into a consistent mobile experience. Check the product website for current platform availability.
- Shared records with Supabase
- Supabase Auth, Postgres and Edge Functions support the backend. Shared expenses and personal loans have different workflows: loan repayments are recorded separately and count after the other person confirms them.
- Saved records when offline
- Drift provides local storage for saved records. Changes made offline queue until the connection returns. Users sign in online first and let pending changes sync before signing out.
- A clear payment boundary
- SabkiJeb opens the user’s UPI app with payment details. The user approves payment there, records it in SabkiJeb and waits for the other person to confirm receipt. SabkiJeb does not move money or automatically verify payment success.
What this means for your app.
A useful first release starts with a complete workflow, a clear record of state and honest boundaries around integrations.
If you are planning a customer portal, booking system or mobile product, start by describing what a user needs to complete. We can scope the screens, backend, integrations and handover around that workflow.
Let’s find the right first step
What would move your business forward?
Tell us what you want to improve, who it is for and when you need it. You will hear back within one working day with next steps, or an honest answer if the project is not a fit.
Prefer to talk first? Use the booking link. Have a brief already? Email it directly. No finished specification needed.