Shiny and #RStats friends, I’m thinking about a Shiny 201 or 301 workshop. Imagine you took Intro to Shiny, and you’ve made a few apps. You’re ready to learn the next thing to level up. What do you wish you had learned next?
@grrrck lately I’m learning more about web dev to better understand how shiny “works”. The goal is to not feel confined to prebuilt modules and components.
What about a workshop that teaches you how to build a custom component?
@jameshwade this is certainly right up my alley, but for the broader shiny user community, it’s probably a pretty advanced topic. Knowing a little CSS or JavaScript, plus a couple of ways to talk to the server from the browser can really go a long way though!
@milesmcbain managing complexity so your app can grow is a key topic! Do you have examples in mind when you think of shared state in large or growing apps?
@grrrck@milesmcbain for me it happens when I want user decisions to follow them across the app. Most commonly, these apps are translating a notebook workflow into page_navbar app.
@grrrck Making my apps available to users privately with shinylive (for free).
Context: For the last app I made, which had privacy restrictions, I had to teach the client how to run it in RStudio so they could use it independently of me; it worked out, but it wasn’t an ideal solution. I’m hoping shinylive could make private sharing more user friendly.
@mccarthymg This is interesting, thanks! In general, I'm hearing lots of "how do I deploy" or "how do I share" my app kinds of questions. The tooling for shinylive is just going to get better...
...but do you think this was a blocking point when you were learning Shiny? To me it feels like there were probably a few more steps between starting to learn Shiny and getting to the point of having clients with specific needs. What would have helped you get to this point faster?
@grrrck Welcome! I haven’t used Shiny much because of the difficulties deploying/sharing, so I’m excited to see what you’re introducing with shinylive!
I’m definitely not an expert, but I feel like Mastering Shiny gave me the core skills and knowledge I need to build something interesting and useful. A big pain point if I do use Shiny more in the future is how to scale up an app in terms of complexity/features.
[1/2] @grrrck I think the nitty gritty of the logistics & infrastructure of using #rshiny
i think most folks have a good grasp of coding, there are great resources out there to learn and more coming out to make it accessible for all kinds of people
to explain, the telos (read: τέλος; end, goal) of rshiny, if we think of rshiny as an organ (read: Ὄργανον; instrument, tool; thing doing the thing towards the end we want) is communication of information to some party...
@drommsen Can you recall any anti-patterns you've learned in your work? Where would it be useful to have patterns or templates to make your life easier?
@haraldkliems@brodriguesco This is pretty difficult, and I also agree it's more of a 501 (aka a Shiny grad course). For this to be really impactful to learn, you have to have a little more experience under your belt. What skills would get you to the point where you have to worry about how and where you deploy your Shiny apps, faster?
Add comment