Mobile Apps en Paris
How we work in Paris
Searching «Perez» has to find Pérez
A search box that tells é and e apart forces the user to get the accent right to find something they already know is there. And a list sorted without accounting for accents pushes every accented surname to the bottom. It is solved with the right locale settings, and it is caught by testing with real French names rather than dummy data.
Validation that rejects correct data
A surname with an apostrophe, a commune with hyphens, a postcode starting with zero, a phone number written in pairs. All of that is correct in France and all of it is rejected by validation written with Spain in mind. The user does not write in to warn you: they close the app. That is why we test with French data before publishing.
Units arrive with the language they came from
If the product grew out of an English-language base, it drags miles, pounds and the twelve-hour clock along with it. In France distances are in kilometres and the time is written on a twenty-four-hour clock. It is five minutes of work if it is decided at the start, and a screen-by-screen review if it turns up later.
Translating without seeing the screen produces strange errors
A spreadsheet of loose strings does not say whether a word is a button, a heading or part of a sentence, and that is where you get translations that are grammatically fine and mean nothing where they sit. We hand the text over with a screenshot and its context, and it is reviewed with the app installed on a phone.
Answering your questions
What people ask us about Mobile Apps in Paris.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Mobile Apps: stack, process, use cases and FAQs