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:

Typescript or Zod for Validation?

TypeScript vs Zod: Clearing up validation confusion

Learn when to use TypeScript, Zod, or both for data validation. Avoid redundant checks and build safer, type-sound applications.

Alexander Godwin
Oct 6, 2025 ⋅ 3 min read
Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read

How to use AI to build accurate ShadCN components

AI agents often break shadcn/ui components with outdated docs or made-up props. The MCP server fixes this by giving live access to registries. In this tutorial, we’ll set it up and build a Kanban board to show it in action.

Chizaram Ken
Oct 3, 2025 ⋅ 5 min read
Rust Project for Web Services LogRocket Article

The best way to structure Rust web services

Learn how to structure Rust web services with clean architecture, Cargo workspaces, and modular crates for scalable, maintainable backends.

Jude Miracle
Oct 2, 2025 ⋅ 2 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