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!
@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
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
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?