I want to write an application that will transfer MP3 files from the server to any of the three main smartphone operating systems in the USA (iPhone, Blackberry and Android).
Here's the tradeoff I'm interested in: if I write the application initially, it will make a better user experience and give me the opportunity to add many more functions if I want, but I will have 3 separate code files, which violates the DRY principle.
If I use one of the frameworks there to write it in Javascript / HTML (for example, Rhomobile Rhodes ), then I have one code base for all major platforms, so I do not violate DRY, and the development process in this regard is simpler, but ) will experience user experience, and b) I did some simple tests using SoundManager to play MP3 files from Javascript on iPhone, and it immediately started sucking (for example, the second phase of the experiment after “cool, I can play MP3” was “ I have no access to ID3 tags? That sucks. ").
I am wondering if anyone who has proven himself in developing for several mobile platforms can confirm or cancel my impression: cross-platform development with Javascript and HTML is viable (especially for a multimedia application)? Or is it “developing and supporting three separate native codebases” to go here?
Thanks in advance.
Edit: This question suggests that I should do this as an application. I understand that it might be much better to simply submit mp3 files and allow iPhone / Android / Blackberry Media Player users, but for my purposes these solutions are beyond the scope of this question.
source
share