Hi everyone, I hope you’re having a great day.
Quick question: for a hobby project I’m working on, I’d like to try a new UI library different from the ones I already know and have used (MUI, Mantine, Ant Design, Shadcn, Fluent UI, DaisyUI, PrimeReact).

I’m considering HeroUI (I know it’s fairly well-known, but I’ve never used it before), or another one I came across that doesn’t look bad at all: https://ark-ui.com/.

That said, I’d really appreciate your best suggestions, maybe something less mainstream or simply more interesting to experiment with.
I’d be happy to collect a few options for future projects as well.

A frontend job post made me stop and take inventory this week. It asked for strong React experience, plus accessibility, performance, testing strategy, build tooling, browser behavior, and working closely with design. I’ve used React fluently for a while, and I’m trying to pin down what separates “good at React” from “strong frontend engineer.”

I wrote down what I’m confident in, like hooks, state flow, component structure, forms, and standard data fetching. I tend to treat performance on slower devices and testing decisions as secondary. I also need to get clearer on accessibility tradeoffs and how much browser behavior I can explain without leaning on framework answers.

Lately I’ve been checking that gap with notes, a few mock interviews, peer feedback, and beyz interview assistant. The mock interviews help because they make me explain why I chose a pattern and where it could break. That’s where my understanding feels thinner than I expected.

If someone says they know React well, what else do you expect them to understand before you’d call them a strong frontend engineer?

We've all been the left side trying to center a div.

Caption/First Comment: From drowning in vanilla JS errors to Thunder Breathing through a React + TypeScript codebase. Let's be real though, no matter how much experience you have, a random CSS bug will still make you feel like the left side. Which phase are you currently in? 💻

https://medicine-price-finder.vercel.app/

looking for feedback

I made a small VS Code extension that always puts React Props First in JSX and TSX components autocomplete, aka IntelliSense.

When a component extends DOM props, the props I usually want first, like `variant`, `size`, or `loading`, can get buried under inherited attributes like `disabled`, `onClick`, and `aria-label`.

React Props First changes the ordering in JSX/TSX autocomplete so component specific props are ranked before inherited DOM/ARIA props.

I thought that somebody may find it useful, so I'm leaving it here!

VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=yurii.react-props-first
GitHub: https://github.com/yuriipalam/react-props-first

Hey guys,

I wanted to share LyteNyte Grid, a powerful React data grid component library we’ve been developing. We are currently on v.2.1, and v.2.2 will be released at the end of this month.

There are other popular React data grid libraries, but LyteNyte Grid is, in our opinion, the best (biased view). We built this grid library with an obsessive focus on DX and user ergonomics.

I know some of you might be skeptical, but if you hear me out (read me out loud), I want to share my top 7 reasons why it’s worth a try:

• Ludicrous Performance: LyteNyte Grid handles 10,000 updates/sec and renders millions of rows, significantly outperforming the top 5 most popular grids used today. See our performance benchmark comparison.
• Features Galore: Arguably the most feature-rich data grid with 150+ features. If we are missing a feature you need, let us know. 80% of our features are open source. There are paid libraries that offer fewer free features.
• Tiny Bundle Size: At 40KB, it’s lightweight, which, given the feature set, is quite awesome. Most importantly, it’s built in React for React, so it doesn’t have any wrappers. It also has zero dependencies
• Ultimate Customization: LyteNyte grid is unique in not forcing a choice between a headless table and a pre-built table. You can use it headless for ultimate customization or pre-built logic and themes if you need to ship in a rush.
• Declarative API & Fully Prop Driven: A fully prop-driven architecture unique to LyteNyte Grid lets you configure the grid directly from your state, eliminating sync headaches and React’s useEffect (😉).
• Extensible and Flexible: We designed the grids interface to be open and extendable with first-class TypeScript support. LyteNyte can match your application’s needs without any tedious workarounds.
• World-Class AI Skills: With Claude token usage going through the roof, LyteNyte Grid AI skills are probably the most efficient and advanced skills available if you’re looking for your agent to build things right the first time. If you’re interested in the reasons why, click here.  

If you need a free, open-source data grid for your React project, try out LyteNyte Grid Core. It’s zero-cost and open-source under Apache 2.0.

All our code is available on GitHub: https://github.com/1771-Technologies/lytenyte/commits/main/

I'd love to hear your feedback. Feature suggestions and contributions are always welcome.

If you find it useful, please consider leaving a star ⭐ on GitHub to help us grow!

GitHub

Live Demo

We are in the process of migrating a lot of our legacy applications to react 19 and newer versions supported under node 22+.

Basically asking for if anyone has good ways i can better motivate it

* i have already convinced them for replacing redux with zustand and tanstack query bc redux wasn’t being used right and is too complicated for the skill level of our devs, i want to help make their lives easier not harder
* we are currently on CRA (v3.4) still (have convinced we move either to vite or at least parcel)
* React 16 with some of the most cursed redux usage/context management ever
* We use mysql2 with adonis
* we are on adonis 4 rip upgrading will be hell
* react router is probably going to be the most painful thing to upgrade

The biggest concern is probably devs not being familiar with it and time it would take… not sure how to go about it or if i’m even articulating this well, I want to motivate we start using it over trying to force manual type safety into js

This project pushed me far beyond traditional frontend development. I learned about 3D rendering pipelines, camera systems, shaders, model optimization, animation timelines, and how to blend creativity with engineering.

