IMtech
Discuss a project

Service

Mobile apps

We build apps for iOS and Android: workstations for staff and apps connected to your system. Data syncs with the server, and work doesn't stop when the network drops.

Discuss a project

Animation: cards scroll on a phone screen while data travels between the phone and the server — sync in both directions.

When you need it

Situations that bring people to us for this service.

  • Staff have no convenient tool

    People on shift, out in the field or on the shop floor note things on paper or in a messenger, and someone later re-enters it into the system.

  • No signal, no work

    An app that doesn't work offline stops the work or loses data.

  • The app and the panel live apart

    What staff do on the phone reaches the manager late — or not at all.

  • Two platforms, two builds

    Separate iOS and Android apps double the work, both in development and in support.

What's included

  1. Analysis and scenarios

    We work out who uses the app and where, what it must do first and what gets in people's way.

  2. Prototype and design

    Screens for real working conditions: short scenarios and a visible state for every action — accepted or not.

  3. iOS and Android from one codebase

    One codebase for both platforms — though we still choose the technology to fit the task.

  4. Offline work

    Records are stored on the phone first and sent as soon as there is a connection — nothing lost, nothing duplicated.

  5. Sync with the server and the panel

    An edit made on the phone shows up in the web panel, and access rules are the same on every screen.

  6. Scans, photos and notifications

    Barcodes and photos for reports and tickets straight from the phone camera; notifications about what needs action.

  7. Preparing for release

    We prepare the app for the App Store and Google Play, including the privacy notice and the account deletion page.

  8. Support and growth

    After launch we keep improving the app based on user feedback.

What you get

  • Scenarios and screen prototypes
  • An app for iOS and Android
  • A server side and web panel, if you need them
  • A pilot with your staff
  • Materials for release in the app stores
  • Code and documentation that are open to you

The project path

From the first conversation to daily use

Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.

  1. 01

    Getting to know the task

    You describe the process and what gets in the way. We reply by email with questions and arrange a call.

  2. 02

    Discovery

    We study the process with the people who work in it and write down what the system must change and how we will check it.

  3. 03

    Prototype

    We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.

  4. 04

    Pilot

    We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.

  5. 05

    Launch and growth

    We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.

Related case studies

Systems where we have already done this kind of work.

  • An automated production line on a factory floorPlaceholder photo
    PrototypeProduct: TermoHubpolymer products manufacturing

    Manufacturing tracking

    Shop-floor tracking of finished goods: scan at the station, build the shipment in the app, keep working with no network.

  • A reception desk in a hotel lobbyPlaceholder photo
    PrototypeProduct: Vatrahospitality and food service

    Restaurant and hotel operations

    One system for hotels and restaurants: rotas, training that gates shift access and maintenance tickets, in staff apps and a manager back office.

  • An open planner on a deskPlaceholder photo
    PrototypeProduct: Flowiproject, finance and health management, own product

    Projects, finance and health management

    IMtech's own product: managing personal and company projects, plus a finance tracker and a health tracker, in one system across phone, browser and desktop.

Technology in these case studies

  • Strapi
  • PostgreSQL
  • Socket.IO
  • Expo
  • React Native
  • Next.js
  • Django
  • Tauri
  • WebSocket
  • Apple Health
  • Google Calendar

Questions about this service

Separate apps for iOS and Android, or one?

Usually one codebase for both platforms: that means less work in development and in support. We still choose the technology to fit the task.

Will the app work without internet?

Yes, if the work requires it. We have already built apps where records are stored on the phone and sent as soon as the network is back — nothing lost, nothing duplicated.

Will you help with release on the App Store and Google Play?

Yes. We prepare the app and what the stores need: the listing description, the privacy notice and the account deletion page.

How does the app connect to our system?

Through the server: the app exchanges data with it, and the server with your accounting system or other software. Access rules are the same in the app and in the web panel.

Other services

All services

Have a project with no ready-made solution?

Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.

Get in touch