Mildly unrelated - does anyone else get frustrated with the ui/ux for HBO now/go? The menu switches from the right side of the screen to the left, the scrolling is wonky, etc.
Man their content is good, but the app sucks.
Crafting a high-performance TV user interface using React
11–20 of 198 posts
Re: Crafting a high-performance TV user interface using React
#12What's with everyone's obsession with React recently? All I see is a template engine and not a particularly good one. You're still left with the same problem mixing your HTML into JavaScript.
The thinking--and I'm not sure I agree with it, but it doesn't seem that objectionable--is that, while the HTML/CSS/JS separation makes a lot of sense for documents, it does not necessarily make as much sense for applications. HTML is just being used as a rendering language, not as a content description language, if that makes sense? And so the split between them might not make as much sense.
As a template engine (which I'm not totally sure is the correct term for it), I will cape up for it (more from a React Native perspective than a React perspective, and with the caveat that I think the JS world is mostly a crime-in-progress). I haven't found something that I've enjoyed working with in the JavaScript world nearly as much as React.
Re: Crafting a high-performance TV user interface using React
#13I assume that HTML Dom would be fastest. Statically generated. And that working w/ DOM/CSS would make it easier for team's designers to be more engaged.
Its quite easy to do server-side rendering of react pages, then only mount the dynamic views once in the browser.
Re: Crafting a high-performance TV user interface using React
#14What's with everyone's obsession with React recently? All I see is a template engine and not a particularly good one. You're still left with the same problem mixing your HTML into JavaScript.
I don't think I could write a comment that's a stronger explanation than what Guillermo Rauch wrote: https://rauchg.com/2015/pure-ui TL;DR: It's not about the HTML in Javascript; it's about being able to declare all the states of your UI in a stateless way. The result is that React components are like pure functions: you pass them inputs and you get predictable outputs.
If it's about state I feel like ExtJS is a better alternative especially with the way it handles Controllers, Events, and "Components" with state.
Re: Crafting a high-performance TV user interface using React
#15What's with everyone's obsession with React recently? All I see is a template engine and not a particularly good one. You're still left with the same problem mixing your HTML into JavaScript.
I found the whole update state and have the UI automatically render on state changes a very useful model. You only need to define the UI once, and have the real time rendering left to the state watcher.
Re: Crafting a high-performance TV user interface using React
#16What's with everyone's obsession with React recently? All I see is a template engine and not a particularly good one. You're still left with the same problem mixing your HTML into JavaScript.
I don't think I could write a comment that's a stronger explanation than what Guillermo Rauch wrote: https://rauchg.com/2015/pure-ui TL;DR: It's not about the HTML in Javascript; it's about being able to declare all the states of your UI in a stateless way. The result is that React components are like pure functions: you pass them inputs and you get predictable outputs.
You can do that with other solutions, its not limited to react. I use polymer but you can use it with vue or others.
Re: Crafting a high-performance TV user interface using React
#17I built my early career entirely around CRO / testing and moved over time into product / ux / app optimization.
Huge, crazy, insane amounts of time are WASTED by humans dickering around with interfaces that they don't understand and that are not personally optimized.
One of the things I don't hear many people talk about, but I am particularly interested in, is the coming and continued improvement of adaptive & personal interface design.
A challenge that any single interface has is that it's difficult to set-up and qualify a test on a small cohort group level (men over 70 years old that wear glasses are homeowners, drink wine, and live in California is an actual target class we can easily devise from current ad tech for instance).
It's challenging because - NOT ENOUGH DATA - eg very hard to run experiments and achieve statistical significance, let alone biforcate your alreadly limited resources to drive to that level of granularity.
But imagine an adaptive UX or set of UX preferences.
EG - Take the same inputs -> eye tracking / natural language feedback (speech!) / interface observation / time to goal / etc Key to not completely confuse and blow users off path will be some kind of throttling mechanism - adaptations that settle you into the UX like your body's settling into the couch cushions.
Re: Crafting a high-performance TV user interface using React
#18What's with everyone's obsession with React recently? All I see is a template engine and not a particularly good one. You're still left with the same problem mixing your HTML into JavaScript.
The thinking--and I'm not sure I agree with it, but it doesn't seem that objectionable--is that, while the HTML/CSS/JS separation makes a lot of sense for documents , it does not necessarily make as much sense for applications . HTML is just being used as a rendering language, not as a content description language, if that makes sense? And so the split between them might not make as much sense. As a template engine (…
So 100% agree. I haven't found something I've enjoyed working with in JavaScript.
The environment I work on usually has very clean MVC and the issue is always that the designers I work with don't know javascript but need control over the HTML so I'm always taking their raw HTML with almost no javascript and basically reworking the HTML & CSS to do the animations or w/e is necessary.
I've tried React but generally I just get very dirty .JS files with mixed HTML/CSS in them. It's honestly not as clean as people make it out to be unless you're working with UI/UX people who know JavaScript already.
Literally every time I have an HTML/CSS person mess with the code I have to fix the JavaScript afterwards.
Re: Crafting a high-performance TV user interface using React
#19Earlier quoted context omitted.
The thinking--and I'm not sure I agree with it, but it doesn't seem that objectionable--is that, while the HTML/CSS/JS separation makes a lot of sense for documents , it does not necessarily make as much sense for applications . HTML is just being used as a rendering language, not as a content description language, if that makes sense? And so the split between them might not make as much sense. As a template engine (…
So 100% agree. I haven't found something I've enjoyed working with in JavaScript. The environment I work on usually has very clean MVC and the issue is always that the designers I work with don't know javascript but need control over the HTML so I'm always taking their raw HTML with almost no javascript and basically reworking the HTML & CSS to do the animations or w/e is necessary. I've tried React but generally I j…
I think the implications of UI/UX people who don't know JavaScript is probably not great to begin with, yeah? I'm not sure that React isn't just exposing a flawed assumption that maybe we shouldn't have had in the first place.
Re: Crafting a high-performance TV user interface using React
#20I built my early career entirely around CRO / testing and moved over time into product / ux / app optimization. Huge, crazy, insane amounts of time are WASTED by humans dickering around with interfaces that they don't understand and that are not personally optimized. One of the things I don't hear many people talk about, but I am particularly interested in, is the coming and continued improvement of adaptive & person…
I disagree there, thinking back to the days of when Office 'customized' it's UI to how you used the product (constantly moving menu items, shudder!), I'd rather have a consistent UX that didn't exactly fit my patterns than an adaptive one.
The problem with many interfaces, especially on consumer products, is that they're not discoverable, and oftentimes hide things behind inane levels of menu. Interface isn't a competitive advantage (although it should be!) so manufacturers don't invest in it.