We’ve gathered all of the questions that were submitted through Slido and answers here in this post. The answers here are summariezed by AI and then reviewed by our teams, with some additional notes added by our engineers when they had something additional to share.
Q1. From the presentation it sounded like the the 2.0 SDK is beta only. How do we get access now?
Answer:
Access starts October 29. More beta details are on the Roku Developer Blog post published during the keynote. Note the wording: the panelist said it will be “generally available” on Oct 29, but Kevin Phillips had just described Oct 29 as a beta, with publishing targeted for about September 2027. The intended meaning is probably “available to everyone as a beta”. There was no answer on getting access before Oct 29.
Where: Day 1, 11:49 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q2. Will all Roku devices on the market support RSG 2.0 when released?
Answer:
Not read aloud, but answered as part of Q061: RSG 2.0 is supported on all platforms, including the low-end Liberty and Littlefield. Q&A #1 (11:00 AM, Q014) also said it runs on Liberty/Littlefield, but without GPUs they cannot hit 60 fps. No one said which minimum OS version is required.
Where: Day 1, 11:57 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q3. Do the new AI skills and MCP support both TypeScript and BrightScript?
Answer:
The skills are TypeScript-centric. The tools they use also work with BrightScript, and there is a skill for the BrightScript DAP debug connection. The skills cover what matters for TypeScript, such as importing XML components, but they do not cover best practices for writing traditional BrightScript.
Where: Day 1, 11:02 AM, RSG 2.0 SDK Q&A #1 (responder: panelist (likely John Roberts))
Q4. Is there a plan to completely deprecate Brightscript at some point in the future?
Answer:
There are no dates for deprecating BrightScript, and Roku will keep supporting it “for now”. Most of Roku’s resources will go to TypeScript, which is where Roku wants everyone to migrate for better performance and app support. On Day 2 (11:32 AM, Community Tools Q&A), panelists said there are no plans to stop supporting BrighterScript.
Where: Day 1, 11:50 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q5. “We strongly recommend developing your app exclusively in TypeScript. Our Hermes JavaScript engine also executes plain JavaScript, but we may enforce TypeScript as a requirement down the line.” Do you mean, in general use ts over BS moving forward and not to use js, even though it’s supported?
Answer:
Roku strongly suggests TypeScript. Hermes runs plain JavaScript today, and nothing currently enforces TypeScript. Static Hermes is on the Hermes roadmap and requires TypeScript for its optimizations. There is no date for it, but TypeScript code could benefit if Roku adopts it.
Where: Day 1, 10:58 AM, RSG 2.0 SDK Q&A #1
Q6. Does typescript work with component librarie?
Answer:
Yes, if the component libraries are compatible with SceneGraph.
Where: Day 1, 11:51 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q7. How many tokens did it take to produce this deck? 
Answer:
No number was given. John did not know. The deck was built over several weeks and many sessions, and the answer was “Lots”. In the talk (10:52 AM) he said the deck app ended up with about 1,300 unit tests.
Where: Day 1, 10:56 AM, RSG 2.0 SDK Q&A #1 (responder: John Roberts)
Q8. What LLM model have Roku found performed the best? Any plans to create your own set of benchmarks/Eval to help the developer community know how well each model performs for developing Roku apps?
Answer:
The team mostly uses Claude. Much of the deck was built with Opus (a mix of 4.8 and 5), with some subagents on Sonnet, and some team members use other models. There are no plans to benchmark LLMs for Roku code development, though he called it an interesting idea. Evals do run against the skills.
Where: Day 1, 10:59 AM, RSG 2.0 SDK Q&A #1 (responder: John Roberts (inferred, he built the deck))
Q9. How does RSG 2.0 performs on Roku LittleField and Liberty?
Answer:
Better than BrightScript. Liberty and Littlefield have no GPU, so they cannot reach 60 fps, but RSG 2.0 runs “pretty well”, comparable to a C++ implementation. On Littlefield, FlexGrid is no worse than RowList. On Day 2 (2:07 PM), Tim Lee (Disney) said the Littlefield round trip was 2 to 4 times longer, roughly in line with everything else. He also said Perfetto would not attach on Littlefield. Roku replied that the SDK launcher process the profiler needs is not yet enabled on Littlefield and took an action on it.
Where: Day 1, 11:00 AM, RSG 2.0 SDK Q&A #1
Follow-up promised on stage.
Q10. Do we have an equivalent of Draw2D API available in TypeScript side?
Answer:
Not currently. Roku “may” add it, but not now. In the BrightScript Q&A (1:34 PM), a panelist added that no Draw2D plans for TypeScript have been discussed. Draw2D is not being deprecated in BrightScript, but it is not an area of investment.
Where: Day 1, 11:05 AM, RSG 2.0 SDK Q&A #1
Q11. How will debugging work with TypeScript? Will that use a different port than 8085?
Answer:
Yes, it uses a different port, “9999, I think” (the panelist was not certain). The BrightScript and TypeScript debug connections are independent. The community VS Code plugin connects to both, so a breakpoint in one runtime stops that runtime while the other keeps running, and VS Code shows them as two threads. The talk (10:48 AM) said TypeScript debugging uses CDP (Chrome DevTools Protocol) from Hermes. On Day 2 (11:11 AM) the community tools talk said the extension reuses VS Code’s built-in JS debug.
Where: Day 1, 11:04 AM, RSG 2.0 SDK Q&A #1
Q12. How does importing an external library into a Roku app developed with TypeScript work? Is it possible to develop a TypeScript module separately and integrate it?
Answer:
Yes. The SDK itself ships through npm as separate modules, and you can import third-party modules with no restriction. XML and PNG imports exist partly so that modules can ship those assets, and the tooling moves them into the package automatically. On Day 2 (2:11 PM and 2:25 PM), partners added that many JS libraries have browser or Node dependencies that must be swapped out, because Hermes runs plain vanilla JavaScript.
Where: Day 1, 11:04 AM, RSG 2.0 SDK Q&A #1
Q13. should we study solid or solid 2.0?
Answer:
The SDK is on Solid 1.9 (“if I remember correctly”) and has not moved to Solid 2.0. There is no concrete plan yet, but they will test 2.0 and update for its breaking changes, hopefully seamlessly. The intent is not to get stuck on an older version.
Where: Day 1, 11:06 AM, RSG 2.0 SDK Q&A #1 (responder: Chakri Kodali, then John Roberts)
Q14. Is it safe to assume the majority of new components like flexigrid will be developed for TS only?
Answer:
New components will be TypeScript, but BrightScript apps can still use them through an anchor node. FlexGrid runs only in the Hermes engine and can only be driven from TypeScript code. Hybrid apps can mix BrightScript parts with a FlexGrid in TypeScript.
Where: Day 1, 11:51 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q15. Will more devices like (Littlefield & Liberty) be deprecated to support newer TypeScript features?
Answer:
No. Liberty TVs are still very popular, so Liberty is a low-end platform that is hard to deprecate and stays supported. RSG 2.0 is supported on all those platforms.
Where: Day 1, 11:57 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q16. Are TypeScript threads supported?
Answer:
No. You cannot create new threads from TypeScript today. Threads are planned, and the interface will be similar to Web Workers. In the BrightScript Q&A (1:45 PM) a similar question was answered by pointing back to this one. On Day 2 (1:49 PM), Fubo noted there is currently no task-node equivalent in TypeScript, so heavy work competes for the single thread.
Where: Day 1, 10:57 AM, RSG 2.0 SDK Q&A #1 (responder: Chakri Kodali)
Q17. Will 9 patch images remain as png even with convert to webp turned on?
Answer:
Yes, they stay PNG. With convert-to-WebP turned on, the build leaves 9-patch images as-is because the renderer does not support 9-patch WebP. They render fine. In Q&A #1 (11:01 AM) the panel was unsure and promised to follow up, and it did here. Q&A #1 also said the TypeScript SDK supports 9-patch images, but the tooling’s automatic HD-from-FHD synthesis does not apply to them.
Where: Day 1, 11:52 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Follow-up promised on stage.
Q18. When will we get more shapes other than Rectangle?
Answer:
The panel only pointed to rounded corners from the effects node, which is also available in BrightScript. No new shape primitives or dates were given. In the BrightScript Q&A (1:37 PM), panelists said a corner radius of half the size gives circles and pills, but ellipses/ovals are not possible today (“we will get back to you”).
Where: Day 1, 10:59 AM, RSG 2.0 SDK Q&A #1
Q19. Is performance across the device lineup equal?
Answer:
Performance improved across the board, Littlefield included. Hermes runs TypeScript fast compared to BrightScript, and Roku has benchmarks, though none were shared. Splitting the program and render threads gives an extra boost on multi-core devices, which is everything except the MIPS devices. Frame measurements on grids show it feels snappier everywhere.
Where: Day 1, 11:03 AM, RSG 2.0 SDK Q&A #1
Q20. and about corner radius from images? any news?
Answer:
Effects work on images. The panelist believed you can round a poster’s corners with the effects node, but you have to set a property on the poster whose name he did not remember. He pointed to the SceneGraph/BrightScript session. That session (1:13:58 PM) named the property: shaderCompatible = true on the poster. It also said effects apply only to rectangles and posters, and do nothing on Liberty/Littlefield.
Where: Day 1, 11:05 AM, RSG 2.0 SDK Q&A #1
Q21. Is TypeScript the chosen future of Roku development from now on? Do you suggest starting to switch to it?
Answer:
Yes, though timing depends on your situation. Roku wants everyone to start exploring TypeScript, but you cannot publish TypeScript apps during the beta period.
Where: Day 1, 11:51 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q22. How are crash analytics being reported? Will they be available with the new crash log API?
Answer:
Roku is working on it, and it is one of the things it wants in place before developers can publish TypeScript apps. There was no detail on how it will be reported or whether it goes through the Crash Logs API. The Dev Portal keynote (9:36 AM) said the Crash Logs API launches externally in Q4. On Day 2 (1:10 PM), Crunchyroll noted that TypeScript component crashes currently have no stack traces.
Where: Day 1, 11:56 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q23. Will we be able to measure jank, jitter, and dropped frames in retail applications to measure performance in the wild?
Answer:
Today it only works on your own device:
Where: Day 1, 11:53 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q24. Does the FlexGrid support custom BrightScript tile components? i.e., in a migration scenario, can we migrate to FlexGrid without needing to migrate all of our tile implementations at the same time?
Answer:
Yes. A BrightScript tile is just another component. You import its XML in your TSX code and FlexGrid can reuse it.
Where: Day 1, 11:55 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q25. I noticed in the demo the rounded corner image also showed gradient colors, will gradients be natively supported ?
Answer:
Yes. The panel pointed to Luke Diamand’s 1 PM session. That session (1:12 PM) showed Effect node gradients: linear or radial, with multiple stops, in the body or the border, with animatable angle and colors. They apply to rectangles and posters and do nothing on Liberty/Littlefield.
Where: Day 1, 11:52 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q26. You mentioned effects node can replace 9 patches for focus rings. Is it more performant to use effects node?
Answer:
The panel said “Yes” and pointed to the 1 PM session. That afternoon’s BrightScript Q&A (1:27 PM) was more cautious. Nobody had benchmarked it. The effect is probably faster on GPU devices, but maybe not on RCE, where the GPU is software. Effects do nothing on Liberty/Littlefield, so 9-patch is still needed there for the same look. The 1 PM talk (1:15 PM) also said each unique effect costs a shader compile of tens of ms on the render thread, while identical effects share one program.
Where: Day 1, 11:56 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q27. How does a TypeScript app size compare with the equivalent BrightScript only app?
Answer:
The evidence is anecdotal because there have been few like-for-like comparisons. Where they have ported something, the compiled result, including the XML components, came out about the same as the Hermes bytecode bundle. Nothing was vastly bigger or smaller. The SDK is kept slim so it does not bloat bundles, but no formal analysis has been done. In the talk (10:43 AM), the build tree-shakes unused TSX along with any XML components it imports.
Where: Day 1, 11:09 AM, RSG 2.0 SDK Q&A #1 (responder: panelist (likely John Roberts))
Q28. Does the TypeScript SDK support, or could it support, hot reloading so that changes are reflected on-device immediately when a developer saves a TypeScript file?
Answer:
Not true hot reload. The rk dev watch command rebuilds and pushes the full package on save. Hot reloading without a full repackage is not supported, but Roku wants to add it and it is on the roadmap. On Day 2 (2:13 PM), a partner said they had asked Roku for hot reload and for bundle chunking.
Where: Day 1, 11:53 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q29. Can we use Roku’s official cloud emulator as the target runtime for an AI Agent using MCP to automatically write, push, and test a channel without human intervention
Answer:
Yes, we will have RCE support in beta and you will be able to do exactly this
Where: Day 1, 11:55 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q30. any plans for news built-in components in sg2.0?
Answer:
Yes, we have a number on the roadmap. In general to help with performance, provide new graphical capabilities or support the new SDK’s TypeScript model.
Q31. Do you recommend to prioritize ts instead of brs?
Answer:
Covered by the Q040 answer, given about a minute before this was submitted. Yes, start exploring TypeScript, depending on your timing. You cannot publish TypeScript apps during the beta.
Where: Day 1, 11:51 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q32. What happens if multiple transactions are queued onto the render thread?
Answer:
Queued transactions are all picked up at the start of the next render tick and applied in one go.
Where: Day 1, 11:07 AM, RSG 2.0 SDK Q&A #1 (responder: panelist (likely Chakri Kodali))
Q33. Is logger allowing sending up remote logs or what is the benefit in production? Or perhaps ability to see logs in production app?
Answer:
The framework includes a Logger object that manages log levels and has more features. Roku wants developers to use it instead of console.log, because the build strips console.log out. The framework itself uses Logger in transaction management and its APIs for control over formatting and stripping. If you as a developer want to emit logs in production to your own endpoints, you can simply implement that yourself. Roku does not intend a generalized way to do that for partners
Where: Day 1, 11:08 AM, RSG 2.0 SDK Q&A #1
Q34. when will the sdk be available
Answer:
October 29, as a beta open to everyone. During the beta it is sideload only. Checks will stop you from publishing an app that contains TypeScript, and the target for publishing is “September next year”. The SDK will be at rokudev · GitLab, and Roku’s existing GitHub repos are moving to GitLab. Roku wants a lot of feedback during the beta. In the keynote (9:47:48 AM), Pinkerton said the SDK will be open sourced under the MIT license, with beta starting in a month and “general availability in a year”. This question was archived at 10:56 AM and held for this segment.
Where: Day 1, 11:48 AM, FlexGrid talk (responder: Kevin Phillips)
Q35. Does the fetch implementation pass the relevant subset of the Web Platform Tests conformance suite? does it support HTTP/2 or HTTP/3?
Answer:
It does not pass but we are looking into the implications of that. At the very least we will document where it does and doesn’t comply
Where: Day 1, 11:59 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q36. If “rk” is necessary for building TypeScript, it would be interesting to understand what’s the best way to have it interop with existing solutions such as the BrighterScript compiler
Answer:
Roku does not use BrighterScript itself, but rk is a CLI, so it can be added to any build. rk has a pipeline API for extending it with extra build steps or transpilers. It is built on esbuild, and you can write your own plugins or plug in other transpilers. The panel pointed to Day 2 partner stories. There (1:08 PM and 1:12 PM), Crunchyroll transpiles BrighterScript, compiles TypeScript, then merges outputs and manifests. Crunchyroll had to suppress BrighterScript’s XML/BRS pairing check. Peacock runs the rk CLI at the end of its pipeline.
Where: Day 1, 11:58 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q37. How fast does FlexGrid run on the slowest device?
Answer:
Not read aloud. While answering Q014, a panelist said FlexGrid on Littlefield is no worse than RowList. No fps figure was given for low-end devices. The FlexGrid talk demos showed 60 fps, but the device was not named.
Where: Day 1, 11:00 AM, RSG 2.0 SDK Q&A #1
Q38. How expensive is toll from ts land to sg? Can I create nodes on the fly in ts? Is it expensive to set fields on nodes? More expensive than just doing it in brs?use case: Can I create nodes 100 nodes in typescript and manipulate them? And if so Would that be slow?
Answer:
SceneGraph itself is the limit. Creating 100 nodes from TypeScript through a transaction costs the same as creating them on the render thread. The talk (10:28 AM) gave data-transfer costs measured on a Roku Ultra: about 4 ms to move a 10 KB object in either direction, and about 1 to 2 ms for primitives. The advice was to move primitives and only the data you need.
Additional note provided by one of our engineers:
There is an async boundary between TS and SG and a transaction mechanism for batching tree manipulation functions into one atomic application. I don’t see that as a toll or being more expensive, it is just how it is programmed. Underneath, the cost of SG node creation and update remains the same, it is just orchestrated differently.
Where: Day 1, 11:56 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q39. What version of SolidJS? Is the custom renderer built with JS APIs that can be used for bringing other frameworks (eg React Native Web) for better code sharing with cross-platform apps?
Answer:
The renderer sits on a low-level Tree Management API that works “like a DOM”. In theory other frameworks could be built on it, but Roku does not support that and the API may change. The version part was answered in Q&A #1 (11:06 AM, Q028): Solid 1.9. On Day 2 (2:11 PM), a partner question about React on the Tree API got the reply that Fubo is not looking at React.
Additional note provided by one of our engineers:
We evaluated React Native and rejected it. React itself is slower and more bloated than SolidJS and we wanted something lean and fast which is a much better match for Roku device profiles. The React Native renderer is also not a good fit, for similar reasons.
Where: Day 1, 11:58 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q40. any plans to be able to write apps with i18n support? currently cannot do so with non roman script language sets
Answer:
The same topic was answered in the BrightScript/SceneGraph Q&A, where the panelist said they had seen it on Slido. There are no updates. Device fonts limit support, and anything new would be announced if Roku enters those markets. You can bundle your own fonts. The hard cases are right-to-left and scripts that need a different text rendering system. Text shaping (ligatures) was added a few years ago.
Where: Day 1, 1:50 PM, BrightScript / SceneGraph Q&A
Q41. Thank you for all your hard work Roku Team! Can you tell us what is next on the SDK roadmap?
Answer:
We can’t make forward facing roadmap comments, but we are committed to providing official announcements for beta programs and new features via our Roku Developers Blog and the Roku Developer Forum.
Q42. Is it possible to build a Roku app without using BrightScript and XML?
Answer:
The keynote said you can either fold TypeScript into an existing BrightScript app piecemeal or “build a new TypeScript app from the ground up”. On Day 2 (1:42 PM), Fubo described a prototype written entirely in TypeScript “with the exception of a few small BrightScript SceneGraph components” (shims for animation).
Additional note:
There is a little bit of boilerplate BRS needed (Main.brs) and one XML component. Future version of RSG will remove this.
Where: Day 1, 9:47 AM, Keynote: Tools, RCE + RSG 2.0 SDK announcements (responder: Brian Pinkerton)
Q43. is the rk CLI open source? can we “eject” or modify the underlying bundler so we can integrate RSG 2.0 as a first-class citizen in our React/SolidJS monorepo that deploys to several platforms?
Answer:
The Q048 answer covers extensibility: rk has a pipeline API, is built on esbuild, and accepts custom plugins and other transpilers. The keynote (9:47 AM) said “this SDK” will be open sourced under MIT. No one said whether rk specifically is open source or can be ejected.
Note from one of our engineers:
You could eject it and replace it with your own, but I’d express some caution. Sure, the build part may be common, but there are Roku specific parts such as the bundling, package building and hermes bytecode generation that are tailored to Roku. If you replace that you risk drift as we update the tools to add new features. It might be better to incorporate using APIs (either import, HTTP, pipeline API or CLI) rather than just bypassing it.
Where: Day 1, 11:58 AM, RSG 2.0 SDK Q&A #2 (incl. FlexGrid)
Q44. how does Hermes’ generational GC interact with RSG reference counting?
Answer:
The SG nodes that Hermes creates exist as JSI host objects, and when they are garbage collected on the TS side, they will be dereffed on the SG side. It is a bit more complicated than that but that’s the main cross over point. We don’t hold reference to BRS objects so there is no issue there
Note from our engineers:
The SG nodes that Hermes creates exist as JSI host objects, and when they are garbage collected on the TS side, they will be dereffed on the SG side. It is a bit more complicated than that but that’s the main cross over point. We don’t hold reference to BRS objects so there is no issue there
Q45. Can we get a copy of the slide deck app code?
Answer:
It’s not currently available, but keep an eye on the examples directory in the future.
Q46. With the zoom on focus, can it easily overlap cells on all sides?
Answer:
If you made its zoom big enough it would overlap
Q47. Would you guys consider making “fps_display” show more info, i.e. frame time statistics?
Answer:
We are looking into other tools to measure framerate. Even programmatically so your app can gather stats.
Q48. Does typescript run faster than brightscript code?
Answer:
Submitted after this answer was given and never read aloud. In the Q015 answer the panel said Hermes executes TypeScript “pretty fast compared to the BrightScript”, with gains everywhere, Littlefield included. No numbers were shared.
Note from our engineers:
Benchmarks says that yes it does in most areas
Where: Day 1, 11:03 AM, RSG 2.0 SDK Q&A #1
Q49. How does FlexGrid compare with RowList, MarkupGrid, and other LabelList?
Answer:
Not read aloud. The talk covered it. The existing lists and grids (LabelList, MarkupGrid, PosterGrid, RowList, ZoomRowList) are good built-in defaults but have three problems:
Where: Day 1, 11:12 AM, FlexGrid talk (responder: Binh Phan)
Q50. I’m glad to see a request made 15 years ago finally was fulfilled: Using a Roku remote to drive a summit slide deck. Thanks!!!
Answer:
Note from one of our engineers:
If you wait long enough anything can happen. Thanks for your patience!
Q51. Is there a native flexbox layout implementation we have access to from JS? How can we share layout and styles with existing React/SolidJS codebases and Framer/Sketch/Miro design tool plugins?
Answer:
Not read aloud. John said in passing that there is no layout capability of that kind on device, so the AI-built code viewer placed everything at absolute positions. On Day 2 (2:14 PM), partners said dynamic measurement (for example multi-line label length) and layout under async rendering are a work in progress. Nothing was said about sharing styles with design tools.
Where: Day 1, 10:50 AM, RSG 2.0 SDK deep dive (talks) (responder: John Roberts)
Q52. Will we see a performance going by using TypeScript?
Answer:
Not read aloud. The Q014/Q015 answers covered it: performance improved across the board, Hermes runs TypeScript fast compared to BrightScript, and the split threads help on multi-core (non-MIPS) devices. The claims were anecdotal. The panel said “we have some benchmarks” but shared no numbers.
Where: Day 1, 11:00 AM, RSG 2.0 SDK Q&A #1
Q53. Will the maximum package size be updated to cover for typescript update?
Answer:
Were sticking with the 4mb max pkg size for now, but we are keeping an eye on it as we get app submissions with TypeScript.
Q54. What are some common performance issues with FlexGrid?
Answer:
Not read aloud. The talk said FlexGrid is fast “but it doesn’t take much to make it slow”, and the cause is usually app efficiency rather than FlexGrid. Examples given:
Where: Day 1, 11:39 AM, FlexGrid talk (responder: Binh Phan)
Q55. It sounds like on the ts side you are combining multiple things into a single node in the actual sg tree. Can you elaborate on how that decision is made?
Answer:
Not read aloud. The talk explained the behavior but not a decision rule. Only the top-level anchor node is a SceneGraph component. Solid sub-components are plain functions, and they “dissolve away” into primitive SceneGraph nodes rather than showing up as composite components in the tree. TSX compiles to Tree Management API calls (createElement, insertNode, setProp).
Note from one of our engineers:
SolidJS components can compose intrinsics (SG nodes) or other SolidJS components. The expression is recursively evaluated until only intrinsics are left, and that is what you see in the SG tree. Fragments can help keep the tree flatter by not requiring a redundant pivot point in the tree (a Group)
Where: Day 1, 10:14 AM, RSG 2.0 SDK deep dive (talks) (responder: John Roberts)
Q56. I’m the future.. Is it possible to build a Roku app without using BrightScript and XML?
Answer:
Same as Q033. The same asker submitted it again.
Where: Day 1, 9:47 AM, Keynote: Tools, RCE + RSG 2.0 SDK announcements (responder: Brian Pinkerton)
Q57. Are the RSG 2.0 bindings synchronous to HostObjects within Hermes? Or is there an async message queue bridging the JS and render thread?
Answer:
Not read aloud. The talk had already answered it. The boundary is asynchronous, with no blocking and no rendezvous. The TypeScript thread only holds references to SceneGraph nodes and cannot touch them directly. Operations such as createElement, setProperty, and insertNode are collected into a transaction. At the end of the TypeScript tick the transaction is pushed to the render thread, which applies it at the start of its next render tick. Events come back the same way, as transactions sent at the end of each render tick. Synchronous callFunc across the boundary is not possible.
Where: Day 1, 10:05 AM, RSG 2.0 SDK deep dive (talks) (responder: John Roberts, then Chakri Kodali)
Q58. With the pluggable focus strategies, can we define our own math?
Answer:
Not read aloud, but answered in the talk just before it was submitted. Yes. The built-in strategies (fixed focus, fixed focus wrap, floating focus) are “pluggable math” made of four overridable functions: computeFocusX, computeFocusY, computeScrollX, and computeScrollY. You override them through the plugin system. They drive both the animation tween and the viewport window calculation. The Fantasy TV example app shows custom focus strategies built this way.
Where: Day 1, 11:28 AM, FlexGrid talk (responder: Binh Phan)
Q59. so why not go full on react native? 
Answer:
Not read aloud. The talk covered the reasoning. Roku chose Hermes, an ahead-of-time compiler, over V8 because of RAM and startup cost. For the framework it chose SolidJS over React or a homegrown framework, because Solid uses much less memory and suits Roku devices better. The talk also said the SDK is “not a web framework”, with no browser environment, CSS, or DOM. React Native was not named.
Note from one of our engineers:
We did evaluate React Native. React itself is bigger and doesn’t suit our device profile. The renderer does not map to SceneGraph neatly and would require extensive changes that would damage performance. We also want hybrid interop between BRS and TS and believe React Native would complicate that and would not be a good fit
Where: Day 1, 10:07 AM, RSG 2.0 SDK deep dive (talks) (responder: John Roberts)
