Yeah. So? By linking a framework that's using private APIs, this becomes your problem now. And Electron's problem, by extension. Go bug them, not Apple.
Electron apps cannot be submitted to the Apple store
11–20 of 441 posts
Re: Electron apps cannot be submitted to the Apple store
#12Well, why the hell is electron/chromium using private APIs? That seems like the real problem here...
Re: Electron apps cannot be submitted to the Apple store
#13Re: Electron apps cannot be submitted to the Apple store
#14The lesson here is write native apps using the preferred native tools of the platform, and avoid shortcut solutions.
and then the app is never written
Re: Electron apps cannot be submitted to the Apple store
#15> I did write back to Apple trying to explain that I am using Electron and I can't really change any of these public-framework usage Yeah. So? By linking a framework that's using private APIs, this becomes your problem now. And Electron's problem, by extension. Go bug them, not Apple.
Re: Electron apps cannot be submitted to the Apple store
#16Re: Electron apps cannot be submitted to the Apple store
#17Wonder why they couldn't do the same for the iOS appstore. Like js apps based in phonegap
Electron always uses Chrome whether it is on MacOS or Windows. There was a node-webkit project before Electron, I don't know its status.
Re: Electron apps cannot be submitted to the Apple store
#18And mind you, GitHub Desktop is taking that much just for showing a mostly empty window! while Fork and Tower are displaying a lot more UI, more controls, trees, custom drawing, more text, and have overall more features (best of all: spell checking for commit messages because all native text fields get it for free.) You can try it on your own machine and compare them.
Now yes Electron has made life very easy for some developers and some apps wouldn't even exist if not for Electron, but why, as a user, should I pick an Electron app over native alternatives?
Re: Electron apps cannot be submitted to the Apple store
#19Re: Electron apps cannot be submitted to the Apple store
#20The lesson here is write native apps using the preferred native tools of the platform, and avoid shortcut solutions.
Don't use anything that provides portability like C or Objective-C, that's not really "native" to the CPU architecture.
.. I know that sounds silly, but you're advocating for that one layer up. It's a very good analogy I think.
People use electron in order to "compile to" native apps for linux and windows and mac without having to write the app 3 times.