Selected Work - Automation

Streetvers - author once, ship everywhere

The same character data has to be a playable unit, a collectible card, and a marketing drop. Done by hand that means re-entering the same thing three times and watching it drift. I built a single source of truth and a pipeline that ships the playable roster and the social drops from one authoring step.

Role

Solo Developer / Automation

Focus

Single source · Content pipeline · Release

01The problem, and the manual way it was handled

In Streetvers, one object lives three lives: the character you play, the StreetCard you collect, and the drop seeded to influencers. The naive build authors each surface separately, so they drift the moment a buff changes in the game but the card still shows the old number. That manual re-entry is a correctness problem and it scales badly across a growing roster on four platforms. The fix is to author the character once and generate everything downstream from it.

02What I automated

  • One source of truth - character data-portrait, stats, rarity, lore-is authored once in the backend and is the single record everything else reads from.

  • Roster generation - the playable unit and the collectible StreetCard are produced from the same record, so gameplay and collection never disagree.

  • Drop pipeline - the marketing drop seeded to influencers-and the stake-gated drops surfaced through the Reality Metaverse partnership-are generated from that same data, integrated over API with no separate asset to build or keep in sync.

  • Cross-platform delivery - one client and one data pipeline reach iOS, Android, Windows, and Mac without per-platform manual rework.

Streetvers x Reality Metaverse - official trailer

03Automation decisions

Author once, generate the rest

Problem
Maintaining one character as three hand-built surfaces guarantees they drift apart and triples the work on every change.
Approach
I made the character record the single source of truth and generated the playable unit, the collectible card, and the social drop from it.
Result
I make a change once and it propagates everywhere, so the marketing surface and the in-game unlock cannot fall out of sync.

Drops as pipeline output

Problem
If every influencer drop is a manual export, the growth loop is bottlenecked on a person assembling assets by hand.
Approach
I wired the drops into the same data pipeline, so promo content is a generated output of authoring a character rather than a separate job.
Result
The collection-as-marketing loop runs as part of the system instead of a recurring chore.

Partner drop reads the source

Problem
The Reality Metaverse stake-gated drop is a fourth surface for the same character, and a hand-maintained export to a partner is exactly where data goes stale.
Approach
I generated the partner-facing drop from the same record and pushed it over the API, so a stat or art change reaches the partner program with no separate export or reconciliation.
Result
The game, card, social drop, and partner drop stay consistent because the integration reads the source of truth rather than copying it.

One pipeline, four platforms

Problem
A growing roster on iOS, Android, Windows, and Mac usually multiplies into per-platform asset work, leaving four places to update on every change.
Approach
I drove all four targets from one Unity project and one data pipeline, so a character authored once builds and ships everywhere without a per-platform re-export.
Result
Adding a platform is a build setting rather than a new content workflow.

04How it was built

A real production stack behind the pipeline, with one record for character data.

Unity 6C#FastAPIPostgreSQLReact 19TanStack StartCloudinary

05Outcomes

Author once

Unit · card · drop, generated

4 platforms

One pipeline, no rework

No drift

Single source of truth