I have developed a RShiny application which I would like to share internally with my colleagues (Hosting the app on a server, is not an option at this stage).

I was exploring various options, and I came across a technique for bundling your app as a standalone desktop application, with an installer file, which you can then share & distribute. (The approach is explained [here](http://www.r-bloggers.com/deploying-desktop-apps-with-r/) & [here](http://blog.analytixware.com/2014/03/packaging-your-shiny-app-as-windows.html))
This is quite neat, because the users installing it need not have R (and any other required packages) to install and run the app (it has portable versions of R, chrome etc)

I was able to follow the approach and create a standalone desktop application, with an installer file, which I can now start sharing.

However, this is my concern:
Ideally, I would not want my users to be able to access the source code. Is there a way to restrict such access? In the tutorial (the first link that I posted), this is what the author says:

\*

> 
> Lastly, keep in mind that your source code is easily accessible. If
>  this is a concern for you (e.g. if you are distributing to a client
>  that should not have access to the code) the best you can do is impede
>  access by first compiling the sensitive source code into a binary
>  package. That said, any user who knows R (and has sufficient intent)
>  can simply dump the code to the console.
> 
> 
> 

\*

Are there better, more fool-proof ways to impede access?

Thanks!