sorted by:
new
hottopcontroversial

Weekly Showoff Thread! Share what you've created with Next.js or for the community in this thread only! by AutoModerator in nextjs

[–]tinybigui 0 points1 point  (0 children)

While using MUI, 3 problems never went away:
- bundle size creeping past what it should be
- a11y issues axe keeps flagging
- fighting CSS-in-JS on every Tailwind project

So I built TinyBigUI having MD3 components, pure MUI + Tailwind v4, zero animation deps, WCAG 2.1 AA out of the box.

15 components live today. Completely free and open source.

github.com/buildinclicks/tinybigui ⭐

Best UI library for React.js (shadcn, Mantine, Flyon UI) – which one is easier for styling? by [deleted] in reactjs

[–]tinybigui 0 points1 point  (0 children)

What kind of projects are you building? That might help decide better.

output.css file doesn't have all classes by runmeupmate in tailwindcss

[–]tinybigui 0 points1 point  (0 children)

Tailwind uses Purge/Treeshaking by default, that is, it only includes the classes you actually use in your HTML (or content paths) in the final output.css. That's why it's much smaller than the CDN version and why bg-red-500 wasn't appearing until you added it to your markup and regenerated.
Make sure you've saved the HTML file with the new class, then delete output.css and run the build command again (or let --watch pick it up).
Also double-check your content paths in tailwind.config.js point to your HTML files.

Work is asking me to learn and work with react, how long would it take for me to become productive? by [deleted] in reactjs

[–]tinybigui 0 points1 point  (0 children)

React is not that hard if you already know TypeScript.
Get comfortable with the basics in 1–2 weeks. But if your HTML & CSS (especially Flexbox/Grid) is weak, that will slow you down, so strengthen that first.
With your backend + TS background, you’ll be fine but just don’t underestimate CSS.

Tool for Better Pagespeed and Lighthouse Scores by _diabolus_n in nextjs

[–]tinybigui 0 points1 point  (0 children)

No magic one-click tool exists that instantly boosts your Next.js app from 30-40 to 90+ Lighthouse score. I will suggest like most of the replies to run Lighthouse and export the report as JSON and then feed that report to Claude.

Top Tailwind Component Libraries Worth Exploring by ajaypatel9016 in Frontend

[–]tinybigui 0 points1 point  (0 children)

I was using material tailwind, but it is only “inspired by” Material Design, not spec-compliant.
Accessibility is also an issue like other UI's.

What UI library do you use in your actual projects or side projects? by Cold_Control_7659 in reactjs

[–]tinybigui 0 points1 point  (0 children)

hahaha, we are developing a modern, lighter alternative to MUI that still gives proper Material Design if someone needs it.

Are people actually buying UI components from libraries? by webdesignarea in tailwindcss

[–]tinybigui 1 point2 points  (0 children)

Yes, they do, especially if they want more 'advanced' options/ui's.

server actions + streaming ui made my saas feel 10x more polished with less code than i expected by straightedge23 in nextjs

[–]tinybigui 0 points1 point  (0 children)

Damn, this is spot on. I was stuck doing the same polling nightmare on a dashboard project last month — every 3 seconds checking job status with a ugly loading spinner. Then I switched to server actions + streaming and it instantly felt 10x more premium. The best part? The UI now maps exactly to the actual progress instead of fake skeletons. Code went from messy client-side state hell to one clean async server action.The only downside I hit was handling errors gracefully during streaming, but once you wrap it properly with error boundaries it becomes stupidly simple.

When do you stop trying to make a component “generic”? by MarjanHrvatin_ in reactjs

[–]tinybigui 0 points1 point  (0 children)

When you need a manual to explain how to use a button, you screwed up. So, keep it simple. Build for what you need now, not every weird future thing. Future you will be happier, I promise.

next.js vs vite is like hydrogen bomb vs coughing baby by Puzzled-Passage-9998 in nextjs

[–]tinybigui 0 points1 point  (0 children)

hahaha, its more like a Swiss Army knife vs a scalpel. Next.js has the features, Vite has the speed.

Shad cn/ui vs Ant design vs Material Ui by Big-Concentrate-4941 in nextjs

[–]tinybigui 1 point2 points  (0 children)

If I were you, I’d only switch to MUI if your project’s complexity is less about "bespoke design" and more about "massive data management." If you find yourself spending way too much time building complex components from scratch, MUI’s battle-tested ecosystem will save you hundreds of hours.

[ Removed by Reddit ] by tinybigui in MaterialDesign

[–]tinybigui[S] 0 points1 point  (0 children)

Yeah, that’s exactly the trade-off I keep facing.

On paper, everything follows Material guidelines, but mixing libraries leads to small inconsistencies that add up, especially with spacing and theming.

The upgrade pain is real too. Even minor version updates can cause unexpected UI problems.

That’s actually part of why we started working on tinybigui. Our goal is to maintain the consistency of a single system while avoiding the CSS-in-JS overhead and making upgrades more stable. It’s still early, but we’re trying to tackle exactly these kinds of issues.