Mobile app development for businesses in France

No. SpiderHunts Technologies is a UK-registered company with a registered office in London and a remote engineering team, and we build for French clients remotely. We would rather say that than claim a Paris address we do not have. For a mobile project it matters less than people expect: builds reach your team through TestFlight and Play internal testing, so you hold the app in your hand every sprint, and the code and store accounts stay in your name throughout.

No. Our French app work runs by video call, screen share and shared builds, which is part of why the price sits where it does. Kick-off workshops and milestone reviews are held by video too; we do not travel to meet clients. What we will not do is imply we have a local team that can come to your office at short notice.

France is one hour ahead of London, and we schedule calls in your working hours, across the whole French working day. Our working day runs across your morning and early afternoon: convenient for a stand-up before lunch and for a build to be waiting when you get in. Later French afternoons are picked up the next morning. We fix the meeting slot at the start of the project rather than leaving it to chance.

Yes. We invoice in euros or pounds sterling from our UK company, usually against agreed milestones. Because the supplier is outside the EU, our invoices do not carry French TVA; a French business customer normally accounts for the TVA itself under the reverse charge, using its numéro de TVA intracommunautaire. Apple and Google bill their own developer account fees and any store commission directly to you. Your expert-comptable should confirm the treatment for your situation: we are engineers, not tax advisers.

You choose the region and we deploy there: for French clients usually an EU region such as AWS Paris (eu-west-3), Scaleway, OVHcloud or Azure France Central, so personal data does not leave the EU. We build to support RGPD requirements and CNIL guidance for mobile applications: data minimisation in the SDK layer, a purpose written down for each piece of data collected, retention rules, working export and deletion routes, encryption in transit and at rest, and a record of processing. We sign a data processing agreement and list sub-processors before anything sensitive moves. Compliance itself stays your organisation’s responsibility; your DPO and legal team make the final call and we work alongside them.

Two separate things have to line up. First, consent under French law: a consent management platform inside the app, Didomi and Axeptio are two French options clients often name, asking in French, before any analytics, advertising or attribution SDK initialises, with refusal as easy as acceptance and the answer stored and re-askable. Second, Apple’s App Tracking Transparency: on iOS, an app that tracks a user across other companies’ apps and websites must show the ATT prompt and honour the answer, whatever your own banner says. Android has no ATT equivalent, but the advertising ID can be reset or removed by the user, so your consent platform has to carry the same logic. We also keep a written note of what each SDK collects, because that is what the App Privacy and Data safety declarations are built from.

Yes, and it is the normal arrangement. The interface ships in French, jj/mm/aaaa dates, the decimal comma, euro formatting, the 24-hour clock, accent-aware search, French VoiceOver and TalkBack labels, and a deliberate choice between vous and tu, and a French speaker on your side reviews the wording before release. French runs longer than English, so the layouts are built to absorb it rather than truncate. Adding English or another language later goes through the same translation files. Meetings, written updates and documentation are in English, so your project contact needs to be comfortable in English.

Yes. We prepare and submit under your own Apple Developer and Google Play accounts, so the app is yours from the start. That includes French-language listing copy, keywords and screenshots for the France storefront, age rating questionnaires, the App Privacy answers in App Store Connect and the Data safety form in Play Console, signing and release certificates kept in your account, and a phased or staged rollout so a problem reaches few users. Store review is outside anyone’s control, so we plan the submission with room for a rejection and a resubmission rather than promising a launch date we cannot hold.

For most French businesses launching a product, one Flutter or React Native codebase covers both stores and keeps the two platforms in step for one team’s effort instead of two. Native Swift or Kotlin earns its cost when the app leans on device hardware, needs demanding graphics or real-time processing, or has to adopt a new iOS or Android capability the week it ships. We recommend what fits the product. The detailed comparison, including where each approach falls down, is on our mobile app development page and in our Flutter versus React Native guide.

It depends on scope, so you get a written quote after a free scoping call. As typical ranges from our service page: a cross-platform Flutter app is £15,000–£35,000, a native iOS or Android build £25,000–£60,000, and a marketplace or enterprise app £50,000–£100,000 or more. On timing, an MVP is typically 8–12 weeks and a full-featured app 16–20 weeks, plus store review. We invoice the agreed amount in euros. Apple and Google developer account fees, cloud hosting and third-party licences are separate and paid by you. Our guide on what a mobile app costs to build explains where the money actually goes.

Yes, and the hosting question gets settled first. Personal health data collected in France has to sit with a hosting provider holding Hébergeur de Données de Santé (HDS) status: that status belongs to the host, such as OVHcloud, Scaleway or the major clouds’ qualifying regions, not to us as a developer. We design the app and backend to deploy there, keep the data set to what the clinical purpose needs, and agree access rules and retention with your DPO before collection starts. Whether your use case falls inside the HDS regime, and what else applies, is a decision for your legal and medical teams.

Yes: in-app assistants, document and receipt capture, search and recommendations. We test on French-language material rather than on translated English, because accents, formal register and tokenisation all behave differently, and models can run through Mistral AI, OpenAI, Anthropic or Azure OpenAI in an EU region with limits on what leaves your systems. The AI Act puts most obligations on the provider and the deployer of a system, which usually means you as the business publishing the app: we design for that with documentation, human oversight where a decision affects someone, logging, and a clear notice when a user is talking to an AI. Your counsel decides what the Act requires of you; our EU AI Act guide sets out the shape of it.