03 · WEB & MOBILE APPS
Web and mobile products, from prototype to release cadence
An interface is where every architectural decision becomes something a person either understands or abandons. We build the front end and the design system behind it, so the second release is as fast as the first.
- UX & UI Design
- Web Applications
- iOS & Android
- Design Systems
What we build
Design and engineering as one track, because handing a static file to a developer is where most of the intent gets lost.
UX and UI design
Discovery, flows and prototypes. Interfaces that make complex systems feel obvious rather than merely look considered.
Web applications
Server-rendered where it matters for speed and search, client-side where it matters for interaction. Accessibility treated as a requirement, not a pass at the end.
iOS and Android
React Native where sharing a codebase is the right trade, native where it is not. We will tell you which.
Design systems
Tokens, components and documentation that survive contact with engineering — the thing that makes release four as cheap as release one.
Accessibility and performance are not a later phase
Contrast, focus order, keyboard paths and reduced-motion handling are built in as the interface is built. So is performance budgeting: a design that only works on a fast laptop is not finished.
2 of these are live right now
Not a portfolio of screenshots — every one of these opens.
H&B Event Solution
Event production storefront
A production-grade brand site that leads with the work: full-bleed event photography, a service breakdown for 3D stall fabrication, SMD screens and sound, a portfolio clients can share, and quote requests captured as structured enquiries instead of chat messages.
hbevents.me ↗Axiom
Private research instrument
A research workspace that turns a question into a defensible trail: it reads sources, separates claims from reasoning, and keeps the link between them. Reports stay in a private library with a source collection per project, and the workspace shows how much research context a report consumed.
axiom-agent-three.vercel.app ↗
What we build on
- Next.js
- React Native
- Figma
Halyx is not religious about the stack — it picks what your team can maintain — but these are the defaults it is fastest and safest in.
Questions we get asked first
- Can you work from our existing designs?
- Yes. We will also say plainly if a design will not survive implementation — earlier is cheaper than later.
- Do you build design systems as a standalone piece of work?
- Yes, and it is worth doing before a second product rather than during it.
- Will it work on a mid-range Android?
- That is the device we test against, because the laptop the design was made on is not a useful benchmark.
The other four practices
Talk to the people who would build it
The first conversation is a scoping call, not a pitch: what you are trying to move, what already exists, what the constraint is. It ends with either a range and a proposed first step, or a straight answer that Halyx is not the right fit.