XSV/DEV
XSV/DEV
Five projects, all of them real. One app in both stores, one on its way there, four sites live. Every screenshot on this page is a capture of the running thing. No mockups, no comps.
A bracket app for iOS and Android, its sync server, and the site at bracketeer.me. Build a bracket for anything, put it in front of a crowd, let the votes settle it. Five formats in one private room: brackets, pick'em cards, squares sheets, survivor pools and golf field pools, all feeding one league table. Every pixel and every sound is generated at runtime: no image assets, no icon packs, no UI kit, no sound files, and the whole app is about 119 KB gzipped. Mine end to end, down to the store listings and the box the server runs on.
An iOS and Android app and the site behind it, for the North Shore's roast beef community: 200+ shops mapped, rated and reviewed, live events, paid sponsor placement and the billing behind it. Seven releases shipped through both stores. I run the server too: it is a live production system with real users on it, not a portfolio piece.
Full brand hub for Mike Petrigno (@whatdidyoueattodaysir, 250K+ followers). His Instagram is the CMS: posts are scraped and parsed straight into the site, which is how 670+ spot records and a video feed exist without anyone typing them in. A numbered-line detector picks his Top 10 posts out of a thousand captions and files them as lists on their own. On top of that, a custom admin panel so he never touches code, live Shopify product pulls through the Storefront API, and two domains on one Next.js site.
The site you're on. A WebGL2 ink-bleed shader behind the hero, hand-written layout, no template and no framework, so it loads as one document. The site is the proof of what I'll build for you.
Several shipped mods and tool suites for games I did not write, across Windows, Linux, Android and iOS. No source, no documentation, nobody to ask: read the compiled binary, work out how the thing is put together, then build a UI on top of it that other people can actually use. It is here because it is the closest thing to a live demo of dropping into an unfamiliar codebase and being useful on day one, which is most of what client work actually is.