Have you thought about using PWA to deliver the app to the desktop? I know it’s not for every use case, but for some use cases it might be good enough.
I’ve been seeing over & over @alawi’s mention of PWAs and somehow I was not aware of their desktop/chrome integration 
I just made the Meteor Forum a PWA (looks so nice as an app, see image below), not just another tab in my browser anymore.
Looks like the PWA desktop might not give you everything that an Electron app does, but wow, I’m impressed. Not sure how I missed this, but I’m even more excited to make my Vue + Meteor app PWA compatible now!
I had realized this for Mobile, but not Desktop… pretty nice & easier alternatives to Cordova and Electron. Although, I do support keeping strong Cordova support & Electron support growing. I do think many mature apps depend on these.
For me the biggest draw to desktop & mobile apps is just the user having an easy icon to click on and recognize when they use the app daily. This is the BIGGEST factor for users returning daily to interact with an app.
For so many years I’ve wondered why this was not easier to do. Feels like 10 yrs ago now, but I remember using this http://fakeapp.com/ for OSX back in the day, but it was not really a good solution.
It would be great to add PWA details in the Meteor docs. I have noticed Vue’s CLI & Gatsby have clear PWA docs.
Thanks to @jkuester for this Meteor PWA guide, I now finally get why the Meteor core team should prioritize making this more obvious, aka good docs, and maybe an atmosphere package or a skeleton for a PWA app that would configure a package like the Vue CLI does.
@filipenevola hoping you could take a quick look at this 
and share with the Meteor core team! 
2 Likes
@omega a great alternative to getting this into core is getting it into the Meteor-Community-Packages org, so that others can help maintain and release it. Others are willing to help keep it up to date as many ppl have businesses relying on this package. Please see this issue https://github.com/wojtkowiak/meteor-desktop/issues/243
2 Likes
2 Likes
So how does the package get there? As much as I understand it’s no longer supported by the original author.
No responses on bugs/issues either. We went along the path due to security and data privacy reasons and are now facing issues as the automatic update doesn’t work and is leaving our customer being stuck with bugs that are long solved (see Cordova force update on stuck clients due hash mismatch)
We’ve been using electron-updater to update our meteor-desktop electron from electron 2 to electron 9 over the course of a couple years and have never had any issues, so it’s not an issue of meteor-desktop.
If the maintainer abandons an open source project then the path forward is fork it into the Meteor-Community-Packages org. It would just need to use a different npm package name like “meteor-desktop-community” or something
1 Like
We’re a two people company and still haven’t launched, so unfortunately we’re not able to maintain this package
Are you guys able to do this or how can we find a volunteer who takes it over?
Hi @efrancis and all, sorry, I’m late here, very late btw.
I have never developed an app with Electron but I have a PWA for desktop with Meteor for example.
Electron could also be a nice addition as we need to access restaurant’s printer and other resources in this product (https://www.bemarke.com)
Also, in the Meteor Software (Tiny) company side, we are willing to keep Meteor as a great choice for desktop apps.
What are the issues, PRs that are pending that we could take a second look?
Please send me a private message here or on Slack if you think we can help in any way. It would be important to have people actively development with Meteor and Electron involved in this work.
1 Like
Hmmm… there is even a Cordova-Electron option apparently: https://medium.com/the-web-tub/electron-on-cordova-29ede5d6d789
First issue that comes to my mind is that the package owner isn’t even responding to requests/issues to move it over into the community, see here:
There are 67 open issues, we personally have a lot of problems with auto-updater and HCP. I know that others had similar issues as well.
Lastly, we need to make sure that the newest version of ElectronJS is used. With no support, this obviously becomes a bigger and bigger problem.
2 Likes
Yes this is the biggest issue @filipenevola, the package is fantastic and does all the work required to use Electron but the community is unable to contribute and it has a ton of open issues. Bringing it under an official meteor or meteor community org would enable us to keep it moving.
Someone has built a complete integration for Electron and it adheres to Meteors build target concept already, little work is required on Tiny. We just need to be able to maintain and update it.
3 Likes
Perhaps it is time to consider just forking the package? It seems like a good candidate for the meteor community org as there seems to be people willing to pitch in. As it is released under the MIT license there should be no legal restrictions to forking. It’s certainly polite to ask first, but that has already been done.
2 Likes
I second that. The original author hasn’t responded in a long time to both issues as well as to requests to update the package.
Forking it is a short term solution to implement bug fixes that are outlined by the various users but IMO its most important that this package is taken in under the official Meteor community as @efrancis also proposed.
1 Like
Now that desktop support is being prominently on Meteor.com I think it’d be great to revisit this. For example with HMR in Meteor 2.0 now, getting HMR support for desktop apps would be very helpful for faster development.
Or as another example, releasing an auto updating Electron app requires deploying to an S3 bucket. It would be amazing if Meteor Cloud supported this while deploying so that we could move entirely off of AWS and to Meteor Cloud instead.
4 Likes
PWA may be a first step for devs to support desktop platforms. What do you expect from your Meteor PWA (Draft here: https://github.com/activitree/Meteor-PWA-Explained) - #22 by paulishca
We can add a new section “Create PWA in X steps” to tutorials.
2 Likes
Let’s first take it over into the Meteor Community and fix those large amount of open issues.
Then we can look how we develop this package further.
1 Like
I think it wasn’t announced yet but thanks to @koenlav and @copleykj we now have the Meteor-desktop package under the Meteor Community umbrella:
https://github.com/Meteor-Community-Packages/meteor-desktop
Please report any issues that you find there so that we can improve the package further on.
Thanks Koen and Kelly!
5 Likes
@koenlav @copleykj do you still own that meteor-desktop community repo? I’d really like to get this fixed asap and get it published to npm. Mongo Atlas is forcing some tiers to Meteor 5.0 which requires upgrading to Meteor 2.6, and meteor-desktop is currently incompatible with Meteor 2.3+ because of this issue.
That means anyone using meteor-desktop is going to have their app break in production some time next week unless this is fixed and released to npm.
We have migrated away from meteor-desktop and started using @capacitor-community/electron.
We actually migrated our entire stack away from “Meteor bundled hybrid layers” (Capacitor/Meteor-Desktop) and moved entirely to Capacitor.
The MongoDB 5 upgrade is only forced for free-tier Atlas clusters, so this should not impact production apps.
If someone is willing to pick up the Meteor Desktop project feel free to mention this here (or beter: GitHub - Meteor-Community-Packages/organization: Discussions on organization of the organization 🎩), it should be relatively trivial to fix these bugs.