Berlin · companies · iOS and Android
App development in Berlin for companies.
An app is not a website with an icon on the home screen. It has to keep working without a network, feel right on the device, deliver notifications reliably and pass two reviews that decide by their own rules. That is precisely where most first attempts fail.
From first draft to store approval — one contact person throughout.
Location
Scoping belongs around a table
The most expensive mistake with an app happens in the first week: too much in the first version. Which screens exist, what happens on each and what explicitly comes later — that settles around a table in two hours and in a video call across three meetings. In Berlin the table is available.
Techlogia — Jaciel A. Acea RuizPrinzenallee 38
13359 Berlin
How we work together
Scoping and reviews take place on site in Berlin and Brandenburg on request. Delivery in between runs remotely, with fixed milestones installable on your own device — not as a video, but as something to hold.
When an app is worth it
Four cases where an app does more than a website
If a mobile website is enough, we say so. An app pays off where it reaches things a browser cannot get to — or where it has to keep working when there is no network at all.
Working without reception
Measuring in a basement, meter readings in an underground car park, stock-taking in a warehouse. Data sits on the device and is carried over once a connection returns. For conflicting edits there is a defined resolution rather than last-one-wins.
Access to the hardware in the device
Camera for codes and receipts, location for routes, pairing with measuring devices or printers over Bluetooth. This is the area where the browser stops and the app begins.
Notifications that get through
A message that arrives reliably is a working tool — one that sometimes arrives is noise. Delivery, grouping and the question of what happens when someone refuses permission belong settled from the start.
A tool for your own crew
Not every app belongs in a store. For applications only your own team uses there is internal distribution — no public review, and no competitor reading along.
How we work
How an app comes about
- 01
Scoping the first version
Which screens, which flows, what explicitly does not belong in version one. What is left out here is postponed, not cancelled — and that is the difference between finished and endless.
- 02
Draft and usability
A clickable draft before any code exists. Changes cost minutes here and days after the build — this is the cheapest moment to discover that a flow feels wrong.
- 03
Build and integrate
Delivery with a shared codebase where it fits, and native where the subject demands it. Connected to your existing systems through their interfaces, with local storage so the app keeps running without a connection.
- 04
Approval and afterwards
Submission to Apple and Google including their follow-up questions, plus crash reports and a path for updates. Operation starts after approval — store review rules change every year.
What it costs
Fixed prices for the usual scopes
What an app costs depends on its scope — but the common scopes can be priced. The three here are the starting points calculations run from, not the ceiling.
App
Mobile App (PWA)
Progressive Web App — installable on home screen, push notifications, offline-capable. No app store, but instantly updatable.
from €2,490
App
Mobile App (Flutter)
Native iOS + Android from one Dart codebase with Flutter — app store listings included, push notifications, hardware access.
from €5,900
Desktop
Desktop App (Cross-Platform)
One app for Windows, macOS and Linux — built with Tauri (Rust) or Flutter Desktop, lean and native-feeling.
from €4,900
Net, plus VAT. Developer accounts with Apple and Google come on top and are held directly by you — they belong to your company, not to us. A guide figure for your scope comes out of the configurator.
Which technologies are used for what, how offline operation and syncing are built, and what to expect from the store process — the technical depth is on the service page.
See app development →Frequently asked
Questions we get asked a lot
One shared codebase or two native apps?
In most cases a shared base for iOS and Android, because two separate apps mean duplicated maintenance forever. Native is the answer where the subject demands it: direct sensor access, Bluetooth pairing, background audio. The decision is made in the initial call against your requirements, not in advance.
Who gets the app into the stores?
We handle the Apple and Google review process end to end — listing, imagery, privacy declarations and the answers to follow-up questions. Rejections are normal for first releases; experience with them saves weeks, because the second submission lands.
Does the app work without a network?
That is the default, not an extra. Data lives locally on the device, changes are carried over once a connection returns, and there is a defined resolution for conflicting edits. An app that gives up in a lift is not an app.
Do we get the source code?
Yes, in full, in your own repository. No closed components, no hidden dependency on our servers. If you commission someone else later, everything is ready for them.
Do we meet in Berlin?
Gladly. The early shaping in particular — which screens exist, what happens on each, what belongs in the first version — goes faster around a table than in a video call. After that, delivery runs mostly remotely, with fixed milestones to look at.
Get in Touch
Have a project?
Let's bring your idea to life together. We're happy to advise you with no obligation.