Link to home
Start Free TrialLog in
Avatar of Federico Nardone Aggiutorio
Federico Nardone Aggiutorio

asked on

iOS, best practice for multi-device multi-language app schema

Dear Expert,
I have an idea about my multi language (with localized text) and multi device (iPhone and iPad) Swift app. I would ask you if it were good.

1) Multilanguage. By classic way, I would localize a specific text file and each storyboard file of the app (the text of each storyboard in an additional file). But I think, is better to have all text in a unique file pro language, and not more file for generic text, storyboard 1, storyboard 2, ecc. Due to this reason, I prefer summarize all text in a unique file (pro language), and assign the label / field text in each storyboard programmatically by Swift code.

2) Multidevice. By classic way, I know, there exist "auto layout", and some other features in x-Code to adapt the layout to different devices. But in particular cases is not good (i.e., I have 4 button in a row, and with iPhone is good see 2 button in 2 rows, in iPad is better to see 4 button in 1 row). Due to this reason, I have created 2 storyboard's folder, and I have set 2 different starting-point from setting panel, depends from the device. And, if I have to change view programmatically, I have created a class which check the device and go to the desired view for the current device (by searching this view in the correct folder, iphone-layout-folder or ipad-layout-folder).

Is my schema correct? What do you think about my idea? Thank in advance!
ASKER CERTIFIED SOLUTION
Avatar of Hamidreza Vakilian
Hamidreza Vakilian

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Federico Nardone Aggiutorio
Federico Nardone Aggiutorio

ASKER

Thank you, your answer solve perfectly my problem.

1. After your answer I'm sure, I'm in the correct way.
2. Size-class are exactly what I need.
Thank you, your answer solve perfectly my problem.

1. After your answer I'm sure, I'm in the correct way.
2. Size-class are exactly what I need.