Soma-Σ

An app for rideshare drivers.

Personal finance management app focused on rideshare drivers. Earnings history, expenses, maintenance records and insights.

Platforms
Mobile
Year
2026
Status
Closed testing on the Play Store
Role
Full stack — API and app
Play Store · closed testing

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.

What the system does

  1. Shift timer

    One tap starts the day's shift, with pause and resume. The state survives closing the app and restarting the phone.

  2. Earnings per platform

    Uber, 99, InDrive, private rides, tours and others, logged on the day itself. Net balance and daily goal progress update instantly.

  3. Daily expenses

    Charging, fuel, food, tolls, parking, car wash and maintenance, each in its own category.

  4. 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.

  5. 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.

  6. Vehicles and maintenance

    Several vehicles, one active at a time, each with its own efficiency and a maintenance history with cost and mileage.

  7. Weekly goals

    Weekly goal and working days per week, with how much is still needed per day to reach it.

How it was built

Frontend
Vue 3Quasar 2PiniaChart.js
Mobile
Capacitor 7Capacitor PreferencesAndroid
Backend
Laravel 12PHP 8.3Sanctum
Data
PostgreSQL

Technical challenges

  1. 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.

  2. 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.

  3. 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.

  4. 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