I owned the journey from the resident’s invitation to the guard’s verification and the administrator’s record. That meant making permissions, feedback and entry history feel connected across very different responsibilities. I also designed the resident–landlord sub-application and built the shared component library, brand identities and development references that helped the team carry one coherent product from design into development and delivery.

My focus was the work behind each transaction: what a corporate user needs to initiate, what an approver needs to review and what an administrator needs to control. I developed shared interface patterns so that permissions and responsibilities could change without making the product feel unfamiliar. The case study follows those decisions across payment workflows, administrative controls and the underlying design system.

I reshaped the mobile design system around repeatable interactions, clear form states and understandable payment feedback. The work covered GAMSWITCH, instant payments and the route from choosing a transfer type to knowing whether it succeeded. Rather than treating each service as a separate interface, I designed the relationships between them, keeping common tasks recognisable as customers moved through the app.

I focused on the decisions staff make during payment operations: finding a record, understanding its status and keeping transaction evidence close at hand. I worked on the shared design system and the states behind its tables, forms and feedback. The result is a consistent operating experience across payment collection and administration, designed around the work bank teams need to complete.

The goal is a connected operational tool for dispatchers and drivers, built around assignments, trip progress and the events behind location data. I have built the frontend and reusable components while backend development continues. The case study shows how product rules informed the interface, and how the same system carries through brand, interaction and implementation.

I connected the vendor’s setup and management tools with the customer’s shopping journey, so a storefront could grow from an existing audience. Building a shared component system helped those two sides feel like one product. Working closely with Pius, I carried the decisions from structure and interaction into delivery, turning the initial idea into something businesses could use and recommend.

Starting as the first designer meant defining the foundation while designing the product itself. I worked with the founder and team to connect how people create, share and read, then used reusable components to make those journeys feel related. The identity and motion belonged to that same system. This case study brings together the interface decisions, brand applications and a recorded walkthrough of the product I helped shape.

I started without a client brief, using the idea of a connected workspace to bring everyday team operations together. My work covered employee information, quick creation, project review and the decisions around attendance and leave. I owned both the interface and the build, so the structure had to work beyond a set of screens. This case study shows how I approached those recurring tasks and carried the product from its early idea through to acquisition.

The starting point was a simple question: what would make this feel worth returning to? I explored a playful visual identity, clear turn-taking, useful answer feedback and results that connect a round to a player’s progress. The screens show the core experience I designed. Rewards and money-based play remain future concepts, with verification planned before those features can be used. This is an exploration of product direction, not a launched game.

The work connects onboarding, business information, bank setup and the financial starting point into a more understandable mobile journey. I designed the illustrations myself so the visual language would support the experience, then carried invoicing beyond the design file into implementation. The screens shown here cover part of that work, from the welcome experience to entering financial information. Development is ongoing, so the story focuses on the product decisions and contribution rather than claiming a finished launch.