Mobile Apps en Montreal
How we work in Montreal
The phone picks the language, and sometimes it picks wrong
An app starts up in the operating system's language. Someone whose phone is set to English but who wants to be served in French needs a switch inside the app, and that preference has to survive logging out and reinstalling. Otherwise every update sends them back to the language they did not choose.
A wrong string lives on people's phones for weeks
On a website a typo is fixed in two minutes. In an app you have to build, submit, wait for review and hope people update, so a badly translated label stays on screen long after you spotted it. That is why the copy, in both languages, is reviewed before the build is made.
The store listing is an asset per language
The App Store and Google Play let you publish a title, description and screenshots for each language, and that is the real shop window. If the screenshots have text baked into them, that is two sets of images to redo at every redesign. It is a cost worth seeing in the budget.
A notification is sent from the server
The push message is not written by the phone: it is sent by your system, which has to know what language each registered device speaks. A mass send in a single language is the most visible failure a bilingual product can have, because it lands on everyone's lock screen at once.
Answering your questions
What people ask us about Mobile Apps in Montreal.
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