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.
-
Show this thread
-
This is the biggest differentiator between something like the Web and React Native. The focused investment in polished native UI components by far that of web browser and JS libraries combined. The web has only optimized scrolling finite content (unless you use scrollbars).
4 replies 2 retweets 13 likesShow this thread -
Replying to @sebmarkbage
I'm not buying this argument. Can you unpack it more, especially as it relates to people who are developing content for the web?
1 reply 0 retweets 1 like -
Replying to @wycats
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.
4 replies 2 retweets 15 likes -
Replying to @sebmarkbage @wycats
Wait, you're claiming is that no one would use argument B? Native control quality encompasses accessibility too and is a (the) primary reason I use native controls. It also is important to match platform conventions for text editing, etc.
4 replies 0 retweets 4 likes
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.