A web application is software you use in a browser. A progressive web app (PWA) is a web application that can also be installed on a phone or computer. We build both, for tools people use every day.
What is a PWA good for?
A PWA suits software that people open many times a day, on a phone, at work. It installs from the browser, it has its own icon, and it can send notifications. There is one codebase to build and test, not three.
Two of our products work this way. Kommo, a hiring marketplace for hair salons and barbershops, is an installable web app. Mesito, a real-estate CRM, is installed on phones and desktops, with a map-first interface and a Today view for what needs a reply.
PWAs have limits. Push notifications and background tasks are less reliable on iPhones than in a native app. We do not build native iOS or Android apps. If your product depends on those features, we say so at the start.
What kinds of web apps do we build?
- Marketplaces and portals. Two or more sides, such as businesses and applicants, with search, profiles and messaging.
- Internal tools and CRMs. Records, roles, approvals and reports for your own team.
- Operations software. Scheduling, reconciliation and audit trails. Our operations and workforce CRM shows how finalised records lock and corrections keep their history.
- Client portals. A place where your customers see their own status, documents and invoices.
What makes an app fast on a phone?
Most users are on a mid-range phone and an unsteady connection. So we keep the first screen light, load the rest when needed, size images properly and avoid layout jumps. The pages that matter for search are prerendered. The screens behind a login can be rendered in the browser, since they do not need to rank.
How do we handle integrations?
Most useful software talks to something else: email, SMS, maps, payments, a website or another vendor’s system. We put each integration behind its own small layer, so that changing a provider means changing configuration, not rewriting the app.
Examples from our products: Mesito has an AI assistant that works in Greek and is built on the Claude API. Forkly sends email notifications, with SMS and Viber ready to switch on. Both depend on providers we can swap.
How do we keep the app maintainable?
- A typed codebase, with tests on the rules that matter.
- Data in PostgreSQL and files in object storage, so the app can run on more than one server.
- Database changes made in stages, so a release does not break the running version.
- Monitoring and backups from day one.
Where to go next
The software service page covers how we work overall. If you will serve many customers from one app, read about SaaS platforms. To discuss your app, contact us.