// case file 08 · Software

Divyd

From “who owes who” to a group that splits bills and actually talks, live on iOS and Android.

RoleFounder · mobile + productTimelineJan 2026StackExpo + React Native3.1.0shipped app version
// 01 the problem

Splitting bills in group chats is awkward, and the tracking app is never where the conversation is.

// 02 how it works
  1. Step 01

    Bill splitting inside communities.

  2. Step 02

    A feed with threaded comments.

  3. Step 03

    Group chat alongside the money, over websockets (Django Channels).

  4. Step 04

    Media and video posts.

  5. Step 05

    Builds and over-the-air updates through EAS workflows; the Django + Celery backend was built with the team’s backend engineer.

// 03 decisions that mattered
01

Runtime versions drift between platforms

iOS and Android builds can land on different runtimeVersions, so one OTA publish only reaches matching builds. Releases are checked per platform.

// 04 results
3.1.0shipped app version
2app stores
OTAupdates via EAS
// 05 takeaway

Shipping is a release process, not a merge.

ExpoReact NativeEASDjangoChannelsCeleryPostgreSQL
// artefacts
// contact

Let’s talk

Open to software engineering and AI automation roles, plus selective contract work. I read every message.

psst, click it
● DRAFT

Show me the copy-paste.
I’ll tell you if it should be a system.

01
02
How often?
03
Which tools?

Hiring? Tell me about the team.
I’ll tell you where I’d help first.

01
02
03
Timeline
04

You get a reply within 24 hours: whether it should be automated, what I’d use, and a rough timeline.

You get a reply within 24 hours.