Menu

LanguageEnglish
Talk to us

From one sentence
to a system you can run

One team builds your web app, mobile app, and backend.
Type a request to see the process
using a prepared example.

Try
Online store with orders
Academy enrollment and billing
Clinic booking app
Purchasing and inventory
Field inspection reports

How a service takes shape

Explore structure, screens, testing, and release with a prepared example.

Example
Online store with orders
Academy enrollment and billing
Clinic booking app
Purchasing and inventory
Field inspection reports
01 Structure Waiting
  1. 01Structure12 data models, 3 permission levelsWaiting
  2. 02Components18 screens built from the design systemWaiting
  3. 03Testing46 tests passedWaiting
  4. 04ReleaseWeb / Mobile / AdminWaiting
Talk to us

Try them as sample apps

In your browser, no sign-up, with sample data

  • 160+

    Design system components

    From buttons to tables, shared by app and web

  • 5

    Platforms from one codebase

    Web, iOS, Android, macOS, Windows

  • Weekly

    A working interim version

    Track progress through links and test apps

We estimate after defining the scope

We map the screens and workflows you need, from customer apps to admin tools and the backend.

  1. 01

    Screens

    Customer-facing + admin

  2. 02

    Platforms

    Web only / Web + app / All

  3. 03

    Integrations

    Payments, notifications, internal systems

  4. 04

    Plan · Design

    Whether you have a spec, or need screen planning first

After consultation, we spend one week defining scope and proposing a screen list and quote. Development time and the start date depend on features, platforms and integrations.

Store accounts, hosting, domains and third-party fees are agreed separately from development costs.

Work you can hand us

We build new services, improve existing ones, and support them after launch.

01 / 03

New

Build a new service

Start with screens and the first release, even without a written spec

02 / 03

Refactor

Improve or take over a service

Review code and operations, then agree takeover scope and priorities

03 / 03

Operate

Operations and maintenance

Checks, updates and improvements within the agreed support scope

Share common features across platforms

We share common parts of screens and features instead of rebuilding them from scratch on every platform.

One code repository serves five platforms (web, iOS, Android, macOS, and Windows), and all of them use the same server and data.

ONE CODEBASE

One code repository

160+ CoUI components

  • WebWEB
  • iOSIOS
  • AndroidAND
  • macOSMAC
  • WindowsWIN

BACKEND

Shared server and data

Every client uses the same data

Your repository and accounts stay in your name

After development, you can run and extend it on your own.

HANDOFF PACKAGE

Copyright passes to you on acceptance and full payment

01REPOSITORY

Repository

Source code and commit history

  • All source code
  • Full commit history
  • In your organization from day one
02ACCOUNTS

Accounts

App store and cloud ownership

  • Store developer accounts
  • Servers and domains
  • Admin access for your team
03DOCUMENTS

Documents

Data structure and deployment steps

  • Data models
  • Environment variables
  • Deployment steps

Six items in total, including a handover session and a CoUI license

Everything you get

FAQ

Can we use what the demo builds?

Not as is. The demo picks the example closest to the sentence you typed and shows how a one-line request becomes structure, screens, testing, and release. A real service is built in the same order, after we work out the requirements with you in a consultation.

Do you use our input and code to train AI?

What you type into the demo on this page is not sent to a server. It is only matched against prepared examples inside your browser, so it does not leave your browser until you send us a contact request yourself.

In real projects, we develop by sending parts of the code and specifications to AI tools. Before the project starts, we give you a list of which tools we use and on what terms, and if we change tools, we tell you before the change.

How is pricing determined?

Price depends on workflows, roles, integrations, target devices and acceptance checks. Amounts follow the scope organized after a consultation, so start with the quotation sample and pricing criteria to see how a quotation is structured.

How long does it take?

After a consultation we spend one week organizing the screen list and scope, then propose a quotation. The actual build time depends on screens, integrations, device testing and store review. We share a working preview each week.

Tell us about your service in three lines

Who will use it, what must it do, and when do you need it? We will work out the scope together.