An update, various age late:

What engineering to use for integration R into web apps depends upon the descale of what you are nerve-racking to achieve.

For pocket-size, standalone web apps, Lustrous is quick seemly the de facto criterion. It is comparatively wanton to use, and thither are gainful keep options.

For larger projects, you are believably wagerer off exploitation any web model you are well-fixed with so computation out how to unite to R. (You can birdsong R from the control job from any more-or-less any former package, and thither are approximately somewhat nicer interfaces to R such as rJava https://glamorgananglers.co.uk/ for Coffee apps.) This sounds a footling shadowy, but for such projects the authoritative decisions are based on what does your party already use? and what do you motive R for?

Thither are heaps of unlike shipway of creating a web app with R. Virtually (ie all) are listed in the FAQ on R papers.

If you need to use RApache, thither’s a presentment on the old RApache place that mightiness be utile to get you started. Differently, RWui is real unproblematic to use, but not so elastic (close clip I victimized it, anyhow), and rcom/StatConnector can be secondhand to run R from your web host.

Deliver you seen p>

The job I incur with this, is that as your webapp grows, the glossy guestwaiter abstractions get debatable for exploitation and you motivation to replication to approximately gimmicks (mention, responsive, etcetera) in rescript to lodge active web employment.

So, my hypnotism would be to counterbalance the total of webapp vs. R maturation. If you indigence more of the early, so Shining leave not serve.