2021-05-06
1716
#react native
Carlos Mucuho
47470
May 6, 2021 ⋅ 6 min read

Top React Native boilerplates for 2021

Carlos Mucuho A geologist-turned-programmer.

Recent posts:

react children prop how to properly type

How to type React children correctly in TypeScript

Learn modern best practices for typing React children in TypeScript, including ReactNode, PropsWithChildren, ComponentProps, and why React.FC is no longer recommended.

Ohans Emmanuel
Dec 19, 2025 ⋅ 7 min read
complete guide to internationalization next js

The complete guide to internationalization in Next.js

Learn how to internationalize Next.js apps with Lingui and next-intl, covering App Router, RSC, routing, locale detection, and dynamic language switching.

Ivan Vlatkovic
Dec 19, 2025 ⋅ 13 min read

Vite vs. Webpack for react apps in 2025: A senior engineer’s perspective

Vite vs Webpack in 2025: a senior engineer’s take on performance, developer experience, build control, and when each tool makes sense for React apps.

Peter Aideloje
Dec 19, 2025 ⋅ 3 min read
vitest 4 adoption guide

Vitest 4 adoption guide: Overview and migrating from Jest

Learn how Vitest 4 makes migrating from Jest painless, with codemods, faster tests, native ESM, browser testing, and a better DX.

Onuorah Bonaventure
Dec 18, 2025 ⋅ 15 min read
View all posts

3 Replies to "Top React Native boilerplates for 2021"

  1. None that use GraphQL, just REST?

    It’s not just for websites anymore and it can be secured in the same ways as REST. For me it was key to use GraphQL with the Apollo client for subscriptions inside my React Native apps, especially when we’re also using it for React.

    The GraphQL client is available in any language besides C++ which just has a parse. So you can even use it cleanly with ejected apps, on gaming consoles etc.

    It’s easy to have one url endpoint for mobile and one for more powerful clients or just stack them if your role/auth pattern allows. You can even add a public read only one like Gatsby does to the same data source.

    Anoher nice thing is you can query your local cache (that has an identical shcema as the server) and manage app state in the Apollo client rather than bothering with ModX or React, and no need for caching in MongoDB or JSON for app state at all.

Leave a Reply

Would you be interested in joining LogRocket's developer community?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now