Work · alternatives · 2026
24 alternatives to Basis UI
I started my JavaScript journey with React and NextJS. But the more I worked with them, the deeper I questioned myself. Because even though React and NextJS are as powerful as hell, most of my needs in my web app development are just Database CRUD + Auth + Markdown Display. (It's my problem, not React's, I know...) And I found myself spending more time tinkering with the toolings and configs of the framework rather than coding the actual design and logic. There I started my search for the minimum JavaScript framework on which I can focus on what actually matters. I loved Svelte for two…
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
21st.dev▲1,211I originally built this app to organize and reuse interesting React + Tailwind components I came across on Twitter, inspired by the shadcn/ui approach. Later, a friend started contributing their own components, and it got me thinking—this could grow into something bigger, like an NPM for design engineers to share and use components. Would love to hear your thoughts!
2025 · 21st.dev · its alternatives →
- 2
Beautiful Next.js templates built by the Tailwind CSS team.
2022 · tailwindcss.com · its alternatives →
- 3AV
I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!
2022 · dev.aspect.app · its alternatives →
- 4
- 5
Layouts.dev▲699A notebook for building interfaces with Tailwind & shadcn/UI
2024 · layouts.dev · its alternatives →
- 6
Hey HN, I'm Nate, the creator of Tamagui. One is a React framework that does two things differently in hopes of simplifying how we build websites and apps: 1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps. 2. We've partnered with Zero (https://zerosync.dev) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff. ---…
2024 · onestack.dev · its alternatives →
- 7
Next.js 13▲323Build powerful & dynamic web applications – without limits
2022 · nextjs.org · its alternatives →
- 8
Author here. This is an attempt to simplify frontend development: 1. Standards first: User interfaces should be assembled with HTML, styled with CSS, and enhanced with JavaScript. 2. Less abstractions: UI composition should be easy and require as few idioms and abstractions as possible, both on client and server. 3. Design Systems: Design should be a separate subsystem, easily accessible for developers who care about and understand design. 4. Scalability: Complex UIs should retain simplicity as the application grows. Eager to hear your thoughts!
2025 · nuejs.org · its alternatives →
- 9
Once UI 1.5▲302When I started my career and built my first design system, I was beyond excited. It took a lot of iterations, learning and 6 months of work to launch it internally. In the next job, I did it again, then at the following job, again… And no matter which company I worked for, 80% of the design system was the same. I’ve decided to work full-time on the design system I’ve always wanted, and today I’m launching and open-sourcing it. You can use it to build Next.js apps faster, and I’ve designed it in a way that it’s hard to go wrong with it: you can choose any settings, and you’ll end up with a…
Dec 2025 · once-ui.com · its alternatives →
- 10
RedwoodJS▲203Hey everyone, I'm the original co-creator of RedwoodJS. (The framework that myself and Tom Preston-Werner, Rob Cameron and David Price built during Covid.) I had tried to build a developer tool startup (Snaplet), and failed. I rejoined the efforts to add RSC to Redwood, but I realized that we needed a much simpler framework that was closely tied to a platform (We chose Cloudflare). We started building RedwoodSDK a year ago and this is the result. An insanely simple stack. I am incredibly proud of this work, please star our repo and let me know if there's anything that doesn't resonate with…
2022 · rwsdk.com · its alternatives →
- 11
Blitz.js▲270Rails-like framework for React apps, built on Next.js
2020 · github.com · its alternatives →
- 12UG
Hi all, I'm currently working on my hobby project, and one of the fun constraints I put in was to build using as less dependencies as possible. I chose Go as it has a really good standard library, and all went well for building backend. But for frontend, I was wondering whether I should break the constraint and go for React. I tried options like Web Components, but I really didn't like the ergonomics and I didn't want to use jQuery either. Out of curiosity, I was exploring Go's html/template package to see if I can write UIs in a React-like manner. I found most of the online docs using…
2024 · its alternatives →
- 13
- 14AJ
I've been building a web UI library for a side project of mine. I thought it might be useful to others, so I'm releasing it as open source. To put it simply, I realized that most of my pain points with React come from its declarative model ui=f(state). So I'm trying something that I'm calling "imperative JSX." Instead of treating JSX as the source of truth for your UI, it essentially becomes a query interface for DOM manipulation. I first had the idea for it a few months ago, and only began writing it in earnest last week, so it's extremely early and nowhere near production-ready. Still, I'd…
2024 · npmjs.com · its alternatives →
- 15IM
Hi! I made a React compatibility library for a Virtual DOM library (https://github.com/aidenybai/million). The idea is to have much faster rendering (a compiler optimizes virtual DOM beforehand) while ensuring the same developer experience React provides. This is very, VERY early stage, so be prepared for weird bugs / plugin incompatibility / etc. If you have any suggestions, I'd be more than happy if you replied in a comment with it! You can spin up the demo here >> https://stackblitz.com/github/aidenybai/million-react-compat
2022 · its alternatives →
- 16
Launch your SaaS product faster on Web, iOS and Android
2023 · reactnativeboilerplate.com · its alternatives →
- 17
Brings a full-stack React.js web app to life in minutes
2021 · reactapp.dev · its alternatives →
- 18
Serverless SaaS Boilerplate for building faster with Next.js and Node.js on AWS. React SaaS Starter kit with Express.js including authentication, payment and teams.
2021 · nextlessjs.com · its alternatives →
- 19FJ
2021 · forgojs.org · its alternatives →
- 20
The needs of app developers all around for better work tools the world give way to progress. On the UI Frameworks front, one toolkit proves useful.
2014 · touchstonejs.io · its alternatives →
- 21
Minimal boilerplate and configuration for the development of firebase websites with react & es6 - Jon-Biz/simple-static-react-firebase
2016 · github.com · its alternatives →
- 22NJ
Hey, I'm absolutely thrilled to introduce my meticulously crafted Next.js Boilerplate, a project I've maintained for over 2 years. Recently, this project has achieved a huge milestone, over 4500+ stars on GitHub! Initially, I've build the boilerplate for my own use case. A template that allows me to kickstart a new React project with all the necessary tooling. The idea is to setup once and then reuse the template for all my future web projects, eliminating the need to start from scratch each time. This approach tremendously saves time, sparing me from repeatedly configuring and integrating…
2023 · its alternatives →
- 23
A starter project for next js with authentication - Contains React 17 + Typescript + Tailwind CSS 2 + React Query 3 + GitHub Auth + LinkedIn Auth + Password-less Auth + Fauna DB + ESLint + Prettier + Husky - pbteja1998/nextjs-starter
2020 · github.com · its alternatives →
- 24
Hey HN, I'm a developer and long-time OSS contributor. Over the years, I've implemented tons of headless CMSs to give product and marketing teams more autonomy. But there's always been a gap with CMSs when it comes to user interfaces. I kept running into the same issues: poor developer experience, bad performance, no support for dynamic content, and needing vendors for AB testing or personalization, which just gets messy and expensive. Versioning? One change and things break or need manual fixes. Accessing your own data? Good luck unless you're ready to pay extra. So, I built a content API…
2024 · docs.croct.com · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →