home / how we build

How we build apps

Solid technology, in plain words.

You don't need to become technical: you need to know what your investment rests on and why we choose it. Here are the three tools we use every day — and when we use which.

F

Flutter

The app your users touch

There was a time when making an app meant building it twice: one for iPhone and one for Android, with doubled costs and timelines. With Flutter we build a single app that runs identically on both phones, with the look and fluidity users expect.

  • One app for iPhone and Android
  • Polished look, smooth animations
  • Fast updates for everyone at once
  • Used by major services worldwide
In practice: one investment, one app to maintain, no customer left behind.
P

PHP

The engine behind the scenes

Every app has a «behind the scenes»: the place where data, users, orders and permissions live. For that we use PHP — the technology that has run most of the web for over twenty years, from small sites to banking services.

  • Mature, proven and secure foundation
  • Talks easily to ERPs, CMSs and online stores
  • Easy to find developers for, even in the future
  • Suited to business rules and complex integrations
In practice: your data on well-known foundations, connected to the systems you already use.
N

Node.js

The part that can't wait

When information must arrive in an instant — a notification, a chat message, the position of a delivery on a map — you need an engine built for real time. That engine is Node.

  • Instant chat and messaging
  • Targeted push notifications
  • Live status: deliveries, sensors, shared screens
  • One language on the server too
In practice: when «now» has to mean right now, Node takes care of it.

How we choose

Never technology for fashion's sake: we start from the need.

It's not a technology quiz — it's a question of needs. A few examples of how we reason.

A

Orders, customers, ERP

When the app must manage data, permissions and connections to your systems, the heart is in PHP: robust, integrable, predictable.

B

Chat, deliveries, alerts

When information must move instantly between phone and server, the real-time part is in Node.

C

Often, both

In most projects PHP and Node live side by side: one for data stability, the other for speed. You simply see an app that works.

Frequently asked questions

What almost everyone asks.

Do I need two apps, one for iPhone and one for Android?+
No. With Flutter we develop a single app that works on both platforms. It looks the same on every phone, and every improvement reaches all users together.
Where do my data and my customers' data end up?+
On servers we choose together, as a rule within the European Union, in compliance with the GDPR. The data stays yours: the code and configurations belong to you, and we document everything.
Who publishes the app on the stores?+
We take care of it: developer accounts, Apple and Google reviews, texts, artwork and publication. The account stays in your name, so you always own the app.
What if I want to change something after launch?+
It's normal — actually desirable: the best apps grow with their users. Updates are published like the app itself and reach phones automatically. With the support agreed during the project, you choose the pace.
How much does an app cost?+
It depends on what it has to do: a prototype for a simple idea doesn't cost like the app of a company with a warehouse and an ERP. That's why we always start with a conversation and a prototype: first we understand, then we quote precisely — no surprises.

A technology doubt? Ask in plain English.

We answer without jargon and without any purchase obligation: if an app isn't the right answer for you, we'll say so.

Ask your question