Projects 06 / 11
Soma-Σ
An app for rideshare drivers.
Personal finance management app focused on rideshare drivers. Earnings history, expenses, maintenance records and insights.
Overview
Soma-Σ is the rideshare driver's notebook, except it does the math. The driver starts the shift in the morning, logs earnings per platform and expenses, and the app returns net profit, earnings per hour and cost per kilometer.
It is dark and minimal on purpose: it's used with the car parked between rides, with little time and lots of glare on the screen. Vue 3 and Quasar in the app, Capacitor for Android and a Laravel API keeping the history.
Features
What the system does
-
Shift timer
One tap starts the day's shift, with pause and resume. The state survives closing the app and restarting the phone.
-
Earnings per platform
Uber, 99, InDrive, private rides, tours and others, logged on the day itself. Net balance and daily goal progress update instantly.
-
Daily expenses
Charging, fuel, food, tolls, parking, car wash and maintenance, each in its own category.
-
Period insights
Net profit, earnings per hour, average per day, hours worked, km driven, efficiency in kWh/100 km or km/l and weekly evolution with the best week highlighted.
-
Calendar and history
Worked days show on the home calendar, shaded by result, and the history groups by week with each day's gross and net.
-
Vehicles and maintenance
Several vehicles, one active at a time, each with its own efficiency and a maintenance history with cost and mileage.
-
Weekly goals
Weekly goal and working days per week, with how much is still needed per day to reach it.
Screens
Inside the system
Screens show fictional data generated for demonstration.
Stack
How it was built
- Frontend
- Vue 3Quasar 2PiniaChart.js
- Mobile
- Capacitor 7Capacitor PreferencesAndroid
- Backend
- Laravel 12PHP 8.3Sanctum
- Data
- PostgreSQL
Behind the scenes
Technical challenges
-
A timer that never gets lost
The shift is an open session in the API, but the pause is local and the state lives in Capacitor Preferences. When the app opens, the local state is restored and then reconciled with the API dashboard, without double-counting hours.
-
Electric and combustion in the same math
The energy type comes from the vehicle's efficiency unit: km/kWh yields consumption in kWh/100 km from the energy price; km/l yields kilometers per liter from the fuel price.
-
Fast, idempotent entry
There's one day per driver per date and one entry per platform per day. Saving a value is an upsert, zeroing it deletes it, and creating the day again never returns an error.
-
Reading the ride before accepting it
In parallel, a native Kotlin Android prototype reads the ride card through screen capture and on-device OCR and shows earnings per km and per hour, without using the accessibility service, to stay within Play Store policies.
Need something
like this?
Tell me the idea or the problem. I help shape the solution and build it from the API to the app.
Let's talk