When Meteor came out a couple of years ago I picked it not only because it was fun developing, but I really liked the prospect of being able to have a single code base for desktop and mobile.
I am in the process of re-writing my application, ditching blaze because I want SSR, so I am trying to choose between VueJS and maybe Svelte (I just can not bring myself to learn React).
Do you guys think Meteor+Cordova is still a good option to build a mobile app? If so, what are your recommendations?
Iām hoping others share here too, but I think Meteor w/ Cordova is still a top way to produce mobile apps with minimal coding.
A really top notch Cordova app, that I didnāt even realize was Cordova is JustWatch, I use this app pretty often to find the best options to stream movies & shows since there are so many platforms now.
Youād probably never think itās not 100% native.
Also, I donāt think SSR is as important as the trends are making it look right now, I think fast apps are the big deal. To me SSR makes development a bit harder, and puts a lot more load on the server during production, where I think that āclientsā should share some of the processing load. Smart phones and laptops are light years ahead of where they were 8 yrs ago, so SSR will seem less relevant every year that hardware advances in my mind.
I just turned my Meteor + Vue app into an official PWA (desktop app & mobile app) with just a couple hours of work, and adding two new JS files to my project and a couple <meta> tags in my main.html file. It blew my mind 
My app, without SSR performed or even final performance tweaks did very well on Googleās Lighthouse tests. I used this guide thanks to @jkuester. Also I figured out how to do native web notifications on all devices other than iPhones, but people expect Apple will make changes that allow them this fall (iOS 14 coming, still a rumor though).
If youāve never seen a PWA app for desktop (download button automatically pops up in Chrome) and mobile, you should check out this example Vue PWA app
I now have an amazing single code base for a Web App, Desktop App, and Mobile Apps that work on Androids, iPhones, and Windows phones or others. I get to bypass the App Store review processes and keep my app current without my users doing updates. This is crazy amazing!
Vue is the dream for me and it is very mature compared to Svelte if you ask me. But pick what you might like the best. The Vue community is the biggest open source community on the planet right now, as far as I can tell, so there are so many things done 
as examples out there that itās fun to build with.
Iām still possibly planning to use Cordova if I want my App in the App Stores eventually, but I can probably hold off for several months or a year on that now and have more simplicity for my initial user base.
Holy crap, that is cool. Need to check into that. Thanks for your feedback.
So you are not using SSR for your VueJS app?
Correct, no SSR for me, I thought about it at the beginning of this project, even did a bit of testing with it, but to me SSR would be more well suited for fast loading websites, just 1 last thing you can do if you want max performance. But for a full multi-user app, I think it has more drawbacks than benefits.
Many people favor SSR for static site generation, due to extra good SEO ease, but there are other ways to SEO optimize a Meteor app too. Static site generation is a cool use case, but it has so many different priorities than real-time mulit-user app development. Everything has tradeoffs, but for me I just donāt want the extra complexity of SSR when I have so many other things to handle. Vue is VERY fast already due to its design and is going to be even faster in Vue 3. And Svelte is super-fast too. Devs from Vue & Svelte both shared optimizations and were able to improve both projects.
I definitely recommend Meteor+Cordova for mobile apps, especially since the recent update to Meteorās version of Cordova proved there is on-going commitment from Tiny (https://github.com/meteor/meteor/issues/10718#issuecomment-555981992)
You canāt beat a single code-base and not having to provide a separate API for native mobile apps. Development and maintenance is a dream. The best bit is hot-code-push though - from a single deploy I update all my web, iOS and Android clients. No need to update app store releases and lengthy Apple reviews every time. Means you can easily do quick development cycles rather then waiting until youāve got enough to bother with a new release.
Using a Material Design library (Vuetify) makes it easy to develop UI which looks great and works briliantly on all devices.
Iām using SSR with Vue, and even added pre-caching and critical CSS to make my landing pages extra fast. I donāt use SSR on logged-in routes though, I only use it on my sales pages. As @mullojo says, it increases load on the server. For my logged-in users SSR isnāt really necessary because they probably have all the app.js, css, and even any pre-visited code-split routes cached in their browser or bundled into the apps, so loading is quick. You only really need SSR on certain pages where you want new visitors to get a quick load time. If those pages are static then you can cache it (as Iāve done), if not you can SSR on demand with hydration.
Have fun! (and it is fun - I have zero frustration points with this setup).
Now Iāve read @mullojoās post a bit more closely, and looked as his demo Iām super impressed with his usage of PWA instead of Cordova! 
For a suitable project PWA would definitely be easier than Cordova. However, hereās why I need/use Cordova instead:
Iām pretty sure Iāll eventually add Cordova to my stack for those same reasons 
Just another reason I love Meteor. I still have to see how more people āhandleā the PWA install idea since it is still so new for most people. And Apple has really dragged their feet on PWA āawarenessā, but almost any app today should include PWA support as a base design requirement. All the big platforms are quietly adding it.
I just removed SSR from my project, but it still restarts the server when I edit a client file. Any ideas why?
Maybe just build a super simple clean project from this guide and give it a tryā¦
I donāt know enough about your projet to advise, but that shouldnāt happen.
For most apps Iād definitely recommend PWA over Cordova at this point. Or to put it in other words, Iād look at options beyond PWA only after I have determined that the app at hand absolutely must have some feature that PWA does not support right now and will not in the foreseeable future. Most apps donāt have such requirements. With PWA:
Like wildhart said, users not āgettingā PWAs is a thing. But this can also be mitigated. It is possible to override the browserās default PWA installation flow (the āAdd to home screenā popup) with the beforeinstallprompt event and handle the installation process in your own UI instead.
I agree with this, Iām also pushing for PWAs over Cordova and Native. Once iOS implements notifications, I donāt see a reason at all to go the native for most of the apps.
Hereās a real-world example of life on the other side (without Meteor or Cordova)ā¦
I have a new job (yay!) and Iāve inherited another project - Iām responsible for the node+mongoose backend and Vue frontend, a colleague is responsible for the native iOS app. There are various collections referencing each other by _id, which need to be displayed to the users, and also some calculated fields (e.g one document isActive if it is used by an active document in another collection). Typical stuff.
I have asked to do the reactive joins and computed properties in the client because itās super easy (particularly using Vue), but heavy lifting for the server, particularly making sure the isActive fields are kept up-to-date.
However, the other dev has asked if we can do all that on the server so he doesnāt have to reproduce the joins/computed fields in swift which doesnāt make it as easy for him. And I see his point.
But jeez, I wish we could use Meteor+(Cordova|PWA) for this project! Write-once-run-anywhere is such a time saver. Weāre both having to reproduce ALL the client UI. Gonna try harder on Monday, but I think itās too late to convert this project to Meteorā¦
We are dropping Meteor+Cordova in favor of PWA. We started our company with a couple of Meteor + Cordova apps. And after doing some SWOT analysis, we have concluded that us and our users will benefit a lot for choosing PWA over Cordova.
The biggest negative that we will lose is IOS push notifications (as @alawi mentioned) but the benefits of doing PWA for us far outweighs this negative. And we are bullish that iOS will support it before the end of the year.
We also highly recommends SSR (+inline css, +fast-render-like data) especially if you will get a lot of traffic from SEO. Achieving a one-render hydration without data query is amazing
I understand how PWA has benefits for developers, but Iām interested what your benefits to users would be?
I knew PWA was supported on smartphones ā with somewhat limited support on IOS for the time being ā but I didnāt know until I read your post that it was supported on OS X desktop. I installed Journalistic. Amazing!
That is an easy answer. Each page in our site has a url. And thus available in search.
We connect property buyers to brokers and agents. Buyers will easily find the properties through a Google/Bing search. It benefits both buyers and sellers. In a cordova app, the app download is a big hurdle.
Also, there is an indirect benefit to users when developers can have more time improving one system than dividing time in maintaining two separate ones.
Iām totally in favor of Meteor+Cordova.
I tried with PWA, and although functionality was the same (I didnāt check PushNotifications, though), final users were asking to get it from the stores. May be in the future where/if final users are more used to PWA (instead of stores) will consider PWA again.
Meteor+Cordova having the Hot Code Push make it also great for quick improvements without waiting for the stores approval/updates.
It depends on the the app you are building and how you plan to market it.
Some of us here are building enterprise apps and there is no need to put in the stores, some running websites and just want to improve the mobile experience.
Now for the consumer apps, yes , this is what the most consumers currently accustomed to, however keep in mind few things:
To sum the only reason why PWA is still not mainstream is consumer familiarity and Apple.
So I would encourage developers to go with PWA whenever they can to break the stores dominance and save themselves money and time unless they absolutely need to go to those stores.
I for one canāt wait to get rid of the Play/Apple stores duopoly, we spend large money on these hardwares, we deserve more options.
just today, I tried to run the todos meteor svelte repo on mobile. Because I was thinking svelte should be the best option for mobile since the performance and what is not. However, I could not get the app to work. The app just shows an empty screen in the emulator and even that happened after spending sometime with preparing all of the prerequisites. First, it complained about jdk so I installed the latest version then it complained jdk must be v8 so I tried to find a download link for jdk 8 that is not from the official orcale website cuz I donāt wanna sign up for that crap company then it complained about Android studio not being installed which it was but gave me a choice to install Gradle instead so installed gardle. Basically, I do not think mobile meteor svelte is ready for production. Maybe I missed something important, the prerequisites are normal and no big deal but I hated that I wasted so much time but at the same time that white empty screen is just not a good first impression