case notes

Work

Every project as a card. Open one for the notes: what it was, what the research changed, and what I built.

Mr. Oktoberfest

A site and a phone-sized admin for a musician who doesn't use computers.

Read the case

Arrivalio

A guided checklist for a newcomer's first months in Canada.

Read the case

FromSurvey

A survey tool I wrote instead of paying for one.

Read the case

Twin V Studio

A brutal-editorial studio site, designed and built solo.

Read the case

TheChistka

An order pipeline for the person who opens it forty times a day.

Read the case

City Dashboard

School redesign of Vancouver's public data site.

Live site

Displine

A running-challenge habit tracker on the Strava API.

Read the case

All work

Mr. Oktoberfest

A site for a solo accordionist, with a guest book he approves by email and an admin he runs from his phone.

Gary plays accordion at Oktoberfests, community halls and seniors' residences across the Lower Mainland. His old site was a Wix template: compressed photos, recordings in an embedded player, and a builder he never opened, so nothing on it changed.

The brief was really about who would run it. Gary answers the phone, not email, and he was never going to learn a site builder. So every recurring job became one step. A booking request arrives as a plain email he can reply to. A guest's comment arrives with a link and one gold button that puts it on the site. Nothing appears until he presses it.

Everything else he can change himself from his phone: songs and their groups, the places he has played, the wording on the page, and his photos. The photo manager was the part that needed the most thought. The site crops each photo to a square or a wide frame, so he taps the face and sees previews of how it will actually look on a computer and on a phone.

Launch was more work than the build. Wix does not allow nameserver changes, and Cloudflare Registrar only accepts domains already active on Cloudflare, so the domain went Wix → Porkbun → Cloudflare DNS. Every old Wix address redirects to the matching section, so links he had shared for years still work.

AI was a large part of this one: the code was written with Claude Code. I did the rest: the client, the direction and design decisions, the content, testing on real phones, and the launch. It runs on a Cloudflare Worker with a D1 database. Forms work with JavaScript turned off.

The Mr. Oktoberfest home page: Gary with his accordion, a request-a-date button and his phone number

All work

Arrivalio

A guided platform for newcomers navigating their first months in Canada.

Arrivalio is my capstone. It helps newcomers get through their first months in Canada with a step-by-step plan: SIN number, bank account, healthcare, housing.

The project started from research into what newcomers actually struggle with. The information is not missing. Government sites, settlement guides and community resources all have it, but it sits in different places and lands on you all at once. For someone who just arrived that is overwhelming.

So I did not add more information, I organised what already exists. Mobile first, because that is where people open these resources. Scattered tasks became one checklist with clear priorities and a sensible order, so it answers what to do first, not only what to do.

Usability testing kept changing the build. The biggest decision came out of it: I had planned a flexible system, and testing showed that too much freedom made things harder. People wanted to be told what came first. It became a guided checklist with task dependencies.

AI tools were part of this project. Figma Make for early layouts, Claude and ChatGPT for debugging and problem solving.

Arrivalio, the guided checklist, shown on mobile and desktop

All work

FromSurvey

A survey tool I built instead of paying for one, then kept because people other than me actually use it.

It started as a university project: I had to collect research responses and every paid tool wanted a subscription for something I would use for a few weeks. I built a small survey app. The surprise was that it did not die after the course. I still use it, and people I know run their own questionnaires on it.

The original looked like a school project. This year I redesigned it so it does not. The public side is one question at a time, in English, Russian, French or Spanish — language is part of taking the survey, not a footer toggle. Empty visits do not count as answers. The private side is where the work is: a builder, results you can read at a glance, and a share that actually means a second person in the same survey.

Most builders make you click a survey together one field at a time. Here you can paste a prompt, or a ChatGPT reply, and get the questionnaire. Sharing is not just a public link. You invite someone by email; they can edit questions, see responses and open analytics. If you are both in the builder, you see who is on which question and when they save, so you do not overwrite each other in the dark.

