>> "You’ll be able to package your application and distribute it like any other desktop application, complete with an installer and auto-updates."
Yep, Electron is excellent. However, Electron is built on top of V8 and V8 does not provide a way to protect the JS source. More than the technical problem this becomes legal issue for businesses that want to develop applications/tools rapidly with electron.
Cons of other options that I know:
1. Obfuscation is not ideal to hide the source from competitors.
2. Writing nodejs modules in C++ is not so easy way. Once could prefer to develop entire app with C++ than the learning curve associated with node modules in C++.
3. V8 snapshots maybe a way to go with nw.js. But doesn't work great and it is hard to isolate issues while packaging.
4. EncloseJS looks promising. There is no company behind it and no guarantee it will be supported. (I personally have been following up with issues in packaging an open source app with encloseJS. No luck so far with support.
5. nexe is interesting. But not easy and no clear way to work with it.
What are your opinions? Any alternatives?
P.S: I'm framing a base with Java (most likely C++ too) to develop an app that runs on client machine but on browsers. Performance and source protection are my goals. Might open source its architecture eventually.
Over couple of weekends I made my second android app (rectifying the mistakes/pitfalls I made from the first one ;) ) that helps one with deep breathing exercise to relieve stress and anxiety.
The idea is simple. When we are stressed we often tend to take shallow breathes and unknowingly it does worst. What we want at that moment is deep abdominal breathing to gain back focus on the stressful tasks.
The app starts with a countdown timer and breathes with you and maintains the constant phase of inhale and exhaling. Additionally, to spice up the app allows you to play an ambient music to reduce the distraction.
I started learning android development for about a month now and I feel really comfortable now.
Made Classy, it's my first hobby app.
Classy is an ambient sound player which can help you drown out the surrounding noise and help you focus on your tasks.
Please try and let me know your feedback. I think I can learn a lot this way and will will definitely evaluate and consider your ideas :)
P.S: Things learnt so far experimenting and building Classy:
1. Wireframe tools like Balsamiq and free paper sketching to put ideas on paper.
2. Photoshop basics to change color of icons and to generate color palette
3. Android ListView in depth and its limitations and actual functioning of recycle view
4. Android's Mediaplayer and Soundpool: pros and cons
5. Customizing native controls like seekbar.
6. Activities and how to trigger them.
>Just wanting to point this out, but the price for a single developer, with support included, is currently $590 according to this page: http://shop.highsoft.com/highcharts.html
Yep, Electron is excellent. However, Electron is built on top of V8 and V8 does not provide a way to protect the JS source. More than the technical problem this becomes legal issue for businesses that want to develop applications/tools rapidly with electron.
refer: https://github.com/atom/electron/issues/2570
Cons of other options that I know: 1. Obfuscation is not ideal to hide the source from competitors.
2. Writing nodejs modules in C++ is not so easy way. Once could prefer to develop entire app with C++ than the learning curve associated with node modules in C++.
3. V8 snapshots maybe a way to go with nw.js. But doesn't work great and it is hard to isolate issues while packaging.
4. EncloseJS looks promising. There is no company behind it and no guarantee it will be supported. (I personally have been following up with issues in packaging an open source app with encloseJS. No luck so far with support.
5. nexe is interesting. But not easy and no clear way to work with it.
What are your opinions? Any alternatives?
P.S: I'm framing a base with Java (most likely C++ too) to develop an app that runs on client machine but on browsers. Performance and source protection are my goals. Might open source its architecture eventually.