Analysing the use of my shiny apps
Chris Evans
2024-08-20, updated 2026-0405
Introduction
This summarises the use of my shiny apps (at https://shiny.psyctc.org/). The page is regenerated to reflect the latest data usually a bit after 03.00 UTC (previously GMT).
Data used to generate this
Info | Value |
|---|---|
First date in data | 2024-02-07 |
Last date in data | 2026-04-17 |
This analysis time/date | 03:13 on 18/04/2026 |
Number of days spanned | 800 |
Total number of sessions | 9214 |
Mean sessions per day | 11.52 |
I am not using any way to separate different users and session is per app, so if someone used multiple apps during one visit to the server, each app used is counts as a separate session.
App uses per day
I can identify one early spike after the apps were publicised through the Systemic Research Centre Email list (5.iii.24) and a smaller one after a posting to the IDANET list (9.iii.24). There are later bursts that I can’t directly ascribe to any publicity.
Mean sessions per day, broken down by week
More sensibly, here is the plot by week, actually plotting the sessions per day and counting from the launch from the launch on 7.ii.24. Where the last week is still an incomplete week that has been taken into account in the calculations, i.e. the plot shows the mean for the number of days so far in that most recent week. 95% CIs are Poisson model estimates.
Breaking that down by app gives me this.
And facetting by app gives this.
Sessions per Month
This is still mapping mean number of sessions per day, but broken down by month.
The first month was incomplete and the last month will usually be incomplete, that is taken into consideration in computing these session per day rates.
Numbers of sessions per app
Here is an interactive table with the usage stats for each app. The names of the apps are clickable links to the apps. You can search the apps and perhaps most usefully, you can change the column sorting using the headers of the columns and you can export the data should you have such an appetite!
Warning: the rest of this output is not that important!!!
The rest of this is unchanged as of code I wrote a few years ago soon after I got my shiny apps up and running. I’m not convinced it’s very useful but I’ve left it hear for now!
App | Sessions | First used | Days available | Sessions per day | Days used | % days used |
|---|---|---|---|---|---|---|
RCI1 | 4,072 | 2024-02-07 | 801 | 5.084 | 670 | 84% |
CSC1 | 1,146 | 2024-02-07 | 801 | 1.431 | 418 | 52% |
COREpapers1 | 569 | 2024-05-11 | 707 | 0.805 | 258 | 36% |
RCI2 | 526 | 2024-02-07 | 801 | 0.657 | 282 | 35% |
CORE-OM_scoring | 496 | 2024-04-16 | 732 | 0.678 | 251 | 34% |
Cronbach1Feldt | 248 | 2024-02-07 | 801 | 0.310 | 178 | 22% |
YP-CORE_2_scores | 197 | 2025-06-16 | 306 | 0.644 | 58 | 19% |
CSClookup2a | 154 | 2024-02-07 | 801 | 0.192 | 80 | 10% |
Spearman-Brown | 152 | 2024-05-03 | 715 | 0.213 | 114 | 16% |
CIcorrelation | 145 | 2024-02-07 | 801 | 0.181 | 99 | 12% |
CISpearman | 137 | 2024-02-07 | 801 | 0.171 | 89 | 11% |
Gaussian1 | 124 | 2024-03-05 | 774 | 0.160 | 92 | 12% |
ECDFplot | 109 | 2024-02-07 | 801 | 0.136 | 49 | 6% |
get_Sval_from_Pval | 91 | 2025-09-02 | 228 | 0.399 | 83 | 36% |
CIproportion | 79 | 2024-02-07 | 801 | 0.099 | 60 | 7% |
g_from_d_and_n | 74 | 2024-02-07 | 801 | 0.092 | 65 | 8% |
random1 | 72 | 2024-11-19 | 515 | 0.140 | 61 | 12% |
Attenuation | 69 | 2024-10-09 | 556 | 0.124 | 46 | 8% |
CImean | 68 | 2024-02-07 | 801 | 0.085 | 56 | 7% |
Mean i-i-corr from alpha | 67 | 2025-06-27 | 295 | 0.227 | 56 | 19% |
CISD | 66 | 2024-02-07 | 801 | 0.082 | 47 | 6% |
Histogram_and_summary1 | 62 | 2024-03-25 | 754 | 0.082 | 31 | 4% |
Attenuation2 | 61 | 2024-10-11 | 554 | 0.110 | 51 | 9% |
Feldt2 | 58 | 2024-11-27 | 507 | 0.114 | 41 | 8% |
getCorrectedR | 50 | 2024-10-13 | 552 | 0.091 | 42 | 8% |
plotCIPearson | 49 | 2024-02-07 | 801 | 0.061 | 36 | 4% |
Screening1 | 48 | 2024-02-07 | 801 | 0.060 | 38 | 5% |
Bonferroni1 | 47 | 2024-03-24 | 755 | 0.062 | 35 | 5% |
CIdiff2proportions | 41 | 2024-02-07 | 801 | 0.051 | 24 | 3% |
useConvFiveNum | 38 | 2025-04-07 | 376 | 0.101 | 35 | 9% |
Hashing_IDs | 34 | 2025-04-05 | 378 | 0.090 | 24 | 6% |
Create_univariate_data | 32 | 2024-04-09 | 739 | 0.043 | 31 | 4% |
CORE-OM_scoring2 | 18 | 2025-10-09 | 191 | 0.094 | 9 | 5% |
Forest_plot_rates | 14 | 2026-01-08 | 100 | 0.140 | 8 | 8% |
The columns of Sessions per day and of Percentage days used are rather misleading as different apps have been available for very different numbers of days. I won’t be able to get a less misleading forest plot of the mean usage per day per app until there has been far more usage than we have had so far so I will maybe add that later in the year.
However, I can get confidence intervals for proportions on what usage we already have so here’s a less misleading forest plot of proportion of the available days on which each app was used. The dotted reference line marks the overall usage as a proportion of days available across all the apps.
Here’s a map of usage per app against dates. The sizes of the points show how many times the app was used on that day. The y axis sorts by first date used and then by descending total number of times used.
That shows that many of the apps were first used on the same day (7.ii.2024) which was the day I set up this logging. I tested all the then existing apps that day so all appear on that day.
Breakdown by day of the week
Weekday | n | percent |
|---|---|---|
Mon | 13,838 | 19% |
Tue | 13,028 | 18% |
Wed | 10,880 | 15% |
Thu | 10,762 | 15% |
Fri | 10,653 | 15% |
Sat | 6,477 | 9% |
Sun | 6,973 | 10% |
Same sorted!
Weekday | n | percent |
|---|---|---|
Mon | 13,838 | 19% |
Tue | 13,028 | 18% |
Wed | 10,880 | 15% |
Thu | 10,762 | 15% |
Fri | 10,653 | 15% |
Sun | 6,973 | 10% |
Sat | 6,477 | 9% |
Time of day
I’ve broken this down by hour. The server is to some extent protected behind a proxy at my ISP which is good for forcing https access but it does mean that I don’t know where people come from so this is all UMT (i.e. old “GMT”: internet time). I think it also suggests, assuming that most accesses are during working hours, that most visitors/users are coming to the site from Europe or the Americas.
Hour | n | percent |
|---|---|---|
0 | 117 | 1% |
1 | 123 | 1% |
2 | 123 | 1% |
3 | 119 | 1% |
4 | 216 | 2% |
5 | 335 | 4% |
6 | 484 | 5% |
7 | 512 | 6% |
8 | 529 | 6% |
9 | 526 | 6% |
10 | 551 | 6% |
11 | 514 | 6% |
12 | 514 | 6% |
13 | 566 | 6% |
14 | 596 | 6% |
15 | 713 | 8% |
16 | 447 | 5% |
17 | 485 | 5% |
18 | 348 | 4% |
19 | 388 | 4% |
20 | 366 | 4% |
21 | 293 | 3% |
22 | 196 | 2% |
23 | 153 | 2% |
Same sorted.
Hour | n | percent |
|---|---|---|
15 | 713 | 8% |
14 | 596 | 6% |
13 | 566 | 6% |
10 | 551 | 6% |
8 | 529 | 6% |
9 | 526 | 6% |
11 | 514 | 6% |
12 | 514 | 6% |
7 | 512 | 6% |
17 | 485 | 5% |
6 | 484 | 5% |
16 | 447 | 5% |
19 | 388 | 4% |
20 | 366 | 4% |
18 | 348 | 4% |
5 | 335 | 4% |
21 | 293 | 3% |
4 | 216 | 2% |
22 | 196 | 2% |
23 | 153 | 2% |
1 | 123 | 1% |
2 | 123 | 1% |
3 | 119 | 1% |
0 | 117 | 1% |
Browsers
For what little it’s worth, here are the browser IDs picked up by shiny (in descending order of frequency).
The value of “ahrefs.com/robot/” is my translation of accesses that identify their browser as: “Netscape 5.0 (compatible; AhrefsBot/7.0; +http://ahrefs.com/robot/) -?”.
For reasons I don’t understand, my open source shiny does not seem to detect Microsoft Edge. I have used the apps with Edge (ugh) and it didn’t show up here. If you know why, or even how to detect Edge, do tell me (https://www.psyctc.org/psyctc/contact-me/)!
Browser | n |
|---|---|
Chrome | 6,639 |
Firefox | 1,253 |
Safari | 950 |
Other | 181 |
Opera | 59 |
The “Other” there refers to visits from browsers not identifying as one of Chrome, Firefox, Opera or Safari. These are usually or always crawlers, the breakdown of them was as follows.
Browser2 | n |
|---|---|
http://ahrefs.com/robot/ | 159 |
https://developers.facebook.com/docs/sharing/webmasters/crawler | 8 |
Netscape.0 (X11 | 4 |
Netscape.0 -? | 4 |
Netscape.0 (iPhone; CPU iPhone OS 18_1_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [FBAN/FBIOS;FBAV/493.0.0.43.104;FBBV/693509315;FBDV/iPhone14,5;FBMD/iPhone;FBSN/iOS;FBSV/18.1.1;FBSS/3;FBCR/;FBID/phone;FBLC/sv_SE;FBOP/80] -? | 2 |
Netscape.0 (iPhone; CPU iPhone OS 18_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.4037 -? | 2 |
Netscape.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.3937 -? | 1 |
Netscape.0 (iPhone; CPU iPhone OS 18_6_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.4037 -? | 1 |
Renaming “N”etscape.0 (iPhone; CPU iPhone OS 18_1_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [FBAN/FBIOS;FBAV/493.0.0.43.104;FBBV/693509315;FBDV/iPhone14,5;FBMD/iPhone;FBSN/iOS;FBSV/18.1.1;FBSS/3;FBCR/;FBID/phone;FBLC/sv_SE;FBOP/80] -?" to “Netscape.0 (iPhone; CPU iPhone OS 18_1_1 like Mac OS X)” makes things more readable.
I am a little bit interested in when these crawlers come and go so …
Browser2 | firstSeen | lastSeen |
|---|---|---|
http://ahrefs.com/robot/ | 2024-11-30 | 2026-04-17 |
https://developers.facebook.com/docs/sharing/webmasters/crawler | 2025-01-08 | 2026-04-09 |
Netscape.0 (iPhone; CPU iPhone OS 18_1_1 like Mac OS X) | 2025-02-10 | 2025-02-10 |
Netscape.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.3937 -? | 2025-08-13 | 2025-08-13 |
Netscape.0 (iPhone; CPU iPhone OS 18_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.4037 -? | 2025-08-13 | 2025-08-17 |
Netscape.0 (iPhone; CPU iPhone OS 18_6_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.4037 -? | 2025-08-22 | 2025-08-22 |
Netscape.0 (X11 | 2025-12-04 | 2025-12-04 |
Netscape.0 -? | 2026-01-09 | 2026-04-15 |
This shows the map against time, size shows number per day.
For what it’s worth, here are the numbers per day.
Other browser | date | nPerDay |
|---|---|---|
Netscape.0 (X11 | ||
2025-12-04 | 4 | |
Netscape.0 (iPhone; CPU iPhone OS 18_1_1 like Mac OS X) | ||
2025-02-10 | 2 | |
Netscape.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.3937 -? | ||
2025-08-13 | 1 | |
Netscape.0 (iPhone; CPU iPhone OS 18_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.4037 -? | ||
2025-08-13 | 1 | |
2025-08-17 | 1 | |
Netscape.0 (iPhone; CPU iPhone OS 18_6_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [LinkedInApp]/9.31.4037 -? | ||
2025-08-22 | 1 | |
Netscape.0 -? | ||
2026-01-09 | 1 | |
2026-01-13 | 1 | |
2026-02-16 | 1 | |
2026-04-15 | 1 | |
http://ahrefs.com/robot/ | ||
2024-11-30 | 1 | |
2024-12-01 | 1 | |
2024-12-13 | 2 | |
2024-12-14 | 5 | |
2024-12-18 | 1 | |
2024-12-24 | 1 | |
2024-12-31 | 1 | |
2025-01-01 | 2 | |
2025-01-05 | 1 | |
2025-01-11 | 1 | |
2025-01-15 | 2 | |
2025-01-16 | 1 | |
2025-01-21 | 1 | |
2025-01-26 | 1 | |
2025-01-31 | 1 | |
2025-02-02 | 1 | |
2025-02-06 | 1 | |
2025-02-11 | 1 | |
2025-02-14 | 1 | |
2025-02-16 | 1 | |
2025-03-06 | 1 | |
2025-03-18 | 1 | |
2025-03-20 | 1 | |
2025-03-21 | 1 | |
2025-03-24 | 1 | |
2025-03-29 | 1 | |
2025-04-06 | 1 | |
2025-04-08 | 1 | |
2025-04-13 | 1 | |
2025-04-18 | 1 | |
2025-04-22 | 1 | |
2025-04-23 | 1 | |
2025-04-24 | 1 | |
2025-04-28 | 1 | |
2025-05-12 | 2 | |
2025-05-17 | 1 | |
2025-05-25 | 2 | |
2025-05-26 | 2 | |
2025-06-19 | 1 | |
2025-06-25 | 1 | |
2025-06-26 | 3 | |
2025-06-27 | 2 | |
2025-07-02 | 1 | |
2025-07-05 | 1 | |
2025-07-10 | 1 | |
2025-07-15 | 1 | |
2025-07-17 | 1 | |
2025-07-25 | 1 | |
2025-07-26 | 3 | |
2025-07-28 | 2 | |
2025-07-30 | 1 | |
2025-08-02 | 1 | |
2025-08-04 | 1 | |
2025-08-08 | 2 | |
2025-08-13 | 1 | |
2025-08-15 | 1 | |
2025-08-18 | 1 | |
2025-08-29 | 2 | |
2025-08-31 | 2 | |
2025-09-05 | 1 | |
2025-09-11 | 1 | |
2025-09-16 | 1 | |
2025-09-20 | 1 | |
2025-09-25 | 1 | |
2025-09-29 | 1 | |
2025-10-02 | 4 | |
2025-10-03 | 1 | |
2025-10-23 | 1 | |
2025-10-28 | 2 | |
2025-11-04 | 8 | |
2025-11-05 | 2 | |
2025-11-09 | 1 | |
2025-11-14 | 1 | |
2025-11-18 | 1 | |
2025-11-24 | 1 | |
2025-11-25 | 2 | |
2025-11-29 | 2 | |
2025-12-04 | 1 | |
2025-12-08 | 2 | |
2025-12-09 | 2 | |
2025-12-13 | 1 | |
2025-12-17 | 1 | |
2025-12-22 | 1 | |
2025-12-26 | 1 | |
2025-12-29 | 1 | |
2025-12-30 | 1 | |
2025-12-31 | 1 | |
2026-01-04 | 1 | |
2026-01-08 | 1 | |
2026-01-09 | 2 | |
2026-01-12 | 1 | |
2026-01-13 | 1 | |
2026-01-17 | 1 | |
2026-01-22 | 1 | |
2026-01-26 | 1 | |
2026-01-31 | 2 | |
2026-02-10 | 1 | |
2026-02-12 | 1 | |
2026-02-16 | 1 | |
2026-03-03 | 1 | |
2026-03-04 | 2 | |
2026-03-08 | 1 | |
2026-03-13 | 1 | |
2026-03-14 | 1 | |
2026-03-18 | 3 | |
2026-03-22 | 1 | |
2026-03-26 | 1 | |
2026-03-27 | 1 | |
2026-03-31 | 1 | |
2026-04-03 | 1 | |
2026-04-05 | 1 | |
2026-04-06 | 1 | |
2026-04-07 | 1 | |
2026-04-10 | 1 | |
2026-04-14 | 2 | |
2026-04-17 | 3 | |
https://developers.facebook.com/docs/sharing/webmasters/crawler | ||
2025-01-08 | 1 | |
2025-01-09 | 2 | |
2025-04-23 | 1 | |
2026-02-15 | 2 | |
2026-03-26 | 1 | |
2026-04-09 | 1 |
Browser versions
I can’t think it matters but here is the breakdown with the version numbers as well as the browser name.
Browser | n |
|---|---|
Chrome 131 | 531 |
Chrome 138 | 435 |
Chrome 136 | 415 |
Chrome 130 | 407 |
Chrome 140 | 405 |
Safari 18 | 366 |
Chrome 134 | 354 |
Chrome 132 | 345 |
Chrome 142 | 317 |
Chrome 135 | 286 |
Chrome 129 | 271 |
Chrome 133 | 258 |
Chrome 141 | 242 |
Chrome 146 | 228 |
Chrome 125 | 221 |
Chrome 128 | 217 |
Safari 17 | 188 |
Chrome 139 | 184 |
Safari 537 | 184 |
Chrome 137 | 181 |
Chrome 144 | 167 |
Chrome 126 | 149 |
Chrome 143 | 135 |
Firefox 125 | 132 |
Chrome 145 | 131 |
Chrome 127 | 130 |
Firefox 131 | 121 |
Chrome 124 | 113 |
Firefox 133 | 102 |
Firefox 130 | 90 |
Chrome 122 | 85 |
Firefox 132 | 85 |
Firefox 128 | 80 |
Safari 26 | 80 |
Firefox 129 | 74 |
Chrome 123 | 70 |
Firefox 124 | 69 |
Chrome 101 | 67 |
Safari 16 | 58 |
Safari 604 | 51 |
Firefox 123 | 44 |
Firefox 126 | 44 |
Firefox 146 | 43 |
Chrome 86 | 38 |
Firefox 122 | 34 |
Firefox 127 | 34 |
Firefox 142 | 33 |
Chrome 147 | 30 |
Firefox 148 | 29 |
Chrome 103 | 28 |
Firefox 138 | 28 |
Chrome 100 | 27 |
Chrome 121 | 27 |
Firefox 134 | 27 |
Chrome 104 | 22 |
Chrome 120 | 21 |
Opera 120 | 20 |
Chrome 102 | 19 |
Firefox 135 | 18 |
Firefox 140 | 18 |
Chrome 79 | 17 |
Firefox 147 | 17 |
Firefox 149 | 17 |
Chrome 119 | 16 |
Firefox 137 | 16 |
Safari 15 | 16 |
Firefox 136 | 15 |
Firefox 141 | 14 |
Firefox 144 | 13 |
Firefox 145 | 13 |
Firefox 115 | 12 |
Opera 117 | 11 |
Firefox 143 | 10 |
Firefox 119 | 9 |
Chrome 116 | 7 |
Firefox 139 | 7 |
Opera 123 | 6 |
Chrome 109 | 5 |
Chrome 112 | 5 |
Chrome 4 | 5 |
Opera 115 | 5 |
Opera 122 | 5 |
Safari 14 | 5 |
Chrome 106 | 4 |
Opera 118 | 4 |
Chrome 107 | 2 |
Chrome 114 | 2 |
Chrome 117 | 2 |
Chrome 148 | 2 |
Chrome 94 | 2 |
Chrome 98 | 2 |
Firefox 102 | 2 |
Opera 109 | 2 |
Opera 113 | 2 |
Opera 124 | 2 |
Safari 13 | 2 |
Chrome 108 | 1 |
Chrome 110 | 1 |
Chrome 111 | 1 |
Chrome 115 | 1 |
Chrome 41 | 1 |
Chrome 52 | 1 |
Chrome 53 | 1 |
Chrome 54 | 1 |
Chrome 55 | 1 |
Chrome 58 | 1 |
Chrome 90 | 1 |
Chrome 99 | 1 |
Firefox 109 | 1 |
Firefox 59 | 1 |
Firefox 68 | 1 |
Opera 114 | 1 |
Opera 119 | 1 |
Durations of sessions
A bit more interesting is the durations of the sessions.
Some sessions don’t have a recorded termination time, currently that’s true for 2245, i.e. 24.4% of the sessions. This could include occasional session still active at the time at which the copy of the database was pulled. However, I think most will be where someone leaves the session open. I have capped the sessions at one hour in the analyses below.
Here are the descriptive statistics.
name | nNA | nOK | min | lqrt | mean | uqrt | max |
|---|---|---|---|---|---|---|---|
durMinsAll | 2,245 | 6,968 | 0.0 | 1.0 | 48.9 | 26.0 | 9,564.0 |
durMinsCapped | 2,245 | 6,968 | 0.0 | 1.0 | 16.6 | 26.0 | 60.0 |
durMinsCensored | 3,350 | 5,863 | 0.0 | 1.0 | 8.5 | 11.0 | 60.0 |
durMinsAll includes all the sessions so far, durMinsCapped treats all sessions recorded as lasting 60 minutes as such, more realistically, durMinsCensored ignores those sessions assuming that they were abandoned sessions. (This shows a maximum duration of 60 minutes as session durations were measured to a fraction of a second so any duration of over 59’30" and less than 60’0" is rounded up to 60 minutes and counted as a genuine 60 minutes!).
Most of the sessions, as you would expect given the nature of the apps, are sessions lasting only a few minutes. If I use the censoring and ignore all the sessions that lasted more than an hour on the plausible assumption that they were abandoned sessions rather than someone continuing to try different parameters for any app for more than an hour then there have been 5863 such sessions so far. Of these 292 lasted under a minute. I guess it’s possible to launch an app and get useful output if only wanting the default parameters in under a minute but I think it would be rare so I think we can regard these as “just looking” sessions and they represent 5% of the 5863 uncensored sessions.
The number of sessions lasting a minute (rounding to the nearest minute) was 2809, i.e. 47.9% of the uncensored sessions. I think these probably represent very quick but perhaps genuine uses of an app.
That leaves 2762 sessions lasting longer than a minute but less than an hour i.e. 47.1% of the uncensored sessions, I think these can be regarded as sessions in which someone entered parameters and perhaps played around with different parameters and perhaps noted or pulled down outputs