The R-Studio suite is a well thought out solution to development, control and publishing r apps and services.
Updated September 10, 2021
The R-Studio suite is a well thought out solution to development, control and publishing r apps and services.
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with RStudio
RStudio is a great way to allow teams to develop r-shiny apps without needing to go and install lots of software on each developer's individual machine. It helps people to get ideas together much faster that you can traditionally. And by pairing it with other products in the suite you can then deploy them to non-devs too for quick feedback.
- Centralised admin
- Ability to manage allocations of CPU / RAM per user
- SSO
- Set up can be complex
- Automated updates via the admin screens
- Less wasted spend on unnecessary large scale development products
- Our use is easy so difficult to say here
- One risk is that users may expect "full scale" apps after seeing the r-shiny one, which is a bigger leap than expected.
PBI is a similar product in many respects that it targets more of the technical business user rather than traditional developer.
However, PBI itself is a great visualisation tool but has limited scripting and forms functionality. It would make sense to pair PBI with PowerApps, or other products in the Power Platform, but r-studio is more like PBI and PowerApps combined.
However, PBI itself is a great visualisation tool but has limited scripting and forms functionality. It would make sense to pair PBI with PowerApps, or other products in the Power Platform, but r-studio is more like PBI and PowerApps combined.
Do you think Posit delivers good value for the price?
Yes
Are you happy with Posit's feature set?
Yes
Did Posit live up to sales and marketing promises?
Yes
Did implementation of Posit go as expected?
No
Would you buy Posit again?
Yes
Using RStudio
300 - A mixture of our users use R-Studio. Analysts use it to prototype ideas, while more business focused people use it to demo upcoming features to their users. It's used as means to get analytical tools in the hands of those who need that insight, without the need of a full-blown dev team in the mix.
3 - A small amount of infrastructure related staff, such as a DevOps Engineer.
Also a "product champion" who owns the way the products are configured, the features they want enabled, and how apps are secured.
An architect is also involved to liaise between the two and offer technical suggestion to resolve issues such as sharing code / libraries between R Studio Apps, deployment practices, source repo locations, etc.
Also a "product champion" who owns the way the products are configured, the features they want enabled, and how apps are secured.
An architect is also involved to liaise between the two and offer technical suggestion to resolve issues such as sharing code / libraries between R Studio Apps, deployment practices, source repo locations, etc.
- Prototyping
- Industrialisation of "small" apps that would never be approved for a full size dev team
- Proof of concepts
- Data validation
- Technical research
- Research
- Ability for R-Studio apps to share code
- Single Sign-On
- Potential to expand to external users / clients
- Other business areas
- Non technical staff delivering example apps