# Shiny for Julia \[work in progress, early request for feedback\]

**URL:** <https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038>\
**Category:** Web Stack\
**Tags:** webapps\
**Created:** [August 25, 2018, 1:59pm UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038 "2018-08-25T13:59:33Z")\
**Posts on this page:** 11\
**Page:** 2

<div class="post-metadata">

**Author:** ![xiaodai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xiaodai/32/15937_2.png) [@xiaodai](https://discourse.julialang.org/u/xiaodai)\
**Post date:** [January 23, 2019, 10:41pm UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/21 "2019-01-23T22:41:17Z")

</div>

> [@essenciary](#):
>
> “Publish” button that would automatically set it up.

I love that feature from RStudio. What’s missing with [shinyapps.io](http://shinyapps.io) is an easy and inexpensive way to host it on your domain!

> [@essenciary](#):
>
> What do you think of the Predix-UI components?

> [@essenciary](#):
>
> Definitely, this is low level - but it made sense to start with the basics

I was a heavy Shiny user and I created one of the first [popular Shiny extensions in shinysky](https://github.com/analytixware/shinysky). This is my 2 cents, we definitely a low-level layer that doesn’t assume any framework or UI components. Shiny was based on jQuery and Bootstrap, but that made extending shiny much harder. On the other hand, we need high level contructs that wraps some library to get started. So if shiny was broken up into a low-level Shiny that you can use any framework with and a ShinyBootstrapjQuery then it would be fine. Julia shouldn’t make the same mistakes.

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [January 24, 2019, 8:11am UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/22 "2019-01-24T08:11:12Z")

</div>

Thanks for the feedback. It’s something that I spent a lot of time thinking about lately.

Architecture wise it seems to me that the best approach would be web components. It’s a mature technology that now has been embraced by all browser vendors - and it doesn’t lock the user into any framework. A web component is a complex UI element which encapsulates all the functionality and which looks like a regular HTML element: a tag with attributes. This would allow users to a) use any of the existing components; b) build and distribute their own; c) write framework agnostic code which can be coupled with any frontend framework.

Then there’s, of course, the issue of coupling these, auto-magically, with the Julia backend, for 2-way communication, managing state, etc.

Re [shinyapps.io](http://shinyapps.io) - yes, 300/mo for your own domain is a bit expensive. I guess their reasoning is that you only need that once your app is ready to make money.

---

<div class="post-metadata">

**Author:** ![aalexandersson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aalexandersson/32/2927_2.png) [@aalexandersson](https://discourse.julialang.org/u/aalexandersson)\
**Post date:** [February 1, 2019, 10:07pm UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/23 "2019-02-01T22:07:11Z")

</div>

Web components sound good but a bit vague to me. In the case of Polymer, is your idea now still version 2, or rather version 3, or even LitElement and Material Web Components, or something different than Polymer?

[https://www.polymer-project.org/](https://www.polymer-project.org/)

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [February 4, 2019, 9:55am UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/24 "2019-02-04T09:55:35Z")

</div>

Short term objectives are

1. support all Predix-UI components
2. Interact.jl support
3. support for WebIO

---

<div class="post-metadata">

**Author:** ![mkborregaard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkborregaard/32/556_2.png) [@mkborregaard](https://discourse.julialang.org/u/mkborregaard)\
**Post date:** [February 4, 2019, 10:25am UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/25 "2019-02-04T10:25:43Z")

</div>

Is there anywhere to go and look at the current state of this? Sounds like a potentially really important project.

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [February 4, 2019, 10:38am UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/26 "2019-02-04T10:38:57Z")

</div>

At the moment the project lives mostly in my head. I’m working on design and architecture plus early experiments. The plan is to get a working prototype by June to present at JuliaCon.

---

<div class="post-metadata">

**Author:** ![Diego\_Javier\_Zea](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/diego_javier_zea/32/1858_2.png) [@Diego\_Javier\_Zea](https://discourse.julialang.org/u/Diego_Javier_Zea)\
**Post date:** [August 2, 2019, 6:12pm UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/27 "2019-08-02T18:12:07Z")

</div>

Hi @essenciary ! Is there any update on this? Thanks!

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [August 13, 2019, 8:54am UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/28 "2019-08-13T08:54:36Z")

</div>

@Diego_Javier_Zea Nothing to show yet, I’m afraid. ATM the focus is on getting Genie to v1 (which should happen in a few weeks) to have a stable foundation. Once that’s done, the focus will be on applications. There are a few projects in the pipeline, including “Shiny for Julia”, GenieCloud (for deploying web apps), and a static website generator.

---

<div class="post-metadata">

**Author:** ![asprionj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/asprionj/32/6856_2.png) [@asprionj](https://discourse.julialang.org/u/asprionj)\
**Post date:** [September 1, 2019, 8:53pm UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/29 "2019-09-01T20:53:41Z")

</div>

Concerning a static-site generator: are you aware of [JuDoc](https://github.com/tlienart/JuDoc.jl)?

---

<div class="post-metadata">

**Author:** ![AmburoseSekar](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/amburosesekar/32/13812_2.png) [@AmburoseSekar](https://discourse.julialang.org/u/AmburoseSekar)\
**Post date:** [April 14, 2020, 10:10pm UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/30 "2020-04-14T22:10:29Z")

</div>

I’m New to Julia, Compiler Design is well planned and Advanced. last one month i have search Package in Hybrid-App for high-performance numerical analysis and computational science. We Need,

1. Best Interaction of Input from HTML  
Interact Widget & WebIO it’s fantastic, but missing filepicker and not fully customizable  
Knockout used for well Data-binder

2. Easy to link with Core  
Julia

3. Best Visualization  
Interact with PlotlyJS is really better performance. but we need more output display other than graphs

4. Support High-Level MVC  
Genie.jl is a high level Web-framework but missing Interact like works.

Thanks for @essenciary @piever and web-stack developers in Julia.

is any updates or suggestion? Most Welcomes 🙂

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [April 15, 2020, 3:51pm UTC](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038/31 "2020-04-15T15:51:34Z")

</div>

Actively working on Stipple, an interactive/reactive UI layer on top of Genie. Here is more info:

> [@Stipple: Reactive data dashboards with Julia \[WIP\]](https://discourse.julialang.org/t/stipple-reactive-data-dashboards-with-julia-wip/37291/8):
>
> They will do the same thing, but the way they do it is different. Dashboards.jl / Dash.jl is about adding Julia as a Dash backend. Stipple is about building and publishing interactive data dashboards with Julia (just like Genie, building a truly native Julia experience). And this difference, I think, is fundamental: I’m focusing (read obsessing) on architecting an efficient, terse, readable, pleasant Julia API. As the resulting frontend is abstracted away, the Julia API is the frontend for the…

Milestone for MVP/beta is JuliaCon - hopefully we’ll have a chance to release it there!

[Previous page](https://discourse.julialang.org/t/shiny-for-julia-work-in-progress-early-request-for-feedback/14038.md?page=1)