The first production host slept the database after a few days of quiet, which is a bad surprise when a real person opens a live survey. I moved it to Vercel and Neon, with auth and data on a same-origin API, so inactivity does not pause the project the way it used to.

The product lets you paste a generated survey. I also used AI on the rebuild, for layout and debugging.

FromSurvey, a one-question survey in English with Russian, French and Spanish at the top

All work

Twin V Studio

A brutal-editorial marketing site for a small design-and-development studio, built solo from design system to deploy.

Twin V Studio needed a landing page that read as brutal-editorial, not another SaaS template: full-bleed layout with no centred container, and a palette that mostly stays quiet. Canvas, paper and carbon carry the page; mint and voltage are kept for accents only.

The page moves through three zones, light, dark, light, and the transition between them is a rounded card that grows into a full-screen section as you scroll. I built that as a reusable ScrollPanel component on GSAP's ScrollTrigger, backed by one set of role-based colour tokens that resolve correctly in whichever zone they land.

The hero runs morphing SVG blobs behind an all-caps Anton headline, and the whole page scrolls through GSAP's ScrollSmoother rather than native scroll, which meant getting fixed elements like the nav to behave against a smoothed viewport. I also check tab visibility before triggering animations, so GSAP doesn't keep animating, and eventually freeze, content sitting in a background tab.

Next.js 16 on Turbopack, React 19 and Tailwind v4 carry the front end; a small FastAPI service handles the brief form and sends it over the Gmail API.

Twin V Studio landing page, showing the hero with morphing SVG blobs

All work

TheChistka

Built around the administrator who opens it forty times a day, not the owner who checks it twice a week.

A three-person cleaning business in Kokshetau, Kazakhstan ran on a spreadsheet, a WhatsApp thread and the owner's memory. Prices lived in one person's head, so an administrator who needed a quote at 9am waited for him to be free. Nobody could say what a customer had paid last spring, which technician had been to their apartment, or how many enquiries never became jobs.

The owner opens the system twice a week. The administrator opens it forty times a day, from her phone, often away from the office. Every screen was measured at 390 points before it was measured wide, and no field is required that doesn't come up in a real phone call with a customer.

A closed order stores the price it was sold at, not a pointer to today's price list, so the owner can raise rates on Monday without changing what last month's jobs earned. Balances and payment status are computed from payment records, never stored as a field, so the number on screen always equals the rows beneath it. Money is integers throughout, no floating point anywhere in the calculation or the database.

Built for a real business, my brother's, and unpaid: I'm calling it commissioned rather than client work because that's the honest word for it. In production since September 2026; first month of real use in progress.

TheChistka CRM order pipeline, showing an order card on the demo stand

All work

Displine

No participant accounts — just the two or three organisers who already track everyone by eye.

Displine is a habit tracker for a running challenge my friend group runs every year — who showed up, who paid their penalty, who's still in.

We used to track it in a spreadsheet and a group chat. Attendance lived in someone's memory until they had time to update the sheet, penalties got forgotten, and nobody could say who owed what without scrolling back weeks. The group didn't need another app to log into. It needed the two or three organisers who already track everyone by eye to have a faster way to do it.

So there are no participant accounts. An organiser or a helper marks each person present, late or missed by name, and the app derives everything else from that: whether a challenge is upcoming, active or finished comes from the start date and duration, not a status field that would otherwise drift out of sync. Missing a day writes the penalty and takes a life automatically; marking someone present again undoes it. Any past day can be reopened to fix a mistake weeks later — add a penalty, remove one, write down what the task actually was.

Firestore rules do the real enforcement: only an organiser's role can write attendance or penalties for a challenge, checked on every write, not just in the UI. Strava connects per person, so a run can be verified instead of taken on trust.

AI tools were part of this one. Claude and Cursor, mostly for UI iteration and Firestore rule debugging. The data model and the access rules are mine.

The day view: each participant marked present, late or missed, with penalties beside the ones who missed

say hello

Hiring, or want
something built?

vladworktime@gmail.com

Based in Vancouver, BC. Email is the fastest way to reach me.