What is the most suitable way to separate the front-end and the back-end of an app?

Earlier I asked whether we can restrict loading of some files based on the route. Looks like the best way to do this is create multiple apps. Let’s say we have a front end and a back end. When separating these two, my questions are…

  1. Is it a good idea to write the front end with plain html and js and use api calls to fetch the data? How can I do this? This is might be good for some instances but it will remove the reactivity right?
  2. How can I just show a simple js and html login screen (without loading the whole app (display a 404 page again without the whole app)), validate by calling the meteor app and show the real site only when logged in?

I hope the Meteor community already have good solutions for this :slight_smile:

Have you tried using client and server directories within your app?

Here are the relevant docs: http://docs.meteor.com/#/full/structuringyourapp

Yes but even the admin interface’s html and js files need to be placed in the client. So they will be loaded for everyone :neutral_face: