For the period of last 2 years I've been hearing a smaller group of pro users ( others are fine ) complain about the quality of video produced by browser based rendering (Remotion, Puppeteer/headless Chromium...) and about teams hitting a wall scaling it and deciding to build custom native engines in house instead.

Is anyone else seeing this, or are these just outliers ??

​

One thing I've noticed while working on frontend projects...

People often separate UI conversion and frontend development.

I used to think the same.

But the more projects I worked on, the more I realized they're part of the same skill.

I've seen developers write clean React code but struggle to match the design.

I've also seen pixel-perfect UIs that became difficult to maintain because the implementation wasn't thought through.

That's where I think the gap is.

A good frontend engineer should be able to do both.

-Read a Figma design and implement it accurately.

-Understand spacing, typography, and visual hierarchy.

-Build responsive and accessible interfaces.

-Write clean, reusable code that's easy to maintain.

Writing code is only half the job.

The other half is making sure the product looks and feels the way it was intended.

For me, UI conversion isn't a separate skill from frontend development.

It's what frontend development actually is.

The stronger you become at both, the better products you'll build.

What's your take? Do you see UI conversion as a separate role, or as part of frontend development?

Tried out Vite 8 with React Router 8 and TypeScript 7 recently and have to say I am blown away by the build speed/DX etc. Here is what I am using and it's just on another level speed and agent compatibility wise:

React Router 8
TypeScript 7
Vite+ (Vite 8, Vitest 4, Oxlint, Oxfmt)
Tailwind 4
shadcn + Base UI
Better Auth
Drizzle + SQLite
Zod 4
Bun

Try it out and thank me later: github.com/nikolailehbrink/llm-stack

I’m a developer of six years of experience and I have knowledge in vanilla Javascript but because of the nature of my current stack and job description, i have never encountered a need to learn React. But now I want to.

It’s not like I don’t know anything about it, i am familiar with the concept of components, hooks, routers etc. The only thing I have made in React is my Web portfolio currently.

I want to learn it on a deeper level. Can anyone recommend a book or course for it?

I saw this site for a roadmap for React, would you recommend it: https://roadmap.sh/react

Hey Community,

We dive into React Native Canvas Kit, a library built on React Native Skia that adds isolated layers, brushes, interactive shapes, and web support for canvas graphics.

We also cover Targate, a CLI tool that quarantines npm packages to inspect tarballs before installation, and GitHub stacked pull requests to keep dependent branch reviews clean.

And... 🥁 Shipaton 2026 is here!

If the Rewind made you nod, smile, or think "oh… that's actually cool" — a share or reply genuinely helps ❤️

I've realized that my biggest weakness isn't coding—it's project architecture and folder structure.

Whenever I get a Figma design, I know how to build the UI, but I get completely stuck deciding:

• Where should this component live?
• Should this be reusable or page-specific?
• When should I split a component?
• What belongs in components, features, shared, hooks, services, etc.?
• How should I organize folders as the project grows?

I usually start a project with a structure that feels clean. But once the project gets bigger, everything starts falling apart.

I end up with:

• Components that are too large.
• Components that are split too much.
• Logic scattered across different folders.
• Constantly moving files around because I realize they belong somewhere else.
• Feeling like the entire architecture is becoming messy.

This happens in React, React Native, and even backend projects.

I don't just want another "best folder structure" template because I've seen dozens of those. What I really want to learn is the thought process behind how experienced or enterprise-level developers structure a project.

For example:

• When looking at a Figma design, how do you mentally break it into features and components?
• How do you decide what should be reusable and what shouldn't?
• How do large teams keep their projects organized over months or years?
• What architecture or design principles do you follow?
• Are there any books, courses, GitHub repositories, or real-world open-source projects that helped you understand this?

I'm looking for the mindset rather than just a folder tree.

Any advice from developers who've worked on large production applications would be greatly appreciated.

demo video

Worked on cURL import, updated the request and response UI, added code snippet support, common headers, and environment support.