diff --git a/locale-en-US/rn2025.yml b/locale-en-US/rn2025.yml index 5be1e65..d9b12c1 100644 --- a/locale-en-US/rn2025.yml +++ b/locale-en-US/rn2025.yml @@ -492,39 +492,41 @@ translations: - key: options.developer_background_contribution_to_lib.answer_no t: No - # Released React Native Apps Count - - key: developer_background.developer_background_releases_count - t: Released React Native apps count - - key: developer_background.developer_background_releases_count.question - t: How many React Native apps have you released publicly? - - key: developer_background.developer_background_releases_count.description - t: What is the number of publicly available apps (released to the app stores) you've worked on in 2025? - - - key: options.developer_background_releases_count.developer_background_releases_count_none - t: None - - key: options.developer_background_releases_count.developer_background_releases_count_one - t: "1" - - key: options.developer_background_releases_count.developer_background_releases_count_2_5 - t: 2-5 - - key: options.developer_background_releases_count.developer_background_releases_count_5_10 - t: 5-10 - - key: options.developer_background_releases_count.developer_background_releases_count_more_than_10 - t: More than 10 - - # Target OS - - key: developer_background.developer_background_os_target - t: Target mobile OS version - - key: developer_background.developer_background_os_target.question - t: What mobile OS versions do you target? - - - key: options.developer_background_os_target.developer_background_os_target_most_recent - t: The most recent versions (iOS 18+, Android 15+) - - key: options.developer_background_os_target.developer_background_os_target_reasonably_current - t: Reasonably current (iOS 17+, Android 13+) - - key: options.developer_background_os_target.developer_background_os_target_old - t: Old (iOS 14+, Android 9+) - - key: options.developer_background_os_target.developer_background_os_target_as_old_as_possible - t: As old as possible (iOS 8+, Android 5+) + # removed to shorten the survey, as it provided low-value data + # # Released React Native Apps Count + # - key: developer_background.developer_background_releases_count + # t: Released React Native apps count + # - key: developer_background.developer_background_releases_count.question + # t: How many React Native apps have you released publicly? + # - key: developer_background.developer_background_releases_count.description + # t: What is the number of publicly available apps (released to the app stores) you've worked on in 2025? + + # - key: options.developer_background_releases_count.developer_background_releases_count_none + # t: None + # - key: options.developer_background_releases_count.developer_background_releases_count_one + # t: "1" + # - key: options.developer_background_releases_count.developer_background_releases_count_2_5 + # t: 2-5 + # - key: options.developer_background_releases_count.developer_background_releases_count_5_10 + # t: 5-10 + # - key: options.developer_background_releases_count.developer_background_releases_count_more_than_10 + # t: More than 10 + + # removed to shorten the survey, as it provided low-value data + # # Target OS + # - key: developer_background.developer_background_os_target + # t: Target mobile OS version + # - key: developer_background.developer_background_os_target.question + # t: What mobile OS versions do you target? + + # - key: options.developer_background_os_target.developer_background_os_target_most_recent + # t: The most recent versions (iOS 18+, Android 15+) + # - key: options.developer_background_os_target.developer_background_os_target_reasonably_current + # t: Reasonably current (iOS 17+, Android 13+) + # - key: options.developer_background_os_target.developer_background_os_target_old + # t: Old (iOS 14+, Android 9+) + # - key: options.developer_background_os_target.developer_background_os_target_as_old_as_possible + # t: As old as possible (iOS 8+, Android 5+) # Industry Sectors Using React Native - key: developer_background.developer_background_industry_sector @@ -616,6 +618,16 @@ translations: t: Weather - key: options.developer_background_industry_sector.developer_background_industry_sector_video t: Video + - key: options.developer_background_industry_sector.developer_background_industry_sector_gambling + t: Gambling + - key: options.developer_background_industry_sector.developer_background_industry_sector_vr_ar + t: Virtual & Augmented Reality + - key: options.developer_background_industry_sector.developer_background_industry_sector_nonprofit_social_good + t: Nonprofit & Social Good + - key: options.developer_background_industry_sector.developer_background_industry_sector_legal_compliance + t: Legal & Compliance + - key: options.developer_background_industry_sector.developer_background_industry_sector_parenting_kids + t: Parenting and Kids ###################################################### ######### Results ######### @@ -651,100 +663,103 @@ translations: - key: platform_apis.platform_apis_pain_points.description t: What pain points have you encountered related to the APIs mentioned above? Specify the individual API if applicable. - ###################################################### - ######### STATE MANAGEMENT ######### - ###################################################### - - - key: sections.state_management.title - t: State management - - key: sections.state_management.description - t: What state management solutions do you use in your React Native apps? - - - key: state_management.intro_message - t: | - This next part of the survey is about sharing your experiences with various libraries that address the most fundamental challenges of React Native apps. - - You can indicate your familiarity with each library by choosing one of the following options: - - **Never heard of it**: this is the first time you've seen it - or you've heard of it but have no idea what it does. - - **Heard of it**: you've read or heard about it, but haven't actually used it yet. - - **Used it**: you've used it at least once, even just to play around with.. - - Also, if you want to tell us more about any of your choices, just click the Add a comment button! - - To provide additional context and facilitate understanding, each state management solution is accompanied by a code sample demonstrating a basic counter implementation, including state access and increment functionality. - - - key: state_management.state_management_others.question - t: Other state management solutions - - key: state_management.state_management_others.description - t: What other solutions not mentioned above have you used in your React Native apps? - - key: state_management.state_management_others - t: Other solutions - - key: state_management.state_management_pain_points - t: State management pain points - - key: state_management.state_management_pain_points.question - t: State management pain points - - - key: state_management.state_management_storage - t: On-device storage - - key: state_management.state_management_storage.question - t: What on-device storage solutions do you use in your React Native apps? - - - key: state_management.state_management_pain_points.description - t: - What pain points have you encountered with state management in your React Native projects? - If applicable, point out the specific solution and its problems. - - key: state_management.state_management_app_architecture_pattern_local_first - t: Local-first app architecture - - key: state_management.state_management_app_architecture_pattern_local_first.question - t: Are you familiar with local-first app architecture pattern? - - - # results - - - key: state_management.state_management_ratios - t: State management ratios over time - - key: state_management.state_management_experience - t: State management experience & sentiment - - - key: state_management.state_management_app_architecture_patterns_experience - t: Local-first app architecture - - key: state_management.state_management_app_architecture_patterns_experience.question - t: Are you familiar with local-first app architecture pattern? - - - key: state_management.state_management_app_architecture_patterns_ratios - t: Local-first app architecture - - ###################################################### - ######### DATA FETCHING ######### - ###################################################### - - key: sections.data_fetching.title - t: Data fetching - - key: sections.data_fetching.description - t: What data fetching solutions (accessing remote data) do you use in your React Native apps? - - - key: data_fetching.intro_message - t: | - To provide additional context and facilitate understanding, each data fetching solution is accompanied by a code sample demonstrating a basic usage. - - - key: data_fetching.data_fetching_others.question - t: Other data fetching solutions - - key: data_fetching.data_fetching_others.description - t: What other solutions not mentioned above have you used in your React Native apps? - - key: data_fetching.data_fetching_others - t: Other solutions - - key: data_fetching.data_fetching_pain_points - t: Data fetching pain points - - key: data_fetching.data_fetching_pain_points.question - t: Data fetching pain points - - key: data_fetching.data_fetching_pain_points.description - t: What pain points have you encountered with data fetching in your React Native projects? If applicable, point out the specific solution and its problems. - - # results - - - key: data_fetching.data_fetching_ratios - t: Data fetching ratios over time - - key: data_fetching.data_fetching_experience - t: Data fetching experience & sentiment + # removed to shorten the survey, as this segment duplicates content from the State of React survey + # ###################################################### + # ######### STATE MANAGEMENT ######### + # ###################################################### + + # - key: sections.state_management.title + # t: State management + # - key: sections.state_management.description + # t: What state management solutions do you use in your React Native apps? + + # - key: state_management.intro_message + # t: | + # This next part of the survey is about sharing your experiences with various libraries that address the most fundamental challenges of React Native apps. + + # You can indicate your familiarity with each library by choosing one of the following options: + # - **Never heard of it**: this is the first time you've seen it - or you've heard of it but have no idea what it does. + # - **Heard of it**: you've read or heard about it, but haven't actually used it yet. + # - **Used it**: you've used it at least once, even just to play around with.. + + # Also, if you want to tell us more about any of your choices, just click the Add a comment button! + + # To provide additional context and facilitate understanding, each state management solution is accompanied by a code sample demonstrating a basic counter implementation, including state access and increment functionality. + + # - key: state_management.state_management_others.question + # t: Other state management solutions + # - key: state_management.state_management_others.description + # t: What other solutions not mentioned above have you used in your React Native apps? + # - key: state_management.state_management_others + # t: Other solutions + # - key: state_management.state_management_pain_points + # t: State management pain points + # - key: state_management.state_management_pain_points.question + # t: State management pain points + + # - key: state_management.state_management_storage + # t: On-device storage + # - key: state_management.state_management_storage.question + # t: What on-device storage solutions do you use in your React Native apps? + + # - key: state_management.state_management_pain_points.description + # t: + # What pain points have you encountered with state management in your React Native projects? + # If applicable, point out the specific solution and its problems. + # moved to REACT NATIVE ARCHITECTURE section + # - key: state_management.state_management_app_architecture_pattern_local_first + # t: Local-first app architecture + # - key: state_management.state_management_app_architecture_pattern_local_first.question + # t: Are you familiar with local-first app architecture pattern? + + + # # results + + # - key: state_management.state_management_ratios + # t: State management ratios over time + # - key: state_management.state_management_experience + # t: State management experience & sentiment + + # - key: state_management.state_management_app_architecture_patterns_experience + # t: Local-first app architecture + # - key: state_management.state_management_app_architecture_patterns_experience.question + # t: Are you familiar with local-first app architecture pattern? + + # - key: state_management.state_management_app_architecture_patterns_ratios + # t: Local-first app architecture + + # removed to shorten the survey, as this segment duplicates content from the State of React survey + # ###################################################### + # ######### DATA FETCHING ######### + # ###################################################### + # - key: sections.data_fetching.title + # t: Data fetching + # - key: sections.data_fetching.description + # t: What data fetching solutions (accessing remote data) do you use in your React Native apps? + + # - key: data_fetching.intro_message + # t: | + # To provide additional context and facilitate understanding, each data fetching solution is accompanied by a code sample demonstrating a basic usage. + + # - key: data_fetching.data_fetching_others.question + # t: Other data fetching solutions + # - key: data_fetching.data_fetching_others.description + # t: What other solutions not mentioned above have you used in your React Native apps? + # - key: data_fetching.data_fetching_others + # t: Other solutions + # - key: data_fetching.data_fetching_pain_points + # t: Data fetching pain points + # - key: data_fetching.data_fetching_pain_points.question + # t: Data fetching pain points + # - key: data_fetching.data_fetching_pain_points.description + # t: What pain points have you encountered with data fetching in your React Native projects? If applicable, point out the specific solution and its problems. + + # # results + + # - key: data_fetching.data_fetching_ratios + # t: Data fetching ratios over time + # - key: data_fetching.data_fetching_experience + # t: Data fetching experience & sentiment ###################################################### ######### NAVIGATION ######### @@ -765,10 +780,11 @@ translations: t: Navigation pain points - key: navigation.navigation_pain_points.description t: What pain points have you encountered with navigation in your React Native projects? If applicable, point out the specific solution and its problems. - - key: navigation.navigation_app_architecture_pattern_file_based_routing - t: Filed-based routing pattern - - key: navigation.navigation_app_architecture_pattern_file_based_routing.question - t: Are you familiar with file-based routing architecture pattern? + # moved to REACT NATIVE ARCHITECTURE section + # - key: navigation.navigation_app_architecture_pattern_file_based_routing + # t: Filed-based routing pattern + # - key: navigation.navigation_app_architecture_pattern_file_based_routing.question + # t: Are you familiar with file-based routing architecture pattern? # results @@ -777,13 +793,14 @@ translations: - key: navigation.navigation_experience t: Navigation experience & sentiment - - key: navigation.navigation_app_architecture_patterns_experience - t: Filed-based routing pattern - - key: navigation.navigation_app_architecture_patterns_experience.question - t: Are you familiar with file-based routing architecture pattern? + # moved to REACT NATIVE ARCHITECTURE section + # - key: navigation.navigation_app_architecture_patterns_experience + # t: Filed-based routing pattern + # - key: navigation.navigation_app_architecture_patterns_experience.question + # t: Are you familiar with file-based routing architecture pattern? - - key: navigation.navigation_app_architecture_patterns_ratios - t: Filed-based routing pattern + # - key: navigation.navigation_app_architecture_patterns_ratios + # t: Filed-based routing pattern ###################################################### ######### STYLING ######### @@ -845,9 +862,9 @@ translations: # Results - key: animations.animations_ratios t: Animations ratios over time - - key: animations.animations_ratios.note + - key: animations.animations_ratios.results_note t: > - The beta version of Reanimated 4 has been released. It brings long-awaited support for CSS Animations and Transitions, making it easier to create high-performance animations. + The stable version of Reanimated 4 has been released. It brings long-awaited support for CSS Animations and Transitions, making it easier to create high-performance animations. The new features build on the existing worklet-based APIs, offering an intuitive approach while staying compatible with Reanimated 3. If your app uses the New Architecture, you can explore the beta version and see how it streamlines your animation workflow. @@ -879,12 +896,13 @@ translations: - key: component_libraries.component_libraries_data_visualisation.question t: What data visualisation solutions do you use in your React Native apps? - - key: component_libraries.component_libraries_other_libraries - t: Other popular component(s) libraries - - key: component_libraries.component_libraries_other_libraries.question - t: What other popular component(s) libraries do you use in your React Native apps? - - key: component_libraries.component_libraries_other_libraries.description - t: Other popular libraries that offer ready-made components for various APIs and mechanisms not yet covered in the survey. + # removed to shorten the survey, as it provided low-value data + # - key: component_libraries.component_libraries_other_libraries + # t: Other popular component(s) libraries + # - key: component_libraries.component_libraries_other_libraries.question + # t: What other popular component(s) libraries do you use in your React Native apps? + # - key: component_libraries.component_libraries_other_libraries.description + # t: Other popular libraries that offer ready-made components for various APIs and mechanisms not yet covered in the survey. # results - key: component_libraries.component_libraries_ratios @@ -914,38 +932,39 @@ translations: - key: debugging_and_profiling.debugging_profiling_others.description t: What other solutions not mentioned above have you used in your React Native apps? - - key: debugging_and_profiling.debugging_profiling_intent - t: Debugging intent - - key: debugging_and_profiling.debugging_profiling_intent.question - t: Debugging intent - - key: debugging_and_profiling.debugging_profiling_intent.description - t: What do you want to do when debugging your app? - - key: options.debugging_profiling_intent.debugging_profiling_intent_view_app_logs - t: View app logs - - key: options.debugging_profiling_intent.debugging_profiling_intent_view_app_logs.description - t: Viewing and inspecting app logs - - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_layout_and_styles - t: Inspect layout and styles - - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_layout_and_styles.description - t: Inspecting the element tree, highlighting elements in the UI, changing styles in realtime - - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_code_behavior - t: Inspect code behaviour - - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_code_behavior.description - t: Step-through breakpoint debugging, evaluating expressions in the JavaScript console - - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_react_behavior - t: Understand React behaviour - - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_react_behavior.description - t: Inspecting React state, analyzing performance issues - e.g. re-renders - - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_network_requests - t: Inspect network requests - - key: options.debugging_profiling_intent.debugging_profiling_intent_profile_the_app - t: Profile your app - - key: options.debugging_profiling_intent.debugging_profiling_intent_profile_the_app.description - t: Monitoring resource usage (Memory, CPU), analyzing execution time of functions - - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_3rd_party_libraries - t: Understand the behaviour of third party JS libraries - - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_3rd_party_libraries.description - t: Use specific dev plugins for third party libraries or use cases (e.g. Redux DevTools). Available today via Expo DevTools Plugins. + # removed to shorten the survey, as it provided low-value data + # - key: debugging_and_profiling.debugging_profiling_intent + # t: Debugging intent + # - key: debugging_and_profiling.debugging_profiling_intent.question + # t: Debugging intent + # - key: debugging_and_profiling.debugging_profiling_intent.description + # t: What do you want to do when debugging your app? + # - key: options.debugging_profiling_intent.debugging_profiling_intent_view_app_logs + # t: View app logs + # - key: options.debugging_profiling_intent.debugging_profiling_intent_view_app_logs.description + # t: Viewing and inspecting app logs + # - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_layout_and_styles + # t: Inspect layout and styles + # - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_layout_and_styles.description + # t: Inspecting the element tree, highlighting elements in the UI, changing styles in realtime + # - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_code_behavior + # t: Inspect code behaviour + # - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_code_behavior.description + # t: Step-through breakpoint debugging, evaluating expressions in the JavaScript console + # - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_react_behavior + # t: Understand React behaviour + # - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_react_behavior.description + # t: Inspecting React state, analyzing performance issues - e.g. re-renders + # - key: options.debugging_profiling_intent.debugging_profiling_intent_inspect_network_requests + # t: Inspect network requests + # - key: options.debugging_profiling_intent.debugging_profiling_intent_profile_the_app + # t: Profile your app + # - key: options.debugging_profiling_intent.debugging_profiling_intent_profile_the_app.description + # t: Monitoring resource usage (Memory, CPU), analyzing execution time of functions + # - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_3rd_party_libraries + # t: Understand the behaviour of third party JS libraries + # - key: options.debugging_profiling_intent.debugging_profiling_intent_understand_3rd_party_libraries.description + # t: Use specific dev plugins for third party libraries or use cases (e.g. Redux DevTools). Available today via Expo DevTools Plugins. - key: debugging_and_profiling.debugging_profiling_pain_points t: Debugging and profiling pain points @@ -959,7 +978,7 @@ translations: - key: debugging_and_profiling.debugging_and_profiling_experience t: Debugging and profiling experience & sentiment - - key: debugging_and_profiling.debugging_profiling_pain_points.note + - key: debugging_and_profiling.debugging_profiling_pain_points.results_note t: | Radon IDE is a new VSCode and Cursor extension that simplifies debugging and streamlines React Native development. It turns your editor into a fully-fledged IDE, eliminating context switching and automatically pausing runtime errors. Radon IDE allows you to add breakpoints in VSCode to easily debug your React Native app. Its click-to-inspect feature makes it possible to quickly jump directly from preview to a file where your component is defined, while the integrated log panel helps to pinpoint issues effortlessly by showing logs directly in the VSCode console. @@ -974,6 +993,11 @@ translations: - key: sections.testing_and_monitoring.description t: What tools do you use to test and monitor your React Native apps? + - key: testing_and_monitoring.testing_and_monitoring_testing + t: Testing + - key: testing_and_monitoring.testing_and_monitoring_testing.question + t: What testing solutions do you use in your React Native apps? + - key: testing_and_monitoring.testing_and_monitoring_testing_others t: Other testing solutions - key: testing_and_monitoring.testing_and_monitoring_testing_others.question @@ -1016,14 +1040,16 @@ translations: t: React Native version - key: react_native_architecture.react_native_architecture_version.question t: Which React Native version do you use mainly? - - key: options.react_native_architecture_version.react_native_architecture_version_0_69_or_lower - t: "0.69 or lower" - - key: options.react_native_architecture_version.react_native_architecture_version_0_70 - t: "0.70" - - key: options.react_native_architecture_version.react_native_architecture_version_0_71 - t: "0.71" - - key: options.react_native_architecture_version.react_native_architecture_version_0_72 - t: "0.72" + # - key: options.react_native_architecture_version.react_native_architecture_version_0_69_or_lower + # t: "0.69 or lower" + # - key: options.react_native_architecture_version.react_native_architecture_version_0_70 + # t: "0.70" + # - key: options.react_native_architecture_version.react_native_architecture_version_0_71 + # t: "0.71" + # - key: options.react_native_architecture_version.react_native_architecture_version_0_72 + # t: "0.72" + - key: options.react_native_architecture_version.react_native_architecture_version_0_72_or_lower + t: "0.72 or lower" - key: options.react_native_architecture_version.react_native_architecture_version_0_73 t: "0.73" - key: options.react_native_architecture_version.react_native_architecture_version_0_74 @@ -1032,6 +1058,16 @@ translations: t: "0.75" - key: options.react_native_architecture_version.react_native_architecture_version_0_76 t: "0.76" + - key: options.react_native_architecture_version.react_native_architecture_version_0_77 + t: "0.77" + - key: options.react_native_architecture_version.react_native_architecture_version_0_78 + t: "0.78" + - key: options.react_native_architecture_version.react_native_architecture_version_0_79 + t: "0.79" + - key: options.react_native_architecture_version.react_native_architecture_version_0_80 + t: "0.80" + - key: options.react_native_architecture_version.react_native_architecture_version_0_81 + t: "0.81" - key: options.react_native_architecture_version.react_native_architecture_version_next t: next / rc (release candidate) - key: options.react_native_architecture_version.react_native_architecture_version_nightly @@ -1043,12 +1079,6 @@ translations: t: React Native version upgrading strategy - key: react_native_architecture.react_native_architecture_strategies.description t: What is your main strategy for upgrading React Native to a new versions? - - key: react_native_architecture.react_native_architecture_strategies.note - t: | - React Native 0.76 and the New Architecture are enabled by default, but navigating them can be challenging. On the Software Mansion blog, you can find insights on handling common New Architecture challenges like view flattening, view recycling, custom shadow nodes, and more. - Read part 1 - Read part 2 - P.S. If you need help adopting the new architecture in your app, contact us. We have already ported 25+ libraries, migrated several apps for clients, and contributed 30+ fixes to React Native core for issues related to the new arch. - key: options.react_native_architecture_strategies.react_native_architecture_strategies_stay_latest t: Stay on the latest version - key: options.react_native_architecture_strategies.react_native_architecture_strategies_upgrade_occasionally @@ -1062,6 +1092,25 @@ translations: - key: options.react_native_architecture_strategies.react_native_architecture_strategies_other t: Other React Native version upgrading strategy + - key: react_native_architecture.react_native_architecture_new_architecture_migration + t: New Architecture migration + - key: react_native_architecture.react_native_architecture_new_architecture_migration.question + t: Have you migrated to React Native's New Architecture? + - key: options.react_native_architecture_new_architecture_migration.react_native_architecture_new_architecture_migration_yes + t: Yes + - key: options.react_native_architecture_new_architecture_migration.react_native_architecture_new_architecture_migration_no + t: No + - key: options.react_native_architecture_new_architecture_migration.react_native_architecture_new_architecture_migration_planned + t: Planned for future + - key: options.react_native_architecture_new_architecture_migration.react_native_architecture_new_arch_migration_not_planned + t: Not planned + - key: react_native_architecture.react_native_architecture_new_architecture_migration.results_note + t: | + React Native 0.76+ defaults to the New Architecture, which may be challenging to navigate. On the Software Mansion blog, you can find insights on handling common New Architecture challenges like view flattening, view recycling, custom shadow nodes, and more. + Read part 1 + Read part 2 + P.S. If you need help adopting the new architecture in your app, contact us. We have already ported 25+ libraries, migrated several apps for clients, and contributed 30+ fixes to React Native core for issues related to the new arch. + - key: react_native_features.brownfield t: Do you integrate React Native with applications written using other technology? - key: react_native_features.ota_updates @@ -1073,7 +1122,7 @@ translations: t: Greenfield vs brownfield - key: react_native_architecture.react_native_architecture_brownfield.question t: What type of React Native project are you working on? - - key: react_native_architecture.react_native_architecture_brownfield.note + - key: react_native_architecture.react_native_architecture_brownfield.results_note t: | Brownfield integration comes with its challenges. If you are looking for resources on how to successfully integrate React Native into an iOS or Android app, Software Mansion has put together a miniguide to walk you through the process: Read part 1 (iOS) @@ -1100,6 +1149,20 @@ translations: - key: options.react_native_architecture_ota_updates.react_native_architecture_ota_updates_self_hosted t: Self-hosted + - key: react_native_architecture.react_native_architecture_nitro_modules.description + t: Have you started using Nitro Modules in your React Native projects? + - key: options.react_native_architecture_nitro_modules.react_native_architecture_nitro_modules_yes + t: Yes, they are fully implemented + - key: options.react_native_architecture_nitro_modules.react_native_architecture_nitro_modules_partial + t: Partially implemented + - key: options.react_native_architecture_nitro_modules.react_native_architecture_nitro_modules_no + t: No + + - key: react_native_architecture.react_native_architecture_framework_usage + t: React Native frameworks + - key: react_native_architecture.react_native_architecture_framework_usage.question + t: What React Native frameworks have you used in the last year? + - key: react_native_architecture.react_native_architecture_mobile_web_code_sharing t: Mobile-Web code sharing - key: react_native_architecture.react_native_architecture_mobile_web_code_sharing.question @@ -1112,6 +1175,16 @@ translations: - key: options.react_native_architecture_mobile_web_code_sharing.react_native_architecture_mobile_web_code_sharing_independent_projects t: No code sharing. Independent project for the web counterpart of my application. + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_file_based_routing + t: Filed-based routing pattern + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_file_based_routing.question + t: Are you familiar with file-based routing architecture pattern? + + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_local_first + t: Local-first app architecture + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_local_first.question + t: Are you familiar with local-first app architecture pattern? + # results - key: react_native_architecture.react_native_architecture_ratios @@ -1119,6 +1192,27 @@ translations: - key: react_native_architecture.react_native_architecture_experience t: React Native architecture experience & sentiment + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_file_based_routing_experience + t: Filed-based routing pattern + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_file_based_routing_experience.question + t: Are you familiar with file-based routing architecture pattern? + + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_file_based_routing_ratios + t: Filed-based routing pattern + + - key: react_native_architecture.react_native_architecture_app_architecture_patterns_experience + t: Local-first app architecture + - key: react_native_architecture.react_native_architecture_app_architecture_patterns_experience.question + t: Are you familiar with local-first app architecture pattern? + + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_local_first_ratios + t: Local-first app architecture + + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_local_first_experience + t: Local-first app architecture + - key: react_native_architecture.react_native_architecture_app_architecture_pattern_local_first_experience.question + t: Are you familiar with local-first app architecture pattern? + ###################################################### ######### BUILD AND PUBLISH ######### ###################################################### @@ -1237,26 +1331,27 @@ translations: - key: dev_tools.dev_tools_experience t: Dev tools experience & sentiment - ###################################################### - ######### React Native Alternatives ######### - ###################################################### + # removed to shorten the survey, as it provided low-value data + # ###################################################### + # ######### React Native Alternatives ######### + # ###################################################### - - key: sections.react_native_alternatives.title - t: Other cross-platform frameworks - - key: sections.react_native_alternatives.description - t: What other cross-platform app development solutions besides React Native are you familiar with? + # - key: sections.react_native_alternatives.title + # t: Other cross-platform frameworks + # - key: sections.react_native_alternatives.description + # t: What other cross-platform app development solutions besides React Native are you familiar with? - - key: react_native_alternatives.react_native_alternatives_other - t: Other cross-platform frameworks - - key: react_native_alternatives.react_native_alternatives_other.description - t: What cross-platform frameworks not mentioned above (besides React Native) are you familiar with? + # - key: react_native_alternatives.react_native_alternatives_other + # t: Other cross-platform frameworks + # - key: react_native_alternatives.react_native_alternatives_other.description + # t: What cross-platform frameworks not mentioned above (besides React Native) are you familiar with? - # results + # # results - - key: react_native_alternatives.react_native_alternatives_ratios - t: Cross-platform frameworks ratios over time - - key: react_native_alternatives.react_native_alternatives_experience - t: Cross-platform frameworks experience & sentiment + # - key: react_native_alternatives.react_native_alternatives_ratios + # t: Cross-platform frameworks ratios over time + # - key: react_native_alternatives.react_native_alternatives_experience + # t: Cross-platform frameworks experience & sentiment ###################################################### @@ -1337,11 +1432,13 @@ translations: # results - - key: resources.resources_experience - t: React Native Directory + # removed as it provided low value data + # - key: resources.resources_experience + # t: React Native Directory - - key: resources.resources_ratios - t: React Native Directory + # removed as it provided low value data + # - key: resources.resources_ratios + # t: React Native Directory ###################################################### # Opinions # @@ -1528,10 +1625,10 @@ translations: t: Years of Experience - key: user_info.years_of_experience.question t: How long have you been working as a programmer or studying programming? - - key: user_info.years_of_experience.note + - key: user_info.years_of_experience.results_note t: | App.js Conf is the biggest React Native and Expo-focused conference, where you can meet the creators and contributors to React Native and Expo, share ideas, connect with the community, and shape the future of app development. - This year’s edition will take place on 28-30 May in Kraków, Poland. It’s the perfect opportunity to level up your React Native skills through hands-on workshops on Reanimated, brownfield integrations, 3d graphics, performance optimization, and more. + This year’s edition will take place on 27-29 May in Kraków, Poland. It’s the perfect opportunity to level up your React Native skills through hands-on workshops on Reanimated, brownfield integrations, 3d graphics, performance optimization, and more. Visit the website to learn the details and grab your tickets! - key: user_info.years_of_experience_rn