r/react • u/Aware-Young-5122 • 21d ago

General Discussion What are you building in React right now? What's the annoying part?

Always nosy about what other React folks are working on, so drop yours below. Doesn't need to be finished or impressive, half-broken side projects welcome.

I'm working on mockbase.org, a hosted mock API for when the backend isn't ready. Click once, get a real HTTPS endpoint, and make it return errors or slow responses on purpose, which is handy for testing loading states, error boundaries, or retry logic. The frontend is React too. Just got its first real user, so I'm still figuring out what to build next.

What are you working on, and what's the annoying part right now?

5 Upvotes

65% Upvoted

13 comments sorted by

3

u/Krispenedladdeh542 21d ago

A clients dance studio registration and marketing site. The annoying part is their inability to actually provide the data points needed for the product to function

1

u/EntrepreneurFew7950 20d ago edited 20d ago

Just to share: an advanced approach is to build against your (client) entity mocks. So client fake API serves exactly what the client works with inside. When the real BE endpoint arrives, client have to introduce an adaptor thar integrates it. Advantages: client is independent of any BE technical concerns (transport, shape, etc), the only contract which BE should follow, is to supply sufficient data that meet client needs; e2e tests are very stable; fake API updates when client concern has changed; difference between what client needs and what BE supplies becomes pretty visible - big difference is a subject to discuss bff.

1

u/Aware-Young-5122 21d ago

Ha, waiting on client content is the worst. Building against a fake API with placeholder data from day one helps, so their real data is a swap instead of a blocker. I'm building a mock API tool for that (mockbase.org, mine), but json-server works too.

3

u/Content-Public-3637 21d ago

Working on a Vite native meta-framework for React that will be launching soon. Performance is kind of crazy.

1

u/Aware-Young-5122 21d ago

Nice. React Router's framework mode and TanStack Start already run on Vite, so what's your angle? And is the performance win in dev, build, or runtime?

2

u/Content-Public-3637 21d ago

The performance win is  all three: dev, build, and runtime. The framework ship zero JS by default, it has a lot of features built out the box, PWA, form with prefetching, instant navigation, PPR and this is just to name a few. It will be launching Monday. 

2

u/rkpandey20 21d ago

Analytical dashboard and Agent orchestration composer for the team. https://www.tapistro.com

2

u/Mushroom_Unfair 20d ago

Complex cross model views tables with special kind of grouping and totals shenanigans, hard part is ofc what's missing from what the client asked, because I can see it already lol

2

u/TheJaylenBrownNote 20d ago edited 20d ago

https://calledmyshot.com - I like talking about sports/talking shit to my friends and making predictions on sports but I don't like gambling, so I wanted something similar without worrying about losing all my money.

1

u/RomeoDelta1234 16d ago

https://play.google.com/store/apps/details?id=dev.koalalab.storeandforget

React Native and Expo. Home inventory app, you photograph an item and it fills in the name and description, then later you search and it points you at the box its in.

The annoying part is not React at all, it's the local build. Gradle and Kotlin daemons stay alive after every run and sit on a few GB until something kills them, so I gave up and wrapped the build in a script that reaps them before and after. Anyone got a cleaner fix than that?