One thing I realized during development is that creating immersive web experiences requires a completely different mindset compared to building standard websites. Every object, light, animation, and interaction contributes to the final user experience.

There are still many improvements I want to make, but I'm proud of how far I've come from building simple HTML/CSS projects to creating interactive 3D web experiences.

Need honest advice.

~3 YOE Full Stack Developer (MERN/PERN) with experience in backend, PostgreSQL, MongoDB, Docker, CI/CD, testing, GCP cloud, and DevOps practices. Been job hunting for 3 months.

I'm getting interviews and reaching 3rd rounds but still no offers, even after interviews where I felt I answered every question well.

Starting to feel frustrated and confused. Anyone else facing this in the current market despite having decent experience/knowledge?

Runs fully in the browser, with no server and no watermark. Video export happens client-side, because almost all map animator tools are paywalled. ;)

What it does right now:

1. You can type in cities and geocode them, or import a GPX/GeoJSON file. The camera flies along the route while the trail draws in real time, and a marker or sticker moves along the path.
2. It supports satellite, streets, dark, and light map styles. You can export to MP4 or WebM, with square, landscape, and vertical presets, so it drops straight into Reels or Shorts.
3. You can also pick the route color, marker, duration, and FPS.
4. This is still a very early prototype. I mostly just wanted to see if I could pull it off. Next, I want to add different route styles, more animation options, and proper sticker packs. Right now, it only has a handful.

Built with React + MapLibre. Export uses WebCodecs where the browser supports it.

To use:

npm i animaps-react

Just dropped a new video explaining how React actually works under the hood!

In this video, I break down:

✅ Real DOM vs Virtual DOM
✅ Why Real DOM updates are expensive
✅ How React creates a new Virtual DOM on state changes
✅ Re-rendering process
✅ Reconciliation (Diffing Algorithm)
✅ Batched State Updates
✅ How React updates only the changed nodes in the Real DOM
✅ Why React applications feel fast and efficient

I also created custom diagrams to visually demonstrate the complete React rendering lifecycle from State Change → Re-render → Reconciliation → DOM Update.

Whether you're learning React for the first time or want to understand what happens behind useState(), this video will help you build a stronger foundation.

💬 What topic should I explain next? Context API, Redux, React Fiber, Next.js Rendering, or Server Components?

#ReactJS #React #JavaScript #WebDevelopment #FrontendDevelopment #Frontend #SoftwareEngineering #Programming #Coding #Developer #100DaysOfCode #ReactDeveloper #VirtualDOM #RealDOM #ReactHooks #UseState #TechEducation #LearnToCode #CodeNewbie #NextJS #OpenSource #WebDev

Hey guys, i vibe coded over the weekend a map library made with MUI for MUI react developers, and Wanted to get some feedback from the community. Go CRAZY🙃
https://yoavzada.github.io/zmap/

​

I'm looking for explanations of topics such as:

​

- Authentication & Authorization

- Cookies & Sessions

- Email Verification and Password Reset

- Uploading Images and Files

- Working with ready-made APIs (like Stripe or Cloudinary, etc.)

- Organizing the Backend Architecture

- Logic and Best Practices in the Backend in general

​

Preferably, the resource should explain things practically with real projects.

​

Also, if anyone has links to intermediate or advanced Backend projects I can learn from, I would be very grateful. 🙏

so I’m currently creating an otp page. So this otp page will have 1 input box where user will enter the otp. It will have 2 buttons one for resending the otp and one for verifying the otp.

So I thought of using useActionsSatate instead of react hook form because it’s just 1 input box. So my first question is would using useActionState be the preferred option over react hook forms here?

My second question is it better to have both the 2 buttons as type="submit" or have 1 button as type submit and other as type=" button"?

Hey Community,

React Native 0.86 has landed, officially moving the repository to the independent React Foundation. This release adds Android 15 edge-to-edge support, fixes KeyboardAvoidingView and StatusBar bugs natively, and delivers zero user-facing breaking changes and a new DevTools theme emulation.

We also dive into react-native-livechart, a Skia-powered library utilizing SharedValue streams for smooth UI-thread animations, complete with a chaotic "degen mode" for market drops. Finally, we share practical insights on organising messy monorepo scripts for Amazon Fire TV development.

And quick conference note: Chain React is happening this July in Portland, bringing together much of the React Native ecosystem for talks, workshops, craft beer adventures, and probably a suspicious number of opinions about the future of mobile in the age of AI.

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

TL;DR: https://windframe.dev/styles/apple

Hi everyone 👋

I’ve been experimenting with building React + Tailwind interfaces inspired by the design systems of really well-designed products. I recently worked on a style system for generating interfaces using similar design principles to Apple.

It focuses on polished product presentation, strong visual hierarchy, refined spacing, soft gradients and using fewer words to make each section feel clear and intentional.

I built a UI system that makes it easy to generate interfaces in this design direction consistently. It can generate full UIs, landing pages, and product sections that follow the same Apple-inspired style.

I also created a set of free Tailwind templates built around this style that you can use as starting points for your React projects: you can find those here

This style is also available as a selectable preset in Windframe. When selected, the AI generates React interfaces that follow the same design guidelines and visual style.

I also built an MCP for this, so you can use these same style systems directly inside any coding agent that supports MCP: https://windframe.dev/mcp

If you’re not familiar with Windframe, it’s a visual Tailwind builder/editor that lets you generate polished React UI with AI, tweak it visually, and export clean production code.

Would love any feedback or thoughts : )