HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
react
react-native
C++2015–2025
react / react-native

react-native

A framework for building native applications using React

129Distinct people
157Mentions
1Explicit recommenders
126.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A framework for building native applications using React

GitHub

Where it is used

  • Discord — “How Discord achieves native iOS performance with React Native” Source

What people are saying

i am sad to say that lists and tables are totally unsolved problems, look how many issues there are in react's virtualized list[1] (just an example, not picking on react) but i…

throwaway71271 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year157 dated mentions

Observed mentions: 2015-03-26 17:08:54 UTC to 2025-09-24 20:13:39 UTC.

0102030402015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 33 mentions; 13 submissions, 20 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 18 mentions; 8 submissions, 10 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 42 mentions; 8 submissions, 34 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 16 mentions; 3 submissions, 13 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 21 mentions; 3 submissions, 18 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 4 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC331320
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC18810
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC42834
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC16313
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC624
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC21318
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC633
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC642
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC413
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

157 sources
You can find std::string_view (C++17) in Google's WebGPU implementation [1], static_assert (C++17) in Protobufs [2], <bit> (C++20) in React Native [3], and std::format (C++20) in Cuda Core Compute [4]. So the big names in tech aren't afraid to add -std=c++20 to their build scripts. On the other hand, C++23 features aren't as common yet, but it's still very fresh and MSVC support is WIP. [1] https://github.com/google/dawn/blob/40cf7fd7bc06f871fc5e4823... [2] https://github.com/protocolbuffers/protobuf/blob/c964e143d97... [3] https://github.com/facebook/react-native/blob/77b3a8bdd6164b... [4] https://github.com/NVIDIA/cccl/blob/07fef970a33ae120c8ff2a9e...
In What's new in C++26 (part 1)
I'm neither flutter nor react native developer just native mobile dev but evaluating both techs so don't have stake in the game right now. Just showing to other so they can make their own judgement: Flutter monthly pulse: https://github.com/flutter/flutter/pulse/monthly "Excluding merges, 83 authors have pushed 451 commits to master and 461 commits to all branches" but: 1st engine-flutter-autoroll (bot with revisions autoroll): 185 commits 2nd zanderso (google employee): 25 commits 3rd ValentilVignal (contributor): 14 commits in top 15 contributors for flutter you have also other bots such as: fluttergithubbot, auto-submit[bot], flutter-pub-roller-bot, dependabot[bot] React Native monthly pulse: https://github.com/facebook/react-native/pulse/monthly "Excluding merges, 84 authors have pushed 437 commits to main and 575 commits to all bra
Read the rest
nches" 1st cipolleschi (meta employee): 92 commits 2nd cortinico (meta employee): 83 commits 3rd NickGerleman (contributor): 45 commits no bots in top 15 contributors Also keep in mind React Native is based on React repo project. On top of that you have a lot of work by community in: - expo https://github.com/expo/expo - react native reanimated https://github.com/software-mansion/react-native-reanimated - react navigation https://github.com/react-navigation/react-navigation - react native skia https://github.com/Shopify/react-native-skia All of those packages are highly maintained and are pretty used in all RN projects and considered standard.
In Show HN: Rust GUI Library via Flutter
I keep seeing this coming up and I have no idea where it’s coming from like it’s some self reinforcing feedback loop based on just utter bullshit. If I am remembering correctly the headcount on the Futter team literally changed by a single person. Here are some actual real life numbers you can use if you want to gauge the health of the two projects: 1. https://github.com/facebook/react-native/pulse 2. https://github.com/flutter/flutter/pulse Specifically Flutter’s 108 merged pull requests to React Native’s 1 and Flutter’s 330 closed issues to React Native’s 18. Also note that this doesn’t even include their rendering engine which had another 90+ closed pull requests https://github.com/flutter/engine/pulse The truth of the matter is that Flutter is actually is far better shape both from a technical and open source perspective.
In Show HN: Rust GUI Library via Flutter
I meant both Animated APIs - neither is able to perform synchronous layouts - because react native is not able to do that. That’s the issue that’s stopping the page sheet controllers being added to react native. I actually was helping getting this added, but we never managed to get the layout issues fixed - https://github.com/facebook/react-native/pull/34834 The measure function you mention isn’t co-ordinated to the layout, so you could read it while a layout is pending and get old data - but that doesn't really matter for most cases
In Expo – Open-source platform for making universal apps for Android, iOS, and web
>most accessibility support is rooted in best practices for every user. This isn't quite true, when you get into things like using aria attributes. I definitely wouldn't put it at 99.99%. And I think a lot of vendors of accessibility software get to skate where others would have their feet held to the fire. They could be doing more to make their software easier to use and for developers to make it accessible. I used to work as a contractor for the CDC, so I have experience in web development that is held to a higher accessibility standard (we had an actual real person who would verify our work and certify that it was accessible.) Some things that come to mind are color contrast ratios where you have to pass different levels (AA vs. AAA) https://webaim.org/resources/contrastchecker/ And being able to navigate a site with a keyboard, or ann
Read the rest
ounce when sections change. That stuff isn't automatic. It might be baked into whatever framework you're using, but those frameworks have bugs too. Here's an example I ran into with React Native, and it's still not clear if they ever fixed it or if it just got closed as stale: https://github.com/facebook/react-native/issues/27989
In Don’t open the details in a modal window, have it be a separate page
Along what metrics is the question. As far as I know it’s: - less popular (https://gist.github.com/tkrotoff/93f5278a4e8df7e5f6928eff986...) - worse performance - much more frustrating developer experience (inherently subjective but not a particularly controversial opinion) - less supported / actively developed (some very core parts of the RN ecosystem got punted to “community supported” where they basically died in place) but also worth comparing GitHub activity for Flutter https://github.com/flutter/flutter/pulse/monthly and RN https://github.com/facebook/react-native/pulse/monthly I think Flutter is a much better long term bet despite the fact that it’s a much newer project.
In React Native 0.69
ratio11·Jun 7, 2022Submission

Tell HN: Apple rejecting cross platform apps (React Native, Flutter, Capacitor)

...Not on purpose, probably. This started immediately after their WWDC service downtime. "Dear Developer, We identified one or more issues with a recent delivery for your app, "App" 1.0.0 (2). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in App: authorizationCode, createRequest, estimatedProgress, identityToken, initWithFrame:configuration:, isMainFrame, isPassthrough, navigationType, onSuccess:, removeValuesForKeys:completion:, setNavigationDelegate:, setProcessPool:, setRequestedOperation:, setRequestedScopes:, targetFrame, userContentController, viewManager, websiteDataStore. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In
Read the rest
addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Best regards, The App Store Team" https://github.com/facebook/react-native/issues/31507 https://github.com/flutter/flutter/issues/105471 https://github.com/ionic-team/capacitor/issues/5661 https://developer.apple.com/forums/thread/127678
90 points · Open discussion

Showing the 15 most recent of 157 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.