4 ms·
well i would argue not everybody has a top of the line handset , and trust me html5 vs native makes a huge difference on cheap devices. You dont have to use al
by camus 14y ago
well i would argue not everybody has a top of the line handset , and trust me html5 vs native makes a huge difference on cheap devices.
You dont have to use all these tricks when you use IOS or Android widgets.
And usually developping with Xcode or Eclipse IDEs makes the work far more easier than using any JS ide.
Instead of using Javascript for the UI i usually use it to implement bits of business logic , algorithms i can easily port from plateform to plateform , so i get native UI and portable JS libraries.
- emehrkay 14y ago> You dont have to use all these tricks when you use IOS or Android widgets. I havent gotten too deep in native development on either platform, but don't they prioritize tasks automatically? JS doesn't, using requestAnimationFrame and web workers is doing exactly that. Wasn't the main knock against Android's UI lag because everything happens once allowing blocking and it was addressed with project Butter?
- mwcampbell 14y agoHave you successfully developed any iOS apps using the approach you describe (native UI, JS back-end)? If so, how did you embed a JS engine in your app and bridge between that and ObjC?