Quick contact

Leave your contact and we will write first

A number, an email or a Telegram handle, whatever is at hand. We will work out the rest.

Where to reply

Mobile apps · 02

An app for your team

Your technician sees their jobs on the phone, photographs the work, takes the customer's signature and closes the job on site. The office sees it straight away, with no spreadsheet in the evening and no voice notes in a messenger.

  1. 01You tell us who on your team works away from a desk and what they record
  2. 02We clarify the details by message or a call
  3. 03We give you the price and timeline of the first version

Not sure an app for your team is what you need? Compare it with the other apps

What's included

What the work includes, and where it ends

Everything in the first list goes into every team app we build. The second we add separately, when it is actually needed.

includedseparately, if needed

  • Roles and access

    A technician sees their own jobs, a manager sees all of them, the storekeeper sees the stock. Each person sees only what they need.

  • Jobs and tasks

    The day's list, statuses, comments, reminders about what is urgent.

  • Photos, signatures, scanning

    Before and after photos, the customer's signature by finger, a barcode or QR code from the phone's camera.

  • Offline work

    What gets recorded in a basement or out of town is saved on the phone and reaches the office as soon as there is a network.

  • An office panel

    Jobs, people, stock and reports in the browser. You keep the lists and addresses yourselves.

  • iOS and Android

    One codebase for both systems, so it runs on the phones your team already has.

  • Installing on the team's phones

    The app reaches your people through a link or device management, with no public store listing.

  • Code and accounts in your name

    The developer accounts, repository and server are yours, with notes for the next developer.

Separately

  • Accounting or CRM sync

    Jobs, customers and stock move between the app and your system without manual copying.

  • A tablet version

    A separate layout for the warehouse or workshop, where a tablet stays in place and people take turns using it.

  • GPS trackers

    Connecting vehicle trackers, so routes and time on site come from them rather than from what people report.

Typical structure

What a team app is made of

This is an example for a field service. In a warehouse there is goods in and goods out instead of a map, but the skeleton is the same: who you are, what to do, doing it, reporting it.

  1. Sign-in and roles

    Sign-in · Role

    Everyone sees their own

  2. My tasks

    Today · Statuses

    Instead of a list in a messenger

  3. Job card

    Photos · Signature · Comment

    Proof of work, gathered on site

  4. Stock and scanner

    Scanner · Stock levels

    What was taken and what was fitted

  5. Site visits map

    Route · Addresses

    Who goes where today

  6. Report

    By day · By person

    What used to be put together by hand in the evening

How the work goes

What you have in hand after each step

One technician tries the app on real jobs long before the whole team gets it. Mistakes in the flow show up on the first site visit, not after launch.

  1. 01Conversation

    We go through who on the team records what, where time gets lost and where there is no connection.

    In hand

    The roles, a list of screens and the scope of the first version

  2. 02Prototype

    Screens as a wireframe, no colour: the path from a job to a report for each role.

    In hand

    A clickable outline you can walk through on a phone

  3. 03Design

    Large buttons for work in gloves and in sunlight, every state: an empty list, an error, offline.

    In hand

    Mockups of every screen

  4. 04Build

    We build in parts, and each part goes to one or two people for real jobs.

    In hand

    A test build on your team's phones

  5. 05Launch

    We install the app for the whole team and walk the office through the panel.

    In hand

    The app on your team's phones, access and a guide

Price and timeline

What the price and timeline depend on

We don't publish a figure in advance: an app for one role and an app for four differ several times over. We name the price of the first version after the brief, and agree on each next stage before it starts.

The diagram shows six screens, three of them shared by different roles, one that works offline, and one accounting connection.
01Roles and flows
How many different people use the app, and how what each of them sees and does differs.
02Offline work
Which screens have to work in a basement or out of town. Each of them is more complex than an ordinary one.
03Accounting and CRM
What has to flow between the app and your system, and whether your system can exchange data at all.
04Data you already have
How many customers, addresses and stock items we move over from spreadsheets or an old program.

After launch

The app grows with your team

You add new people, addresses and lists yourself in the panel. A new screen is added as a stage, under a monthly hours package or as one-off work. The app has to be updated for new iOS and Android versions every year: that is part of the package too.

  1. 01Launch

  2. 02In 3 months

  3. 03In six months

added by you: people, addresses, listsadded with us: a new screen

The timings are illustrative: an example, not a plan.

You, in the admin

  • New people and roles
  • Addresses and sites
  • Lists of jobs and products
  • Access for people who have left
  • Report templates

With us

  • A new screen or role
  • Updates for new iOS and Android versions
  • Connecting one more system

Common questions

About team apps

  • Does the team need an app, or is a browser portal enough?

    An app is needed when people work in the field: without a connection, with the camera, a scanner and a map. If the team is mostly in the office filling in forms, a browser portal is enough, and an app can be added to it later.

    An app. An icon on the phone, the camera, a scanner, a map, offline work. When people are on site visits, in the warehouse or on the road and record the work where they do it.

    A browser portal. Opens from a link on any phone or computer, nothing to install. When the team is mostly at a desk and what matters is everyone seeing the same jobs.

    A portal and an app. The same jobs, people and lists in both. When the office works in the browser and the field on the phone.

  • We name the price of the first version after the brief. It depends on the number of roles, offline screens, syncing with your system and the data we move over. We agree on each next stage before it starts.

  • Yes, on the screens that need it. In the first conversation we work out what gets recorded offline, and that is kept on the phone until there is a network.

  • Not through public store search. On the App Store it can be distributed through a direct link or Apple Business Manager, on Google Play as a private app for your organisation. We set it up.

  • Either. The app runs on iPhone and Android, so you don't have to buy new phones.

  • You switch off their access in the panel. As soon as the phone goes online, the app signs out and wipes the work data from it. Jobs, photos and reports stay on the server, not just on their phone.

  • Yes, as separate work. First we look at your system and what exactly has to flow between it and the app: jobs, customers, stock.

  • Yes, as a separate version with a different screen layout. The code is the same, so it isn't a second app.

  • You do. The repository, server and accounts are in your name, and the notes let another developer carry on.

Other apps

If you need a different app

A team app is just one of the kinds we build. Here are two more.

Write to usKyiv · UTC+2
Telegram@kraywarePhone+380 73 125 48 44

Tell us who on your team works away from a desk and what they record, and we'll tell you where the app should start.

  1. 01A link

    to the site, the mock-up or the repository, whatever exists

  2. 02What to change

    one sentence on what should become different

  3. 03Who it's for

    who will use it: your customers, your team, and how many