About

We love this work, and it shows.

Kakadu Labs is a software studio. We treat every project like it's our own product: we enjoy the details, we finish what we start, and we stand behind everything we ship.

It starts in the design fileFlows, states, and every edge case drawn out before a line of code exists, so we argue about pixels early instead of in production.

Green before it shipsTests run on every change. If the suite is red, nothing goes out. No exceptions, no "we'll fix it after launch".

ApiClient.javaApiClientTest.java

src › main › java › com › kakadu › api › ApiClient.java

1package com.kakadu.api;

3import java.net.http.HttpClient;

4import java.net.http.HttpRequest;

5import java.time.Duration;

7/** Thin wrapper over the JDK client: typed, timed out, mapped. */

8public final class ApiClient {

10 private static final Duration TIMEOUT = Duration.ofSeconds(10);

12 private final HttpClient http;

13 private final ObjectMapper mapper;

15 public ApiClient(HttpClient http, ObjectMapper mapper) {

16 this.http = http;

17 this.mapper = mapper;

18 }

20 public <T> Result<T> get(String path, Class<T> type) {

21 HttpRequest request = HttpRequest.newBuilder()

22 .uri(URI.create(BASE_URL + path))

23 .header("content-type", "application/json")

24 .timeout(TIMEOUT)

25 .GET()

26 .build();

28 try {

29 var res = http.send(request, BodyHandlers.ofString());

30 if (res.statusCode() >= 400) {

31 return Result.failure(new ApiException(res.statusCode()));

32 }

33 return Result.success(mapper.readValue(res.body(), type));

34 } catch (IOException | InterruptedException e) {

35 throw new ApiException("request_failed", e);

36 }

37 }

38}

⎇ main*0 problemsLn 21, Col 34TypeScript

Code we'd be happy to hand overTyped, reviewed, and readable. The repository is yours from day one, and it's written for whoever opens it next.

We sweat the details

A screen doesn't ship because it's good enough. The empty state, the loading time, the way a button feels: we keep at it until it's something we'd happily show off.

With you start to finish

The people who scope your project are the ones who build it, launch it, and look after it once it's live. Nothing gets handed off halfway.

Products, not hours

We scope the outcome and quote in writing. You pay for a working product, not a timesheet.

Process

What working with us actually looks like.

Week 0

Discovery and quote

You get it in writing: what we'll build, what we won't, and what it costs. Not a line of code is written before the scope is settled.

Week 1

A build you can open

By the end of the first sprint there's a working version on your phone. We move with software, not slide decks.

Every Friday

Demo day

We show you what shipped this week, live, and pick the next thing together. The project board stays open, so you never wait on us to know where things stand.

Launch

Stores and deployment

We handle the App Store and Google Play submissions, the deployment, and the monitoring. You're not on your own on launch day.

After

We don't disappear

Once real users arrive we measure, fix, and improve. The interesting part of the job starts here.

In writing

Our commitments

Everything we promise, we put in writing.

A scoped, fixed quote before we write any code.
A repository in your own account from day one. The code and the design files are yours.
A weekly demo call and a project board that's open around the clock.
A reply within two business days, every time you write.
No handover fee and no lock-in. If you want to leave, you leave with everything.

What we build with

Chosen for the job, not for the hype. We pick mature, boring tools that will keep your product standing for years.

TypeScriptNext.jsReactFlutterGoJavaPostgreSQLFigmaAWS

Want to work with us?

Tell us about your idea. We reply within two business days.

Get in touch