↳
- Use aync task for the same - Use some kind of timeout mechanism.
↳
Rxjava with switchMap
↳
Professionally.
↳
-HTML5 for cross-compatibility across platforms. Use Phonegap, jQuery Mobile, Titanium, TideSDK as examples. -HTML5 if future web interface. -Mobile app if you will have features relying on system behaviour (ex, iOS iCloud, Android Play Store, etc.) -Mobile app if users need performance, or if they might be using it offline (but HTML5 offline is still an option) But we are now starting to see a hybrid of these two approaches (ex. http://www.orubase.com/ Orubase). It really depends on the requirements, and the ability of developers (cost estimates) to do this. Less
↳
Like best: - Scalable - Easy to understand for front-end developers because it's still javascript Like least: - Not bundled with other features included in other environment like Rails. You have to download modules, but why can't these be integrated from the beginning? - Lack of cross-compatibility in modern browsers (bad answer, since he was referring to server-side JS) Less
↳
I did paint on the board, a small diagram, and explained it.
↳
I have worked on some e-health app which is an inventory system for drugs
↳
they give u some time between each part for you to organize your ideas, focus on your career story, some time to analyze the code and ask the specific questions. Less