Question 1

How long does it take to build an application?

Accepted Answer

Entirely dependent on scope. A progressive web app built around one clear purpose ships in a few weeks; a full business application released on the stores takes several months. We always split the work into deliverable versions, so you have something usable well before the final release.

Question 2

How does a project run at Glaider?

Accepted Answer

A first conversation establishes the need and whether we are the right people for it. A scoping phase follows, producing a costed proposal and a written scope. Development then proceeds in short iterations with regular check-ins, and the production launch comes with a hands-on onboarding period. We stay available afterwards for maintenance and further work.

Question 3

Do you work with clients outside the Pyrénées-Orientales?

Accepted Answer

Yes. Development and managed services are handled entirely remotely. Being local changes one thing in particular: for clients around Perpignan we can come to you, which matters during scoping or when physical infrastructure is involved.

Question 4

What budget should we expect?

Accepted Answer

We do not publish a price list, because a figure stripped of context misleads more than it informs. We do give an order of magnitude in the very first conversation, before you commit to anything: if the budget and the need do not match, it is better to know straight away.

Question 5

Is the first conversation chargeable?

Accepted Answer

No. The initial discussion and the estimate that follows are not billed. Only an in-depth scoping study, where a project requires one, is quoted separately.

Question 6

Who owns the code you write?

Accepted Answer

You do. The source code produced for your project is delivered to you and the rights are yours. We avoid proprietary components that would stop you bringing in another supplier later.

Question 7

Where is the data hosted?

Accepted Answer

On infrastructure located in France, either at OVH or on servers we administer. For workloads involving artificial intelligence, there are two cases. Either the model belongs to a provider, and the data you submit to it is passed on. Or we deploy it on your own infrastructure, and nothing leaves. We tell you which of the two applies to your project before starting.

Question 8

Can you take over an application someone else built?

Accepted Answer

Often, yes. We start with an audit of the existing code and infrastructure, after which we tell you honestly whether taking it on is sensible or whether rebuilding will cost less in the long run. Sometimes the second answer is the right one.

Question 9

Do we need to go through the App Store and Google Play?

Accepted Answer

Not always. A progressive web app installs straight from the browser, reaches the phone's peripherals and updates instantly, with no store review. Going through the stores makes sense when visibility, native push notifications or particular hardware features require it. We advise based on how the app will actually be used.

Question 10

What happens after delivery?

Accepted Answer

Nothing stops at launch. We offer ongoing support: fixes, security updates, monitoring and further development. You remain free to handle it yourself or hand it to someone else, since the code and documentation are yours.

Question 11

Are your backups actually tested?

Accepted Answer

Yes, and we are insistent about it. A backup that has never been restored is not a backup, it is an assumption. We run periodic restore tests on the infrastructure we manage.

Question 12

What if we decide to leave?

Accepted Answer

You take your data in open formats, the source code and the operating documentation. We support the handover to whichever supplier you choose. Reversibility is not something negotiated at the end of a contract; it is designed in from the start.

Frequently asked questions

How a project runs

Budget and commitment

Technical questions

After delivery

Your question is not here?