Mobile app

You want an app on your customers' phones and wonder whether iOS and Android mean paying twice. With us they do not: we write one React codebase and the same code runs on both systems. You order a new feature once, one fix repairs a bug for iPhone and Android users at the same time, and neither version waits for the other to catch up.

A mobile app pays off where customers come back regularly: a service they use every week, a loyalty programme, bookings, a tool for a crew in the field. An icon on the phone and a push notification remind people about you without an advertising budget. If a customer looks you up once a year, a fast business website will cost less, and you will hear that from us on the first call.

Before we draw the first screen, we settle on the one thing a user should get done faster in the app than on a website: book a slot, collect points, report a finished job. The home screen, the navigation and the wording of notifications are designed around that action. Further features come once the first version has users and shows what they actually need.

The code is the same either way. They differ in where users get the app from and which hardware it can reach. A PWA is enough if you can do without the App Store and without Bluetooth or sensors: it installs from the browser, works offline, sends push and skips the Apple and Google commission. Capacitor is the choice when you need native APIs or want to be in the stores. For most business uses a PWA does the job and costs less.

Capacitor wraps the same app in a native shell, which means you can start with a PWA and add the store version later without rewriting the interface or the backend. When we quote, we will tell you which route pays off now and which can wait until the app has its first users.

Upkeep differs too. A PWA updates like a website: we deploy a new version and everyone gets it at the next launch. A store version needs a prepared release and Apple and Google review, and every fix reaches users later. We recommend the stores when they give you something specific: native features, or customers who look for apps there.

• PWA (Progressive Web App)

  installs from the browser, works offline and sends push, with no Apple or Google commission; every update reaches users at once, with no review

• Capacitor (hybrid native)

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

• A shared foundation

  one React codebase, one backend and one interface design, whichever route you choose

The code is built under our apps and PWA service and the interface under design that sells, which on a phone means designing for the thumb: bottom navigation and buttons where the hand holding the phone can reach them. We test the prototype on real phones, because a monitor will not tell you whether a gesture feels natural or the keyboard covers a form field.

Offline mode and data sync are planned from the first sketch. For a crew in the field, in a warehouse or on a building site, no signal is routine, and an app that shows an error at that moment is forgotten within a week. During design we decide which data has to be available without a network, what the app stores locally and what happens when two people change the same record before the phone is back in range.

• UX design for the phone

  user flows, a clickable prototype and testing on real devices

• React and Vite frontend

  an interface built for gestures, bottom navigation and swipes

• Push notifications

  web push in a PWA or native push with Capacitor, to remind people about you without a campaign

• Offline mode

  a service worker stores key data and the app works without a signal too

• Backend and sync

  Neon Postgres, data refreshed in real time, authentication and an API

• Distribution

  an install link for a PWA, a direct APK download or publication in the App Store and Google Play

In an app, motion is part of how it works: moving between screens, confirming that something has saved, a gesture that closes a card. Under animation and 3D we design micro-interactions and transitions that show what just happened without straining weaker phones. When a user turns on reduced motion in the system, the app respects it and stays readable.

The app plugs into the tools you already use. Through integrations and automation we connect it to payments and subscriptions, CRM, email and your booking system. Data entered without a signal syncs once the phone is back online, and nobody retypes a job after a day in the field.

Payments are planned around your business model: a one-off purchase, a subscription or a fee per booking. In a PWA a provider such as Stripe handles them, with no app store commission. For the store version we check the Apple and Google rules for your model before we design the payment screen, because a rejected release has to be fixed and sent through review again.

Kacper Baranowski runs the project personally, from discovery to release, and you explain your business once, to the person who then builds it. You check progress on your own phone: you install a test build and use it in everyday situations before customers see it. We collect your feedback while the work is in progress, when a change costs least.

If you are still testing a product idea, start with an MVP for a startup: a smaller scope and validation with real users before you invest in a full version with a backend, payments and an admin panel. A few weeks after launch, data will show which features to build on and which to drop.

• Discovery

  who uses the app, how often and what has to work without a signal

• Choosing the route

  PWA or Capacitor, depending on the hardware and distribution you need

• Prototype

  a clickable design you check on a phone before any code is written

• Build

  interface, backend, push notifications, offline mode and integrations

• Device testing

  the schedule has a buffer for checking the app on different phones

• Release

  an install link, an APK file or submission to the App Store and Google Play

A PWA costs from PLN 12,000 net. An app in a Capacitor native shell starts at PLN 18,000 net. A full app with a backend, payments and an admin panel is PLN 25,000–60,000 net. A free quote with the scope and schedule written out arrives within 48 hours of the call; the exact figure is set after discovery, before we start, and we stick to it. PWA extras, such as push notifications or Google Play publishing, are priced in our pricing.

A simple PWA is ready in 3–5 weeks, an app with Capacitor and a backend in 6–12 weeks. What moves the price and the timeline most is the number of screens and roles, offline work, native features, integrations and store publishing. If your users will mostly work on a computer, in the browser, look at a web app instead.

Prepare three things before the call: a note on who will use the app and how often, the features the first version cannot do without, and the names of the tools it has to connect to. If you plan on the stores, set up Apple and Google developer accounts in your company's name. The app is yours, so the accounts should be too.

The code, backend, store accounts and user data belong to you. After release you get access and documentation, and you can grow the app with us or any other team. For 30 days from acceptance we fix bugs caused by our code free of charge. PWA updates reach users immediately, and for the Capacitor version we prepare each new release and submit it to the App Store and Google Play.

Have an idea for an app your customers would use every week? Tell us what it should do and we will reply by the end of the next working day and set up a call about the scope. After the call you get a quote with a list of work and stage dates, and you decide on the budget knowing the figure and the timeline.