UI/UX design for screens a developer can build

What we design

We design product workflows for web, iOS, Android and shared-code apps. Screens include the states a simple mockup misses: loading, empty data, errors, offline use, denied permissions and failed payment. A marketing website can be scoped as web design, while account and product pages belong with the application workflow.

Typical jobs

A first release is a short list. We design the one job the product must do: how someone arrives, the action, the empty state before any data exists, and the way back out. Settings wait until that path is agreed. Otherwise they consume the schedule.

A design system job often starts as three text styles named Body. We name the type in use, the spacing, and components for what repeats: buttons, fields, lists, empty states. A Figma prototype is the review copy. You click the path, including one failure, before anyone builds it, and the person building it can mark a costly step while the screen is still a frame.

How a project runs

Send the product’s purpose, audience, launch platforms and decisions already made. Include any review or release date that affects availability. A finished brief is optional.

A known set of screens gets a fixed quote. One flow, a critique of a file you have, or a few new states fits hourly work. If the note stops at "an app for our industry," paid discovery comes first: the user flows, a screen list, and a written scope. You can stop there. The scope stays yours.

We agree the review sequence around the decisions still open: a user flow, key screens, a prototype and the reusable components. Your developer can review constraints before detailed handoff. The deliverable includes the Figma files, interaction states and implementation notes. Building the product is a separate scope, with checks against the approved design.

Figma, and the platform underneath

Day to day the file is Figma: frames, components, text styles, and a prototype of the paths that matter. When you already have a library, we add to it. Notes sit on the screen they explain.

Platform rules live in the frames. On iPhone and iPad, type has to grow, and a Home Screen widget is a separate layout when the product has a reason to be there. On Apple TV the type is larger and focus replaces the tap. On Android the back gesture and the system bars belong to the screen. On the web we design keyboard focus, a narrow width, and a slow connection.

Contrast, a name on each control, focus order, and a target large enough to hit are the same pass, not a later audit. We implement the technical side of WCAG. We do not certify compliance, and the file alone does not make a shipped product conform. A second language needs room for longer labels, and a chosen place for the switch. An offline screen says it is offline.

Who it is for

This suits founders or product leads commissioning a new workflow, agencies with approved requirements, and teams that want design beside an existing developer. We can take a prototype, missing states or a component library as a bounded sub-project.

If the brief is still open, paid discovery can turn it into a defined feature list and acceptance checks. If you already have a developer or agency, we can take a bounded part of the work and agree how it joins the wider project. Share the target date so we can assess capacity and dependencies before committing.

hehe.software is based in Vancouver, British Columbia. We work remotely with businesses across Canada and the United States.

What we can show you

Our owned products include Tifo, whose interface spans iPhone, iPad and Apple TV; Broski, with exact bill shares and offline use; and ICD Atlas, with reference lookup in multiple languages. These offer specific interface examples you can inspect. A proposed design for your product is checked against its own workflow, platform constraints and missing states, then handed over with the decisions a developer needs.

A finished brief is optional. A quote moves faster with the current product or a sketch, who it is for, the platforms in the first release, brand files if you have them, and the name of whoever will build it. An invite to the existing Figma file can wait until we have agreed to look.