Web and mobile apps
A PWA that works like a native app on iPhone and Android — installed from the browser, with no waiting for an app store.
Custom applications
Your application. As fast as native.
In shortA custom application is software designed around your company's processes: a web app, a mobile app (a PWA that works like a native app on iPhone and Android), an admin panel or a live dashboard. From the same codebase we can also prepare a version for the App Store and Google Play.
What we can build for you.
App Store and Google Play
When a company needs an app in the stores, we build a native layer on the same codebase (e.g. Capacitor) with phone features such as push notifications, the camera or offline mode. A website merely wrapped in an app does not pass Apple's review.
Admin panels and CMS
Management of content, users, roles and permissions — with a change log.
Live dashboards
Data refreshed in real time, including a TV mode for the office or the shop floor.
Integrations and automations
ERP, KSeF, public registers, email, webhooks — the app collects the data itself.
AI agents and assistants
Reading documents, summaries, answers to questions about company data.
Comments and helpdesk
Comments on documents, @mentions in tickets and a ticket inbox with assignment and statuses.
Email and push notifications
Approvals, alerts and reminders reach the right person on time.
Payments and subscriptions
Online payments, subscription plans and billing built into the app.
Sign-in with 2FA
Password plus a TOTP code or a passkey, roles and invitations.
Analytics
You see what users rely on and where the app saves time.
PWA and app stores
One codebase. Three platforms.
We start with a web application and a PWA — you install it from the browser and it works like a native app on iPhone and Android. When you need a presence in the App Store and Google Play, we extend the same codebase with a native layer and phone features. No three separate projects and three budgets.
Example: the time-tracking app in Business Panel — installed from the browser, with push notifications and location logging.
Live dashboards — also in a TV mode for the office or the shop floor.
Performance you feel from the first click.
- to load views in our panels — no waiting
- ~0.5 sto load views in our panels — no waiting
- people working live in a single panel at the same time
- 40–50people working live in a single panel at the same time
- very active users at once in a load test on a single server
- ~300very active users at once in a load test on a single server
- of running automations that do people's work every day
- Hundredsof running automations that do people's work every day
Data from our deployments and a load test: a single server handled about 300 very active users at once, and the estimated headroom at full load is about 350–400. This is not a guarantee — performance depends on scope and infrastructure.
From workshop to application in 2–3 months.
Workshop
1–2 weeksWe learn the process, the people and the data. We agree what will bring the biggest effect the fastest.
Prototype
2–3 weeksClickable screens and architecture. You see the app before the code exists.
MVP
4–8 weeksThe first working version in users' hands — usually 2–3 months from the start of the project.
Growth
ongoingMonitoring, fixes and further modules based on what the team really uses.
Technologies
- Next.js
- React
- TypeScript
- Python (FastAPI)
- PostgreSQL
- Redis
- Docker
- Claude, Gemini, Mistral (AI)
Need an ERP or KSeF integration? See KSeF and Comarch integrations. Want to automate your team's work? See automation and AI. The full list of tools: technologies and integrations.
Custom applications — questions and answers
How is a PWA different from a native app?
A PWA (progressive web app) is a web application that you install from the browser onto your phone's home screen. It works like a native app — full screen, an icon, notifications — but it has a single codebase and updates without an app store. A native app goes to the App Store and Google Play and has broader access to phone features. We usually start with a PWA. If a presence in the stores is needed later, we extend the same codebase with a native layer.
Can the app be published in the App Store and Google Play?
Yes. We build the App Store and Google Play version on the same codebase as the web app and PWA, adding a native layer (e.g. Capacitor). Apple rejects apps that are merely a wrapped website (guideline 4.2), so we agree the scope of native features and the time needed for store review at the start.
Will the app handle many users at once?
Yes. In our deployments 40–50 people work in a single panel at the same time, and views load in about 0.5 s. In a load test a single server handled about 300 very active users at once, with an estimated headroom of up to about 350–400. This is data from our projects, not a guarantee — performance depends on scope and infrastructure.
How long does it take to build an app?
The workshop takes 1–2 weeks, the prototype 2–3 weeks, and the first working version (MVP) is usually ready after a further 4–8 weeks of implementation, which means 2–3 months from the start of the project. After that we develop the app in stages.
What technologies do you build apps with?
Most often Next.js, React and TypeScript on the front end, Python (FastAPI) or Node.js on the back end, PostgreSQL and Redis as databases, Docker for deployments, and AI models (Claude, Gemini) where they bring real value.
Let's talk about your app.
Tell us what takes your team the most time today. The first conversation and a preliminary analysis are free, and we reply within 24 hours.