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:

CSS @container scroll-state: Replace JS scroll listeners now

CSS @container scroll-state lets you build sticky headers, snapping carousels, and scroll indicators without JavaScript. Here’s how to replace scroll listeners with clean, declarative state queries.

Jude Miracle
Feb 19, 2026 ⋅ 4 min read
Anti-libraryism 10 web APIs that replace modern JavaScript libraries

Anti-libraryism: 10 web APIs that replace modern JavaScript libraries

Explore 10 Web APIs that replace common JavaScript libraries and reduce npm dependencies, bundle size, and performance overhead.

Chizaram Ken
Feb 19, 2026 ⋅ 15 min read
podrocket 2-18

How developer platforms fail (and how yours won’t)

Russ Miles, a software development expert and educator, joins the show to unpack why “developer productivity” platforms so often disappoint.

Elizabeth Becz
Feb 18, 2026 ⋅ 52 sec read
the replay february 18

The Replay (2/18/26): Copilot workarounds, platform pitfalls, and more

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the February 18th issue.

Matt MacCormack
Feb 18, 2026 ⋅ 36 sec 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