Skip to content

Services · Mobile

Your product, in your customers’ pockets.

Phone apps that share the same accounts, data and rules as your web platform — so you aren’t maintaining two separate products.

A connected mobile app is a phone app that runs on the same backend and data as your web platform, instead of living as a separate product.

Details

Bitnoda builds these apps as PWAs (web apps you install on your phone) or as native apps, on top of one shared API.

Who it’s for

  • You already have a web platform, and your customers keep asking for an app.
  • You need push notifications, quick access from the home screen and features that still work on a weak signal.
  • You want to validate an idea on mobile without paying for two separate native apps.
  • Your field team needs an internal tool on their phones, connected to the data back at the office.
  • You want your website, app and admin panel to share the same accounts and the same data.

What you get

  • A phone app or an installable PWA
  • One API shared by the website, the app and the admin panel
  • Accounts, sign-in and data synced across devices
  • Push notifications
  • Offline mode for the core features, where it makes sense
  • App Store and Google Play readiness, if you go native

How we work

  1. Discovery

    We decide what the app needs to do on the phone and what stays on the web, and choose between a PWA and a native app based on features, budget and audience.

  2. API & data

    We design or extend your platform’s API so the website and the app read the same data, under the same rules.

  3. Design & build

    We design screens for thumbs and patchy connections, and build them in short iterations you can test on your own phone.

  4. Launch & updates

    We publish the app, set up notifications and monitoring, then keep it updated alongside the platform.

Technologies

  • PWA
  • Vue 3
  • Nuxt
  • TypeScript
  • Dioxus (Rust)
  • Firebase
  • Supabase
  • FastAPI
  • Node (Fastify, Nitro)
  • PostgreSQL

Related work

Frequently asked questions

PWA or native app — which one do I need?

For many products, a PWA is enough: it installs from your website, can receive push notifications and runs on every phone from a single codebase. A native app makes sense when you need deep access to the phone’s features or a presence in the App Store and Google Play. We recommend one after discovery, not before.

Does the app use the same data as the website?

Yes — that’s the whole idea. The website, the app and the admin panel all talk to the same API, so an account, an order or a booking looks the same everywhere. You maintain one source of truth, not two systems.

Which projects show experience relevant to mobile?

The projects on this page are the platforms and APIs a mobile app builds on: DriverHub runs on Firebase and Supabase, e-voluntar.md has a FastAPI backend, and the confidential HR platform includes a Telegram bot. A phone app reuses exactly this kind of backend, with the accounts and data already in place.

How much does a mobile app cost?

It depends on the approach (PWA or native) and on how much backend already exists: if your platform has an API, a big part of the work is already done. The contact form lets you pick a range, from under €3,000 to over €25,000, and after the first conversation you get an estimate broken down by stage.

How long does it take to build a mobile app?

A PWA built on top of an existing platform can be ready in a few weeks, while a native app with a new backend takes a few months. We set a realistic timeline after discovery, once we know which features go into the first version.

Who looks after the app after launch?

We do, if you want us to. We update the app alongside the platform, keep an eye on errors and prepare new releases. The code belongs to you, so you can hand it to another team at any time, documentation included.

Other services

Tell us what you want to build.

Describe your idea or product in a few lines. We’ll come back with good questions and a concrete plan.

Start a project