Web app and PWA development

Customers book, order and ask about their status, and someone on your team copies it all from email and phone calls into yet another spreadsheet. If that is what your day looks like, an informational website is no longer enough and web app and PWA development comes in: users log in, enter data, book and order on their own, and you see the whole process in one place, from any device, with permissions set the way you want.

A Progressive Web App goes one step further. It runs in the browser, but it can be installed on the phone's home screen, opened without the address bar, used with no signal, and it can send push notifications. Users will only notice that they never had to download it. You maintain one codebase instead of separate iOS and Android versions, and every fix ships the moment you deploy it, with no store approval to wait for.

Not every project needs an app. If what you are after is enquiries and calls from new customers, a well-built business website will do more for you, and you will hear that from us on the first call, before we prepare a quote. An app built without a real need leaves you with a maintenance bill that never comes back as saved time or sales.

We set the scope from the problem you want to solve, because a feature list borrowed from a competitor rarely matches what your people actually use. Each item below can be ordered on its own or combined into one app, and features nobody needs on day one move to later stages, so the first version launches sooner. If you already have a system with an API and only need an app for your field team, we build just the PWA on top of it.

We work with React and Next.js, and with a Postgres database wherever the app needs a backend. It is a mature, widely used stack, so if you ever hand the project to another developer, they will find their way around it quickly.

• Web applications on React and Next.js, from admin dashboards to client portals, with the full range of features.

• PWA with home screen installation, offline mode and push notifications, no app store download required.

• An interface built for the phone, with gestures, a correct viewport and safe areas, so buttons never hide under the notch or the system bar.

• API integrations (REST, GraphQL, webhooks) with your CRM, invoicing and the other systems you already use.

• Login and roles

  user accounts, sessions and permissions set so that everyone sees only what they should.

• Offline layer

  Service Workers, IndexedDB, the Web Push API and the PWA manifest.

The first conversation is about your process. We work out who will use the app, what they do step by step and where they lose time today. That becomes user flows and a clickable prototype you test before we write the first line of code. On larger projects this stage runs together with strategy and direction, so the scope follows the goal the app is meant to reach in your business.

The interface is designed as part of design that sells: phone first, with gestures, thumb reach and small screens in mind. Coding starts once the scope is approved. You follow progress on a staging address, so you can click through, test on your own phone and send feedback while the work is in progress, long before sign-off.

Before launch we check on real devices that the PWA features you care about work for your users, iPhones in particular. Deployment runs through CI/CD, and production errors land in monitoring before a user has time to report them. After launch you get the access details, documentation and training on the admin panel, so you change day-to-day content and settings yourself.

Choose a PWA when the app has to work on every device, you want to maintain one codebase and you do not need deep access to the phone's hardware. It costs less, ships faster and skips the Apple and Google commission. For most business use cases that is enough, and users still get an icon on their home screen.

When you need full hardware access, such as the camera, Bluetooth or sensors, or you have to be in the App Store, we wrap the same code in a native shell with Capacitor. Both routes are detailed in our mobile app for iOS and Android offer. If Google Play is all you need, we publish the finished PWA there without rewriting the code. We make this decision at the start of the project, because switching routes halfway through costs the most.

• PWA

  installs from the browser, works offline, sends push and puts the new version in users' hands the moment we deploy.

• Capacitor

  the same app in a native shell, with access to the camera, GPS, biometrics and files.

• Google Play via TWA

  your finished PWA in Google's store through Trusted Web Activity, no new code.

The order of magnitude is below; the exact price follows a conversation about your process. A web application starts at PLN 15,000 net and takes 4–16 weeks: a simple dashboard usually 4–6 weeks, a full platform 8–16 weeks. A mobile app as a PWA costs from PLN 12,000 net, a Capacitor version from PLN 18,000 net, and a simple PWA is ready in 3–5 weeks.

What moves the price most is the number of roles and permissions, integrations with external systems, payments, offline mode and whether the app has to be in the stores. You get a free quote with the scope written out and a schedule within 48 hours of the call; we set the price before we start and stick to it. We often suggest starting with a smaller scope, so the first version reaches users sooner and further work is based on how they actually use it. The three features below usually come as separate items; their prices are also in our pricing.

• Offline mode and data sync

  from PLN 2,500 net. Data saved locally syncs on its own once the signal is back, which is what field apps and internal tools need.

• Push notifications

  from PLN 1,800 net. Web Push gets through even when the app is closed, and you set the content and recipients in the admin panel.

• Google Play publishing (TWA)

  from PLN 1,200 net. Configuration, certificates and help with Google's review process.

We most often build three kinds of projects. The first is an MVP for a startup: the smallest version of the product that lets you test the idea with real users before you spend the budget on a full platform. The second is a SaaS client portal, where your customers log in, see their data and sort out their account without emailing you.

The third is tools for companies that run a process in spreadsheets and email, and apps for teams in the field, where signal is patchy and offline mode is a must. A PWA also works well for services customers use every week, in loyalty programmes and bookings. A process that repeats regularly and ties up the same people every time is a good candidate for an app.

The code, the database, the domain and the service accounts are yours. You get the access details and the documentation at sign-off, so you can keep developing the app with us or with any other team, without asking us for permission. For 30 days after sign-off we fix any bugs that come from our code free of charge. A PWA update is instant: we deploy the new version to the server and users get it the next time they open the app, with no store review and no asking them to download anything.

An app rarely works on its own. Payments, CRM, email and invoicing are connected through integrations and automation, and monitoring, fixes and new features after launch are covered by support and growth. One person, Kacper Baranowski, runs the project from the first call to launch, so you explain your process once, to the person who will then build it. Tell us in the contact form what that process looks like today and who handles it. You will hear back by the next business day at the latest, and within 48 hours of the call you will have a quote with the scope and schedule written out.