5 ms·
First of all, clearly the advice I'm giving is a bit too early for where you are at presently. I think that's giving credit to you for the quality of the work y
by developer2 9y ago
First of all, clearly the advice I'm giving is a bit too early for where you are at presently. I think that's giving credit to you for the quality of the work you are producing. Basically, I want this app. You might want to dial back just a tad on the intricate details, out of fear you may wind up never shipping an initial version. Being a software dev myself, I understand that you could spend another year (hell, even 2-3 years) completely hashing out every minute detail. However I think that what you have is getting to the point of being "above and beyond what is necessary" that you need to stop tinkering so much, and find a way to ship something sooner rather than later.
When you get around to desktop clients, ignore the seemingly negative consensus regarding Electron[1] if you think it's the right fit for you. All the negativity I've read about it is from "purists" who aren't specifically singling out Electron; rather they are hating on all non-native implementations. I noticed the mention of Xamarin on your site; never heard of it, but I'd be weary as they seem to be oriented more towards mobile whereas you're looking for a cross-platform desktop solution which is where Electron shines.
If your goal were to be the gold standard for apps, you should be developing using native OS X APIs; the performance you get from a native implementation on OS X is astounding. However, if you do native OS X you're putting yourself in a position to do native Windows and possibly Linux apps, and the collective work required for native-everywhere obviously does not come easy or cheap - particularly if you are doing this as a solo project without assistance from a team.
Electron is a perfectly fine balance for most UIs that are fairly simplistic, which is going to be true even for the most advanced todo-type app. Extra bonus being that if you put in the effort to plan out the Electron app side-by-side with your web/browser-based app, you can share the frontend development between the two, resulting in less overall work.
[1] https://electron.atom.io/ https://electron.atom.io/
- VladimirGolovin 9y agoBeing a software dev myself, I understand that you could spend another year (hell, even 2-3 years) completely hashing out every minute detail. I won't do that :) I stopped working on the spec the moment I handed it down to coders, and my total time spent on the spec since then is around one week. When the spec is written well, and you simulated all important situations in your head before encountering them in the wild, you actually don't need much extra time. There's almost no tinkering happens on the app right now. I'm fixing critical bugs and smoothing out rough details that manifested after months of my dogfooding. Regarding the desktop solutions: yes, going native would be perfect, but that is not feasible for a 4-man team. We'll go with Electron or Xamarin or, less likely, Qt - we haven't decided on the exact technology yet.