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:

profit center vs. cost center: How company structure affects engineering

Profit center vs. cost center: How company structure affects engineering

Examine the difference between profit vs. cost center organizations, and the pros and cons these bring for the engineering team.

Marie Starck
May 15, 2025 ⋅ 4 min read
How to pass a TypeScript function as a parameter

How to pass a TypeScript function as a parameter

Explore how to pass functions and structured objects as parameters in TypeScript, including use cases, syntax, and practical scenarios.

Kealan Parr
May 15, 2025 ⋅ 10 min read
API Docs Made Easy With Docusaurus

Create fast, modern API docs using Docusaurus

Why API documentation matters, recent trends in the space, and how to build great docs from scratch using Docusaurus, step by step.

Frank Joseph
May 15, 2025 ⋅ 6 min read
A checklist for mastering Expo SDK 53

A checklist for mastering Expo SDK 53

Get up to speed on Expo SDK 53, which brings with it a wealth of new and improved updates for the React Native ecosystem.

Andrew Baisden
May 15, 2025 ⋅ 17 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