Want to share your content on R-bloggers? click here if you have a blog, or here if you don’t.
I have just finished updating my reviews of graphical user interfaces for the R language. These include BlueSky Statistics, jamovi, JASP, R AnalyticFlow, R Commander, R-Instat, Rattle, and RKward. The permanent link to the article that summarizes it all is https://r4stats.com/articles/software-reviews/r-gui-comparison/.
I list the highlights below as this post to reach all the blog aggregators. If you have suggestions for improving any of the reviews, please let me know at muenchen.bob@gmail.com.
With so many detailed reviews of Graphical User Interfaces (GUIs) for R available, which should you choose? It’s not too difficult to rank them based on the number of features they offer, so I’ll start there. Then, I’ll follow with a brief overview of each.
I’m basing the counts on the number of dialog boxes in each category of the following categories:
- Ease of Use
- General Usability
- Graphics
- Analytics
- Reproducibility
This data is trickier to collect than you might think. Some software has fewer menu choices, depending on more detailed dialog boxes instead. Studying every menu and dialog box is very time-consuming, but that is what I’ve tried to do to keep this comparison trustworthy. Each development team has had a chance to look the data over and correct errors.
Perhaps the biggest flaw in this methodology is that every feature adds only one point to each GUI’s total score. I encourage you to download the full dataset to consider which features are most important to you. If you decide to make your own graphs with a different weighting system, I’d love to hear from you in the comments below.
Ease of Use
For ease of use, I’ve defined it primarily by how well each GUI meets its primary goal: avoiding code. They get one point for each of the following abilities, which include being able to install, start, and use the GUI to its maximum effect, including publication-quality output, without knowing anything about the R language itself. Figure one shows the result. R Commander is abbreviated Rcmdr, and R AnalyticFlow is abbreviated RAF. The commercial BlueSky Pro comes out on top by a slim margin, followed closely by JASP and RKWard. None of the GUIs achieved the highest possible score of 14, so there is room for improvement.
- Installs without the use of R
- Starts without the use of R
- Remembers recent files
- Hides R code by default
- Use its full capability without using R
- Data editor included
- Pub-quality tables w/out R code steps
- Simple menus that grow as needed
- Table of Contents to ease navigation
- Variable labels ease identification in the output
- Easy to move blocks of output
- Ease reading columns by freezing headers of long tables
- Accepts data pasted from the clipboard
- Easy to move header row of pasted data into the variable name field
General Usability
This category is dominated by data-wrangling capabilities, where data scientists and statisticians spend most of their time. It also includes various types of data input and output. We see in Figure 2 that both BlueSky versions and R-Instat come out on top not just due to their excellent selection of data-wrangling features but also for their use of the rio package for importing and exporting files. The rio package combines the import/export capabilities of many other packages, and it is easy to use. I expect the other GUIs will eventually adopt it, raising their scores by around 20 points.
- Operating systems (how many)
- Import data file types (how many)
- Import from databases (how many)
- Export data file types (how many)
- Languages displayable in UI (how many, besides English)
- Easy to repeat any step by groups (split-file)
- Multiple data files open at once
- Multiple output windows
- Multiple code windows
- Variable metadata view
- Variable types (how many)
- Variable search/filter in dialogs
- Variable sort by name
- Variable sort by type
- Variable move manually
- Model Builder (how many effect types)
- Magnify GUI for teaching
- R code editor
- Comment/uncomment blocks of code
- Package management (comes with R and all packages)
- Output: word processing features
- Output: R Markdown
- Output: LaTeX
- Data wrangling (how many)
- Transform across many variables at once (e.g., row mean)
- Transform down many variables at once (e.g., log, sqrt)
- Assign factor labels across many variables at once
- Project saves/loads data, dialogs, and notes in one file
Graphics
This category consists mainly of the number of graphics each software offers. However, the other items can be very important to completing your work. They should add more than one point to the graphics score, but I scored them one point since some will view them as very important while others might not need them at all. Be sure to see the full reviews or download the Excel file if those features are important to you. Figure 3 shows the total graphics score for each GUI. R-Instat has a solid lead in this category. In fact, this underestimates R-Instat’s ability if you include its options to layer any “geom” on top of another graph. However, that requires knowing the geoms and how to use them. That’s knowledge of R code, of course.
When studying these graphs, it’s important to consider the difference between the relative and absolute performance. For example, relatively speaking, R Commander is not doing well here, but it does offer over 25 types of plots! That absolute figure might be fine for your needs.
The post R GUI Reviews Updated first appeared on r4stats.com.
R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you’re looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don’t.
Continue reading: R GUI Reviews Updated
Analysis of R GUI Reviews
An in-depth review of Graphical User Interfaces (GUIs) for the R language has been conducted, comparing key features of popular interfaces including BlueSky Statistics, jamovi, JASP, R AnalyticFlow, R Commander, R-Instat, Rattle, and RKward. The categories of Ease of Use, General Usability, Graphics, Analytics, and Reproducibility were considered as part of the comparative study. The GUIs were scored depending on how many features they offered in each category.
Implication and Future Developments
Improvements in Ease of Use and Functionality
First, it is clear that no GUI achieved the highest possible score in any category. This suggests that there is considerable room for improvement in all interfaces, especially in terms of ease of use. There is a need for R GUI developers to give more consideration to user-friendly features such as having simple menus that grow as needed, the easy movement of blocks of output, and the smooth importing of data from the clipboard.
Adoption of the Rio Package
Second, some GUIs like BlueSky and R-Instat were recognized for their use of the rio package for importing and exporting files. This convenience feature is expected to be eventually adopted by the other GUIs, potentially boosting their scores by about 20 points.
Graphics Capabilities
Third, there were significant differences in the graphics capabilities of the various GUIs. For example, R-Instat stood out due to its layering option, which could allow any graph to be placed on top of another. However, this feature requires knowledge of R code.
Actionable Advice
If you decide to use a GUI for R, firstly, consider the features that are most important to you. The robust review provided something of a consumer report, offering detailed insights into the strengths and weaknesses of each GUI.
Secondly, it is suggested that you keep an eye on GUIs that are making intensive use of the rio package. It seems that this feature is gaining prominence in the R community, and it is likely that user interfaces that adopt this package will gain in popularity and acceptance.
Finally, when it comes to graphics, it is important to not only look at the score but also understand what the score means in terms of the absolute performance of the GUI. For example, while a GUI can have a relatively low score, it might still offer the kind of graphics utility that satisfies your specific needs.
An in-depth understanding of your requirements from a GUI, keeping an eye on emerging trends, and a critical evaluation of GUI capabilities are key to making the right choice. Also, providing feedback to the GUI development teams can help in the evolution of these interfaces to better serve user needs.