Mobile Apps en San Francisco
How we work in San Francisco
The phone arrives with a variety already decided
The system hands over a language identifier with its region: English for the United States, for the United Kingdom, for Australia. Your app can follow it or impose its own, but on purpose. By default many libraries take whatever the device says and your decision evaporates on first launch.
The keyboard corrects toward the device's variety
What your users type arrives already adjusted by their phone's autocorrect, which has not read your guide. If there is a search box inside the app, it has to find both spellings or somebody will get “no results” over content they wrote themselves.
The stores allow separate English listings
You can publish one listing per variety of English, with its own title, description and screenshots. It is a real option and a real duplication: every version has to be maintained and reviewed on each submission. It pays off when the text really changes, not when four letters do.
Screenshots carry text and nobody reviews them
An image of the app with the word spelled the other way gets flagged by no spell checker and no code review. It turns up when somebody looks at the listing carefully, months later. That is why we generate them from the app itself with the language forced.
Answering your questions
What people ask us about Mobile Apps in San Francisco.
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