New Penpot render engine - CourtneyR.dev's 2nd Brain

New Penpot render engine 🔗 **Source:** [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) > [!note]+ Document Notes > tags: [Penpot, Render engine, WebAssembly] > author: [MISSING] > source: [Merlin AI] > reference: [https://www.youtube.com/watch?v=ciG0U5jJtHY] > date created: > > # 🏷️ Title: New Penpot render engine >  ## 🧰 Action Inbox - [H1] Confirm Skia adoption with commit link — forum thread. [oai_citation:0‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) - [H2] Note WASM constraints for plugins — MDN overview. [oai_citation:1‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) - [H3] Request tile-system dev notes — forum performance post. [oai_citation:2‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) - [H4] Track bug-fix migration policy — forum thread. [oai_citation:3‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) - [H5] Document font fallback behavior — prepare test matrix. (Video link inaccessible to tool; based on provided transcript.) - [H7] Watch background blur rollout — subscribe to renderer update thread. (Video link inaccessible to tool; based on provided transcript.) - [H8] Plan for public beta testing — create feedback form. [oai_citation:4‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) - [H2] Educate devs on WASM security model — MDN reading task. [oai_citation:5‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - Penpot is shipping a new render engine. It replaces DOM/SVG bottlenecks with Skia and WebAssembly. [oai_citation:6‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) - Skia underpins Chrome and Flutter, which signals maturity. [oai_citation:7‡Android Git Repositories](https://android.googlesource.com/platform/external/skia/%2B/fb4b77f/site/index.md?utm_source=chatgpt.com) - WebAssembly brings near-native speed in browsers. This changes performance ceilings. [oai_citation:8‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) - The team adds a tile system, font fallback, and export improvements. They aim for quality and consistency. (Video link inaccessible to tool; based on provided transcript.) - Bottom line: Expect smoother rendering, better exports, and a public beta soon. [oai_citation:9‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) ## 📖 Main Content - Penpot moves past DOM/SVG limits toward a canvas+Skia path. Forum posts describe an experimental WASM engine and performance goals. [oai_citation:10‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) - Skia is a battle-tested 2D library. It powers Chrome, Android, and Firefox derivatives, and sits inside Flutter. This reduces risk. [oai_citation:11‡Android Git Repositories](https://android.googlesource.com/platform/external/skia/%2B/fb4b77f/site/index.md?utm_source=chatgpt.com) - WebAssembly executes sandboxed binaries in browsers. MDN notes near-native or native performance in some contexts. This justifies the switch. [oai_citation:12‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) - A tile system avoids heavy image caching. The forum focus on canvas engine speed aligns with this approach. [oai_citation:13‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) - Planned UX wins include reliable font fallback and consistent exports. That removes OS and headless-browser variability. (Video link inaccessible to tool; based on provided transcript.) - A public beta and iterative bug-fix migration are expected. Opt-in testing is hinted in forum updates. [oai_citation:14‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) ### 🗒️ Notes #### ⏱️ [00:14](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=14) Context and rationale - The speaker frames SVG performance limits and the need to evolve. ### [H1] Penpot adopts Skia for rendering > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “We decided to use the Skia library which is a 2D graphics open source library…” Skia offers broad feature coverage and maturity. Flutter and Chrome use Skia. [oai_citation:15‡Android Git Repositories](https://android.googlesource.com/platform/external/skia/%2B/fb4b77f/site/index.md?utm_source=chatgpt.com) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=61) #xref #articleseed ID:rw_[MISSING] #### ⏱️ [01:01](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=61) Technology choices ### [H2] Engine uses WebAssembly for speed > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “and we are also using web assembly which is like a lowlevel like assembly language and it runs let's say like near native performance directly on the browser.” WASM can achieve near-native performance in browsers. See MDN guidance. [oai_citation:16‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=95) #xref ID:rw_[MISSING] #### ⏱️ [01:50](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=110) Rendering pipeline changes ### [H3] Tile system replaces cached images > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “we have built our own tile system which um is developed directly in within the render.” Tiles reduce redraw cost and memory churn. Forum posts target canvas speed. [oai_citation:17‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=120) #xref #articleseed ID:rw_[MISSING] #### ⏱️ [02:44](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=164) Quality and frame rate ### [H4] Team fixes bugs in new renderer > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “what we are doing is to fix them directly in the new render.” This avoids patch debt in the legacy path. It accelerates convergence. [oai_citation:18‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=211) #xref ID:rw_[MISSING] #### ⏱️ [03:31](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=211) Shadows, clipping, and text ### [H5] Penpot implements its own font fallback > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “we have implemented our own font fallback” This reduces OS-dependent differences. It stabilizes exports and previews. [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=257) #xref #articleseed ID:rw_[MISSING] ### [H6] Designers can upload custom fonts > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “you can uh upload your own font and and use it directly” This improves creative control and brand fidelity. [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=257) #xref ID:rw_[MISSING] #### ⏱️ [05:06](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=306) New capabilities ### [H7] Background blur filter will ship > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “we will bring also the so demanded background blur uh filter” Feature demand is high in the community. (Video link inaccessible to tool; based on provided transcript.) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=306) #articleseed ID:rw_[MISSING] #### ⏱️ [06:00](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=360) Compatibility and rollout ### [H8] Public beta release approaches > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “we are going to publish a public beta version” Opt-in testing aligns with forum hints about beta access. [oai_citation:19‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=360) #share ID:rw_[MISSING] ## 📚 References - [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) — YouTube. *Tool could not fetch the page; link may be rate-limited.* - [New processor — WASM-based canvas engine (experimental)](https://community.penpot.app) — Penpot Community. [oai_citation:20‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) - [How Canvas engine got faster](https://community.penpot.app) — Penpot Community. [oai_citation:21‡Penpot Community](https://community.penpot.app/t/background-blur-effect-please/4891?utm_source=chatgpt.com) - [Skia site page (android.googlesource.com)](https://android.googlesource.com/platform/external/skia/) — Project overview. [oai_citation:22‡Android Git Repositories](https://android.googlesource.com/platform/external/skia/%2B/fb4b77f/site/index.md?utm_source=chatgpt.com) - [WebAssembly on MDN](https://developer.mozilla.org/) — Background and performance notes. [oai_citation:23‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) - [Skia + WASM usage (Uno Platform docs)](https://platform.uno/docs/articles/external/skia-wasm.html) — Implementation example. ## 🗣️ Paraphrase - Penpot is shifting rendering to a Skia+WASM engine for speed and quality. Compatibility remains stable for APIs and exports. - The team adds a tile system, consistent text rendering, and plans features like background blur and a public beta. ## 📰 Newsletter - Penpot previewed a Skia+WASM renderer with smoother frames and reliable exports. Community threads show a WASM canvas engine and performance work. Skia powers Chrome and Flutter, which supports this path. Expect a public beta and improved font handling. Link your teams to WASM and Skia primers for faster onboarding. [oai_citation:24‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) ## ✅ Action Items #### DevRel - Publish a short explainer: Skia+WASM for web designers; include code samples. - Record a side-by-side perf demo and capture metrics. - Open office hours to collect beta feedback and reproduction steps. #### OSPO - Review WASM sandboxing guidance and dependency licensing notes. - Add a renderer adoption checklist to the contribution policy. - Track upstream Skia security advisories with response SLAs. #### Community - Run a testing cohort on the beta renderer with issue templates. - Share font fallback test cases across OSes and browsers. - Collect background blur design examples for validation. #### WordPress - Playground: prototype Skia+WASM graphic experiments and measure costs. - Training: prepare a “design exports 101” module for developers. - Documentation: document export parity and known differences. #### The WPOCC - Fund small bounties for cross-tool export tests. - Support a maintainer sprint on accessibility and text rendering. - Publish a transparent beta feedback report. ### FAIR - Draft provenance checks for exported assets and fonts. - Document sunset clauses for legacy renderer patches. - Add a renderer capability scorecard for governance reviews. ## 🧪 Hypotheses - Skia+WASM reduces frame latency versus SVG in complex scenes. - A tile system improves panning performance under high node counts. - Custom font fallback reduces OS variance in exports by 90%. - Beta participation correlates with faster bug resolution. ### 📊 Methodology - Build identical scenes in both renderers; record FPS and latency. - Stress-test with layered text, shadows, and clipping. - Compare exports across OSes using visual diff tools. - Track cohort feedback velocity and fix lead time. ### ❓ Questions - How does the renderer handle HDR and color management? - What are memory ceilings on low-end devices? - Will background blur impact mobile battery life? ### 🔮 Future Research - Evaluate WebGPU pathways for future effects. - Explore font shaping performance with complex scripts. - Study incremental rendering strategies for collaboration. ### 💡 Implications - Teams can expect smoother prototyping at scale. - Exports become consistent, improving handoff to developers. - Education must cover WASM constraints and testing practices. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ≈ 9–10. #### 👀 Visual learners - Present: before/after videos and screenshots. - Improve: architecture diagrams and tile system visuals. #### 🔊 Aural learners - Present: talk recording. - Improve: 3-minute audio summary with key terms. #### 🗣️ Verbal learners - Present: definitions for Skia, WASM, tiles. - Improve: analogy comparing tiles to map rendering. #### 🧩 Kinesthetic learners - Present: beta testing tasks. - Improve: reproducible perf labs with checklists. #### 🧠 Logical learners - Present: benchmarks and timelines. - Improve: error budgets and SLOs for exports. #### 🧑‍🤝‍🧑 Social learners - Present: forum threads and cohorts. - Improve: peer review rubrics for issues. #### 🧘‍♀️ Solitary learners - Present: self-paced notes. - Improve: reflection prompts on tradeoffs. #### 🌿 Naturalistic learners - Present: none explicit. - Improve: energy-use notes for effects and filters. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: headings and landmarks in docs. - Improve: alt text guidance for exports and previews. #### Keyboard navigation - Present: standard browser focus rules. - Improve: skip links in docs and demos. #### Contrast and readability - Present: consistent text rendering goal. - Improve: verify 4.5:1 in export presets. #### Text resizing and reflow - Present: responsive docs. - Improve: prefers-reduced-motion coverage. #### Media and captions - Present: captions on talks. - Improve: downloadable transcripts and audio descriptions. #### Forms and interactions - Present: bug templates. - Improve: inline validation and forgiving inputs. #### Standards reference - Map issues to WCAG 2.2 AA criteria. ### 🌍 DEIB Assessment #### Cultural breadth - Present: global forum participation. - Improve: multilingual testing instructions. #### Inclusive language - Present: straightforward vocabulary. - Improve: glossaries for non-native speakers. #### Neurodiversity support - Present: chunked updates. - Improve: icon+text labels in docs and UI. #### Representation - Present: varied voices in community posts. - Improve: balanced examples in demos and imagery. #### Psychological safety - Present: respectful feedback culture. - Improve: published moderation flow and escalation paths. ### ✅ Logical Validity #### Strong reasoning - Technology choice cites maturity and reuse (H1). This is a sound pragmatic argument. [oai_citation:25‡Android Git Repositories](https://android.googlesource.com/platform/external/skia/%2B/fb4b77f/site/index.md?utm_source=chatgpt.com) - Performance goal uses WASM’s speed claims cautiously (H2). MDN supports the premise. [oai_citation:26‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) - Migration strategy fixes bugs in the target renderer (H4). This reduces wasted effort. [oai_citation:27‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) #### Fallacies - None apparent. The talk avoids over-promising by showing incremental rollout. #### Tone of voice - Pragmatic, technical, and community-minded. The speaker emphasizes stability and openness to feedback. ### 🛡️ DARVO Analysis - Deny: No denial patterns observed. - Attack: No attacks on critics observed. - Reverse victim/offender: Not present. The talk invites critique and testing. ## 🎯 Conclusion - Penpot’s renderer shift to Skia+WASM targets speed and consistency. Forum posts align with this direction. A beta and quality improvements are incoming. Prepare teams for WASM constraints, export parity tests, and feedback loops. [oai_citation:28‡Penpot Community](https://community.penpot.app/t/its-time-for-penpot-to-almost-move-away-from-the-dom/6437?page=2&utm_source=chatgpt.com) ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Penpot adopts Skia for rendering > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) by an unnamed author via [[Merlin AI]]. Published [MISSING]. Accessed . > “We decided to use the Skia library which is a 2D graphics open source library…” Two lines: why Skia’s maturity matters; link Skia projects. [oai_citation:29‡Android Git Repositories](https://android.googlesource.com/platform/external/skia/%2B/fb4b77f/site/index.md?utm_source=chatgpt.com) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=61) #xref #articleseed ID:rw_[MISSING] ### [H2] Engine uses WebAssembly for speed > [!quote] [New Penpot render engine](https://www.youtube.com/watch?v=ciG0U5jJtHY) > “and we are also using web assembly which is like a lowlevel like assembly language and it runs let's say like near native performance directly on the browser.” Two lines: connect to MDN notes; flag sandboxing. [oai_citation:30‡MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Fundamentals?utm_source=chatgpt.com) [view highlight](https://www.youtube.com/watch?v=ciG0U5jJtHY&t=95) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Skia adoption improves renderer scalability - Compare SVG vs Skia under complex scenes. - Links: [[Rendering-Architecture]] [[Performance-Tests]] #### [Z2] WASM enables near-native browser rendering - Measure CPU and memory during stress tests. - Links: [[WebAssembly]] [[Performance-Tests]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft a beta feedback rubric — context/https://community.penpot.app #fleeting #inbox - [F2] Build an export parity test pack — context/https://community.penpot.app #fleeting #inbox - [F3] Prep a Skia+WASM explainer deck — context/https://developer.mozilla.org #fleeting #inbox ---  ## 📺 Video ![](https://www.youtube.com/watch?v=ciG0U5jJtHY) --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=ciG0U5jJtHY)* **[00:04]** [Music] Okay. Did you listen to me? Well, my voice is a little bit off because yesterday I was having so much fun talking to all of you. So, I'm sorry for that. Um, yeah, I'm Elena and I'm working on the team that is building the new render engine and I'm going to be talking about it today. So one year ago, we published this blog uh this blog post um and we said that it's time for PMPOP to move away almost uh from the DOM. And **[00:38]** long story short, right now our render is an SV render, right? Which is a standard. It works great, but in terms of performance, it doesn't scale that well. So that's why we needed to think of a different solution that work that works faster. So I'm going to get a little bit techy on this. I'm going to to talk you about the technologies that we are using. We decided to use the Skia library which is a 2D graphics open **[01:08]** source library that is widely used uh for uh well in many projects such as uh Chrome, Android, Flutter and Libra Office as well if I uh remember correctly. So that's why we chose it because it had like anything that we needed. So we didn't have to reinvent the wheel and and yeah and the project is very mature and we are also using web assembly which is like a lowlevel like assembly uh language and it runs **[01:40]** let's say like near native performance directly on the browser. So it works like this. We can use directly the Skia functions that we are using for rendering different shapes directly from the uh browser through web assembly super fast. Okay. So what um what has this um helped us to do? Well, basically right now our rendering system relies on um let's say cached images when it comes **[02:10]** to fixed performance bottlenecks. So that uh we are not going to need that anymore because we have built our own tile system which um is developed directly in within the render. So we don't have to like rely on external stuff for caching uh and for improving performance and it has um unlocked many things. So we have a couple of videos to um compare in this case um how the performance has improved. I don't know if we can like see the videos, but in **[02:42]** any case, if we take a look. Yeah, here it is. So, this is um the carbon render. So, you can see that the quality of the image is not like super great. The frames per second I like are like a bit bumpy. So, with the current one, if we take a look at it, we are going to see that it not it is not only like uh you know, you can see that it has a better quality. It's way smoother. it works uh faster as well. So um yeah, that's it. **[03:16]** Okay. Of course, a lot of you um have been asked about bugs or issues that we had. So what we are doing is to fix them directly in the new render. So like I don't know shadows clipping and some stuff that we can like like it makes no sense to fix it in the current render since we are developing an uh a new one. So we are including them directly there and um I'm quite proud of this one because you know I love emoji. I think that most of us love emoji and you know **[03:48]** text rendering it's hard. So um if you see those uh images um we can see that the uh the phone that we are using is different that is because our current render relies on the phone fallback from the browser directly. So when you use pampot on different operating systems what happens is that you are going to see probably different stuff and we wanted to unify that. So that's why we have implemented our own font fallback and it also means that although we are **[04:20]** now using a default emoji font you can uh upload your own font and and use it directly which is uh kind of cool and it also means that this is not longer going to happen because if you have uh tried to export um files with emoji or with other samples that might happens because right now we are using um headless browser to rendering those kind of exports which is also like a common way uh right now to do that kind of things. But now since we are already using a **[04:51]** Skia which exports um also uh different um image formats and so on, we can use that for exporting images. So you're not going to see that anymore and you will always be exporting the same. And uh this means that we can also start adding more features to what we have. So we have a little video as well because um one of the demanded features that we had was uh text to path. So you can like directly build your own icons on pimpot. **[05:22]** So yeah I guess there's some excitement here and yeah and we will bring also the so demanded background blur uh filter as well. So well does it mean that uh there's anything that is going to change? Well actually no because we are keeping our core values right. So you will be able to export your code just like we are doing right now. So the new render it it only affects visuals and **[05:55]** the way you work with the with the application. Nothing else. Everything is going to be the same. You can still export into a SVG. So we are being consistent. we are going to use the same data model. It doesn't affect uh our APIs or whatever. So yeah, don't worry about that. And you may be wondering okay so what's next? So the team is working hard on a lot of stuff like for example integrating the text editor within the new render but we can announce you that in the upcoming weeks **[06:25]** we are going to publish a public beta version so you can all uh test it out. Yeah. And that's it. Thank you very much. [Music]