When you used a built-in interactive HTML UI component (e.g. textarea, select, checkbox) in the browser was it because? A) Accessibility?
B) A better polished/integrated user experience than any JS library provides. C) Meh I just needed to throw something together.
-
-
The quality of primitives on the web is poor. E.g. contextual menus, stack navigation, buttons, video controls, infinite scrolling lists with context, date pickers etc. This was known before the mobile era. Many reimplementations of <select /> and jQuery UI solved a real problem.
-
Comparing to native is important to avoid getting stuck in a local maxima. When developing on for mobile, we see that native code execution isn't important. It is access to well designed UI primitives that do the heavy lifting of managing animations, touch, accessibility etc.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.