The appropriate programming language is required to deploy GUI programs used by small people for continuous updates. I'm currently developing with PyQt, but I'm having trouble implementing the update. So when I make my next program, I want to use a development language with a lot of community or documents, which one is good, Electron or PyQt? Or are there other options such as Java or C lang?
I am building a desktop application for Windows. I have worked with Electron earlier but it doesn't seem to work on a few Windows systems, also has no support for win7. Which language/framework should be chosen to cover a wide range of Windows versions including 7 or should I stick to Electron only?
Electron is an enormous amount of overhead. Just use C# with Visual Studio and you can build applications for every Windows version since 2002 or so. Developer experience is also way better than pretty much anything else. For a Windows-only app, there's no reason to use anything but Visual Studio.
Here are my suggestions.
C# + .NET Framework: It will work consistently on Windows 7, 8, 10, and even older versions.
Java with Swing Lib: Java is a mature and widely used programming language. The Java Runtime Environment is pre-installed on most Windows computers, so your application will likely "just work" for most users. You can use the Swing library for the UI.
You can avoid Electron by considering the fact that Performance issues, Bigger install size and More bugs and compatibility issues.
Kiosk App on Raspberry Pi
Hey subz390,
I think the Raspberry will fit your bill just fine. What I'm not really clear about is why you'd want to use Electron for the Kiosk App. Electron itself bundles a browser which then executes a web application - so in essence I do think you should be able to totally ditch Electron and just load up your web application in a browser (i.e. Firefox) in Kiosk mode. That could save you some complexity in your stack and maybe even some resources.
thanks for the feedback, it would be possible to do what I'm doing in a web page and bundle it in a PWA with `display: standalone` and then run the nodejs server as a separate process.
I use them in kiosks with lower performance demands. You’re going to get some stuttering doing animation.
Madan Traders has built a reputation for offering top-tier products at affordable prices. With a strong commitment to quality and customer care, they continue to serve customers with a diverse range of goods. Whether it’s wholesale or retail, <a href=”http://mayoworld.com/madan-traders-16898”>madan traders</a>is your go-to business partner.
We want to create a 3D web and desktop(Windows and macOS) application with a lot of functionalities. This is a 3D furniture customization application in which we give options to add, delete, scale, move, rotate objects. Something like a floor planner. We are also going to add AR and VR.
I am thinking about using Electron or Unity. Please recommend what should I choose for this purpose. Please consider that we have to develop for web and desktop (windows and mac) all platforms.
Take Unity for development as it is a full engine, with better tools to develop UI, use 3D assets, develop the integration with the API endpoints and deployment not only for Web (w/ WebAssembly) and Desktop, but also Mobile platforms (Android and iOS)
Hey! I am actually in internship and have an app to create for my structure. It will be an intern app which will allow crud dashboard actions with some data provided by the use of an API of one of the structure partner and make a correspondence to data contained in a private database. Since it's an intern app, I thought about Electron for a desktop app because I did a lot of web with Laravel and the structure goes more for the desktop app. But it will be my first occasion working with this tech.
Is Electron a good choice? Wich ORM should be more complete and adapted to this between Sequelize and TypeORM? (Database will be MySQL) Some charts will be displayed in the app. Is there a library (preferably without jQuery) that suits this stack?
Thank you !
Unless you're either using a local database or a backend server, you shouldn't choose either.
My recommendation would be having a NodeJS API on the backend that connects to the database and Electron connects to the API. Never give the database connection data to the end user, unless it's a planned move and it's to use on a local database.
I can recommend Sequelize because what I'm use the most on every project I need to create database connections. It supports TypeScript, and if you already have the database create you can use sequelize-auto to create the models, as easy as that.
I've only used Electron once and I liked it, but it's not a good comparison, since it doesn't offer any database access by default. I used React for the frontend part of the app, you can use whatever you want.
Thank you! That's what I finally decided. Your answer makes me sure that I am on the right track
If possible, avoid making an Electron App because the build process can be much more irritating and complex than making a web app. If you're able to use technologies like Firebase Firestore and a simple front-end to serve the data it will be hundred times faster than handling a full desktop app!
I would like to share my stack in Web/Mobile application Development for Mid Sized Applications.
Project-1 : Laravel + jQuery + Android Java + IOS Swift
Project-2 : Node.js + React + React Native + Electron.
This is my current Stack, Can you comment on my selection and add your thoughts if my choice is a perfect match? Thanks
I would say go for Node.js since you probably would only build a REST API that would talk to the frontend and some communication with the database.
On the other hand, Laravel is a much heavier framework that follows MVC pattern. Since you don't need the V in the MVC of Laravel. You can go for a straight Express that just handles the API request and return a response.
I'm currently doing some research to build a full cross-platform system that our personnel will use for various management and selling purposes, this is just a first step to migrate (and clean, lots of cleaning) a gigantic and obsolete system made in Java 7 with a nightmarish coupling between logic and view layers.
Since the system itself is considerably large, we are currently migrating the essential modules of its logic to an ExpressJS driven Restful API.
As a complementary project, I must find a way to share the highest possible amount of view code while achieving said cross-platform capacity.
My approach is the following:
While Angular is the common part, and considering that Ionic can work on any platform, i'm wondering what is the best way to achieve a non-conflicting integration of Electron.js to the very-commonly-used Angular+Ionic Stack for both Mobile and Web development?
I've stumbled with a quite good template build called Polyonic but I would love to hear more about the matter before taking such a long-lasting decision.
Hello Fernando, I think that most of your approach is correct but maybe you're forgetting that an Ionic and Angular (together or not) could be a PWA that solves your desktop problem. With a PWA you only have to build a mobile and web solution and remember that you can build a library of components shared between Angular and Ionic. I hope this helps.
Oh yes, absolutely, with your PWA approach i even get a simpler distribution process. In that case, the only question that remains is if i will have the same level of access to the host. (i do have to connect to some periferials)
Thank you very much!
Hi again,
here you have a good resume of PWA characteristics:
https://www.altexsoft.com/blog/engineering/progressive-web-apps/
If you need to use some native functionalities is possible PWA does not fit your necessities but I think it worths it to take a look.
Hi, I'm a web dev and am using Electron for a desktop app. Now I have to develop a mobile app with the following features:
Which tool is better for such a project?
Thanks in advance
Given your experience in electron I think the shortest hop is going to be React Native. Especially since half of the requirements are server-side. Google is doing a pretty great job bringing up Flutter and the tooling is pretty great. For me however, dart seemed like quicksand and not everything is in its final home. React Native is mature, and considering my cursory analysis of your experience and the low complexity of this project, you've got quite a lot of room to grow into Javascript Land. Ultimately, my recommendation is always "play with both, see what you like, and get to know the documentation and the community." Keep your head on a swivel and set aside time to peek greener pastures, but spend most of your time delving deeply into what you're already doing.
But yeah, go with React Native first, get bored of it, learn what the shortcomings are through experience and then see if something else is really more attractive or just a new shiny.
Well, I will personally recommend to go for React Native as I have worked in both of them. React native has big community and it is easy to opt as compared to Flutter. There no doubt about the fact that Flutter is a great framework for developing both Android/IOS apps. However, you should have some experience to go for the same. Both will require prior knowledge as for React Native you have to go through Javascript first with which you are already familiar and for Flutter you need to go through Dart. So being familiar with Javascript you should go for React Native. You can go expo which has lot of inbuilt functionalities for the React Native developers.
Thanks Varun for your suggestion! Just a little more help.
I saw Pepperoni Kit seems to accomplish a lot of the features I need to build.
Also I saw Expo, it seems help avoiding the installation both Xcode and Android Studio, but it's less "complete out of the box", am I right?
I'm curious to heard your opinion regarding this.
Sincerely,
CS
Hi Zensabbah,
thanks for asking. Expo is a great toolchain that is built around React Native and you can achieve almost every task using expo in react native. As far as Pepperoni Kit is concerned. It is new in market as compared to Expo toolchain. I do not have any experience with the same. However, I personally recommend Expo because you will able to get help as the community for expo is so big. So, you won't be having any issues in troubleshooting your stuff. In case you need any help regarding any stuff of expo then let me know.
