StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Frameworks
  5. React Native Desktop vs Symfony

React Native Desktop vs Symfony

OverviewDecisionsComparisonAlternatives

Overview

Symfony
Symfony
Stacks8.5K
Followers6.2K
Votes1.1K
GitHub Stars30.7K
Forks9.7K
React Native Desktop
React Native Desktop
Stacks15
Followers203
Votes11

React Native Desktop vs Symfony: What are the differences?

  1. Runtime Environment: React Native Desktop allows developers to create cross-platform desktop applications using React and Javascript. On the other hand, Symfony is a PHP framework that is used to build web applications. The key difference lies in their runtime environments, with React Native Desktop targeting desktop applications and Symfony focusing on web-based projects.

  2. Language: React Native Desktop is primarily based on Javascript, making it suitable for developers with experience in web development technologies. In contrast, Symfony is built on PHP, offering a robust set of tools and libraries tailored for server-side programming. The choice of language between Javascript and PHP plays a significant role in selecting the appropriate framework for a given project.

  3. User Interface Design: React Native Desktop leverages the React framework to create dynamic and responsive user interfaces, allowing developers to reuse code components across different platforms. Symfony, on the other hand, follows a more traditional approach to web application design, offering templating engines like Twig for building user interfaces. The approach to user interface design differs significantly between React Native Desktop and Symfony.

  4. Deployment Options: React Native Desktop applications can be deployed across different desktop platforms like Windows, macOS, and Linux, providing a wide reach for developers targeting desktop users. In contrast, Symfony applications are typically deployed on web servers running PHP, limiting the deployment options to web-based environments. The difference in deployment options between React Native Desktop and Symfony influences the target platform for the applications.

  5. Community Support: React Native Desktop has a growing community of developers contributing to the ecosystem, providing resources, libraries, and updates to enhance the development experience. Symfony, being a mature PHP framework, has a strong community backing with a plethora of resources and extensions available for developers. The level of community support and resources differs between React Native Desktop and Symfony, affecting the development process and access to additional functionalities.

  6. Performance Considerations: React Native Desktop applications utilize native platform APIs to access device features, potentially offering better performance compared to web applications. Symfony, being a server-side PHP framework, relies on server resources for processing requests and rendering responses. The performance considerations differ between React Native Desktop, which focuses on leveraging native capabilities for efficiency, and Symfony, which excels in server-side processing capabilities.

In Summary, the key differences between React Native Desktop and Symfony lie in their runtime environments, languages, user interface design approaches, deployment options, community support, and performance considerations.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Symfony, React Native Desktop

Fabian
Fabian

May 5, 2020

Needs adviceonGraphQLGraphQLC++C++SymfonySymfony

I'm about to begin working on an API, for which I plan to add GraphQL connectivity for processing data. The data processed will mainly be audio files being downloaded/uploaded with some user messaging & authentication.

I don't mind the difficulty in any service since I've used C++ (for data structures & algorithms at least) and would also say I am patient and can learn fairly quickly. My main concerns would be their performance, libraries/community, and job marketability.

Why I'm stuck between these three...

Symfony: I've programmed in PHP for back-end in a previous internship and may do so again in a few months.

Node.js: It's newer than PHP, and it's JavaScript where my front-end stack will be React and (likely) React Native.

Golang: It's newer than PHP, I've heard of its good performance, and it would be nice to learn a new (growing) language.

2.4M views2.4M
Comments
Semih
Semih

Software Engineering Manager

Oct 1, 2020

Needs adviceonJavaScriptJavaScriptHTML5HTML5.NET.NET

Hi,

We are planning to develop a brand new UX for an already existing desktop software. The previous version is developed on C#.NET with Winforms & WPF. Our plan is to use JavaScript/HTML5 based frontend technologies for the new software. For some components, we are highly dependent on .NET/ .NET Core because the JS-based versions are not mature enough.

What would you choose for a desktop-based Engineering Software that supports multi-OS and has rich UI capabilities considering the .NET dependencies?

Thanks in advance,

Semih

57.9k views57.9k
Comments
Filippo
Filippo

Aug 27, 2020

Review

In my humble opinion the best available php platform is "API Platform". I have tried a lot of backend frameworks in the last 10 years, and that is one of the best, at least in the PHP ecosystem. It's based on Symfony, it supports plenty of features like Swagger docs, Rest API, GraphQL. You can plugin React Admin to have a full admin in no time. But the best part in my opinion it's how you can easily extend the backend taking advantage of the ORM Doctrine (which is one of the most mature available across all technologies) and all the plugins of Symfony. The fact that the Doctrine entities are in automatic relation and they can be exposed as GraphQL it's a big win if you have a complex database. It is also possible to reverse engineering an existing database and create automatically all the entities, admin, restapi, graphql endpoints ... welcome to the future :)

51 views51
Comments

Detailed Comparison

Symfony
Symfony
React Native Desktop
React Native Desktop

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Build OS X desktop apps using React Native.

Statistics
GitHub Stars
30.7K
GitHub Stars
-
GitHub Forks
9.7K
GitHub Forks
-
Stacks
8.5K
Stacks
15
Followers
6.2K
Followers
203
Votes
1.1K
Votes
11
Pros & Cons
Pros
  • 177
    Open source
  • 149
    Php
  • 130
    Community
  • 129
    Dependency injection
  • 122
    Professional
Cons
  • 10
    Too many dependency
  • 8
    Lot of config files
  • 4
    YMAL
  • 3
    Feature creep
  • 1
    Bloated
Pros
  • 3
    Pretty awesome
  • 2
    Does not include any browser
  • 2
    Memory usage reduced
  • 2
    Is native app
  • 1
    Open source
Cons
  • 0
    Memory usage reduced
Integrations
CakePHP
CakePHP
PHP
PHP
ReactPHP
ReactPHP
React Native
React Native

What are some alternatives to Symfony, React Native Desktop?

Node.js

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Spring

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Phoenix Framework

Phoenix Framework

Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase