Mobile Apps en Miami
How we work in Miami
The field decides which keyboard appears
A postal code field with a full alphabetic keyboard forces a layer switch to type five digits. A phone field with a text keyboard, the same. Declaring the input type is one line per field and saves a gesture for every person who gets that far.
System autofill has to be asked for
iOS and Android know how to fill in a saved address, but only if each field declares what it is. Without that declaration the keyboard offers nothing and the person types seven fields by hand. It is among the cheapest things that move the share of completed forms.
The device's country is not the address's country
A phone set to English may be ordering delivery to a street in Barcelona, and one set to Spanish to a street in Florida. The device language and region are good for proposing a starting value, never for locking one in with no way to change it in a tap.
Fifty entries are not scrolled with a thumb
Picking a state from a long list is one of the worst interactions on mobile. A field with search on the first letters, accepting either the full name or the two-letter code, does the same job without making anyone drag half a screen.
Answering your questions
What people ask us about Mobile Apps in Miami.
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