5 posts
#react
React posts from production use. Server Components two years in, Next.js 15 Server Actions and their edge cases, TanStack Query as the main state manager, and how shadcn/ui changed the way teams build design systems. One post lays out an i18n stack for web apps, from plurals to RTL.
Start with the Server Components piece, since it shapes how you use Server Actions and data fetching. Then read the TanStack Query post if your state management feels heavy. The studio builds web applications on React when it fits the project.
Related service: Web application development
(01)
Server Components two years in
RSC was the future of React in 2024. By 2026 it is split between believers and pragmatists. Where it actually helped.
→
(02)
Next.js 15 Server Actions in production
Server Actions reduce CRUD code by 30-50%. They also have edge cases. What we found shipping them at scale.
→
(03)
TanStack Query as state manager
TanStack Query (formerly React Query) was built for server state. Many teams use it as their primary state tool. It works.
→
(04)
Web app i18n stack 2026
Localizing a web app is more than translating strings. Dates, numbers, currencies, plurals, RTL, SEO — all different.
→
(05)
shadcn/ui adoption — design systems shift
Copy-paste, not install. shadcn/ui changed how teams build UIs. Two years later — what stuck and what fell apart.
→