Good practices to use meteor build tools to generate a website and a mobile app, but no back end

[fabienhuet]

I’m starting an application that already have a backend build in PHP. But I’d like to use meteor as my front end for both the website and the mobile app.

So, I’ll need to disable websockets, DDP… Export the result as a static site and export as a static app.

• disable elements : ?
• export as a static app : ?
• export as a static website : https://github.com/frozeman/meteor-build-client/ => it works well enough

[mordrax]

Honestly… the best things about meteor is minimongo, ddp, isomorphism. For front end, there are alot of people replacing spacebars with react, angular, ionic, etc… I wouldn’t be jumping onto the meteor bandwagon for a front end specific project even if the ground was on fire…

[robfallows]

You could look through this thread: What's the minimal amount of packages required to run Meteor server-side only?

[mordrax]

He wants it client-side only.

[robfallows]

True, but the principle of removing the meteor-platform package and then adding required packages is still valid.

[fabienhuet]

Well, it looks like it creates more problem than it solves

I think I’ll go with a basic gulp / react workflow.

[mordrax]

I just chanced upon this and take back my earlier opinion. It’s not only possible but people are already doing it, check it out:

Any way to make a 100% client-side app that's only HTML/JS?

Is there some way to use Meteor strictly 100% client-side, a la plain old HTML/Javascript? I imagine a process where I build front-end code and pretty much everything is in client/, and then I can minify/build/compile into HTML & Javascript, which I can upload to a web server and have it work. No Node needed, no Mongo, etc. Is this doable? If not, what’s the closest I can get?