ZL STUDIOStart a project

Services

What we build.

We build digital products designed around real problems. Most projects need some of all three of these, which is why we do all three rather than handing you a design nobody can build.

01

Mobile apps

One codebase, both stores. React Native and Expo, with native modules where the platform demands them.

  • iOS and Android from one codebaseReact Native and Expo, native modules where needed.
  • Everything the phone can doMaps, camera, location, push, calendar and deep links.
  • Sign-in people already havePhone, Apple and Google.
  • Into the stores, not just builtSigning, provisioning and store submission.
  • Tested before the public sees itTestFlight and Play testing tracks.
  • Fixes that skip the queueOver-the-air updates, so a fix does not wait on review.

02

SaaS platforms

Web products with a real backend underneath. The part that is easy to demo and hard to run is the part we plan for first.

  • Accounts and access controlRoles, permissions and per-row authorisation.
  • Secure, scalable data architectureSchema design, migrations and row-level security.
  • Automation and integrationsBackground jobs, scheduling, webhooks and third-party APIs.
  • Getting paidPayments and subscription handling.
  • Tools to run it after launchAdmin tooling, so support does not mean a database client.
  • Knowing when something breaksLogging and alerting you will actually read.

03

Product design

Designed on a phone first, because that is where it will be used. Behaviour and flow, not decoration.

  • Decided before it is drawnFlows mapped before screens are.
  • Works one-handedInterfaces built for the thumb zone.
  • The states nobody demosEmpty, loading, error and offline, designed rather than defaulted.
  • Usable by everyoneAccessibility treated as the same job, not a later pass.
  • Design the build enforcesTokens checked at build time, not by eye.
  • No dark patternsAnd we will say so if you ask for one.

Technology

Built with technology we actually ship.

Not a capability matrix. These are the things we have put in front of users and then had to keep running.

Mobile

  • React Native
  • Expo
  • iOS
  • Android

Web

  • React
  • Next.js
  • TypeScript
  • Astro

Backend

  • Supabase
  • PostgreSQL
  • Node.js
  • REST and RPC APIs

Infrastructure

  • Cloudflare Workers
  • CI/CD
  • Store releases
  • Over-the-air updates

Engagements

Three ways this usually starts.

Build a product

From an idea or a half-finished prototype to something in the stores. Scoped in phases, with working software from the first week.

Rescue a build

A project that stalled, a contractor who left, an app that will not pass review. We are usually happy to pick these up.

Take one over

Ongoing work on something already live. Releases, fixes, new features, and the maintenance nobody enjoys quoting for.

We scope and price each phase before it starts, so you are never approving an open number. If a phase turns out to be smaller than we thought, it costs less.


Not sure which of these you need?

Describe the problem rather than the solution. Working out which one it is is part of the job.