I today released an Android application which includes some language-dependent MP3 files. My concern is that the more languages, the bigger the application size.
What would be your recommendation:
- Release one application per language (not really easy to deal with, would have to release n apps each time I add new features to the software)
- Provide a mechanism to download the MP3 files at first launch (would require an internet connection whereas the user may think he doesn’t need one. It could bring frustration.)
- Optimize the MP3 files (not that scalable if I have to support 10 languages)
- [ ] fill the blank !
Hervé.
I’m a big fan of user-choice. As such, I might make the MP3 files optional, but on first run explain to the user that you have some language-dependant features and allow them to download them if they desire.
The reasons for this are many:
It keeps the file size low.
It is easily supportable with one distribution.
It allows you to extend/correct the language files independent of the software.
It is upfront, and gives the user the choice of language (even potentially multiple).
It allows the user to change the aural language without having to uninstall/reinstall or have duplicate installs.
There are many users (such as myself) who never speak to their phone, and never want to hear it speak to them. 🙂 (Yes, I’m crazy)
Just a suggestion!
FuzzicalLogic