Apps that people enjoy using.

We build them for iOS and Android, from the first screen to release in the stores.

What does building an app involve? Play the video and see how an app comes about here.

Marek Kejda, founder

How we work

Three things every app of ours stands on.

A design that sits well in the hand

First we draw the screens and click through a prototype. Before we write a line of code you know exactly how the app will look and work.
Native performance on iOS and Android

One code base, smooth on both platforms. No stutter, no waiting: the app responds the way people expect.
Release to the stores and care afterwards

We take the app through review in the App Store and Google Play and keep looking after it: updates, measurement and fixes are off your plate.

When an app is worth it

Not everything has to be an app. These three things a website cannot do, though, and when you run into one of them an app is the right answer.

People come back to it

When somebody has a reason to open it every week, an icon on the home screen is closer than an address in a browser.
It needs the phone, not just a screen

The camera, the location, a code scanner, or a notification that arrives with the app closed.
It has to work with no signal

The app keeps the data with it and catches up once there is a connection. In a warehouse and in a lift.

We enjoy design

We draw from a blank page, not from a template. Typography, rhythm and the details a visitor still remembers a few days later.

How we do design

Rive

Animation that notices the visitor. It reacts to a hover and to a click, and it does not just loop like a video.
Variable font

A typeface whose weight and size change smoothly. A tiny caption and a big headline still look like one family.
Lottie

An animation from a designer that fits into the page instead of a video. It is sharp at any size and weighs a fraction of a video. Click and the next smiley arrives.

Security

The sensitive part is what the app carries on the phone: the sign-in, the tokens, the data. So we leave keys in the system store, encrypt the traffic and ask for a permission only where the app really needs one.

First-rate security is not an extra. It is the way we build apps.

And there is a lot more!

Design and prototype

Screens drawn out from the first sketch to a clickable prototype
Visual style colours, type and components that hold together
Icon and store graphics previews and copy exactly as the stores want them
One-handed use legible type, contrast and everything within a thumb

Building the app

iOS and Android from one base one codebase, two platforms, the same behaviour
Works without a signal the app carries on and catches up once it is back online
Push notifications the message arrives even when the app is closed
Camera, maps and location code scanning, sharing or Bluetooth as needed
Sign-in and accounts by e-mail, through Apple ID or Google, or a fingerprint

Connecting to your systems

APIs and webhooks the app talks to what your company already runs
Data in sync a change in the system shows up on the phone right away
Payments in the app a payment gateway as well as App Store and Google Play purchases
Content without a new release you change the words and the offer yourself, no update needed
Roles and permissions everyone sees what they should, from a temp to the board

Release and care beyond it

Approval in the stores we walk the app through review in the App Store and on Google Play
Test builds TestFlight and internal testing before the public sees it
Crash reporting we know about a fault before you get to report it
Behaviour measured you see which screens people actually use
Updates new versions and answers to changes in iOS and Android

What you ask most often

What does building an app cost?

By the scope, not by a price list. An app of five screens is one thing, one wired into a warehouse and payments another. A small app can be built from €2,800.
How long does it take?

First we draw the screens out and you click through a prototype, only then is it built. Once we know exactly what is to be built, we give you a date and then we keep it.
Will you make the app for iOS and Android?

Yes, from one codebase. One code, two platforms and the same behaviour on both, so nothing is done twice.
Can you take over an app we already have?

Usually yes. We look at what it runs on and say whether it is worth improving or rebuilding.
Do you look after the app after release?

Yes. We walk it through review on the App Store and Google Play and carry on from there: updates, crash reporting and fixes.