[dbecker]

Streamlit is awesome.

It's nicer than sending someone static results, and it isn't much more effort.

And vastly better than sending a notebook to someone unless you expect them to modify the notebook a lot.

And learning time to make Streamlit useful for a small internal apps is probably ~15 minutes for most people.

[IanCal]

I can't emphasise enough what you put here:

> And learning time to make Streamlit useful for a small internal apps is probably ~15 minutes for most people.

For the types of things streamlit works for, it's minutes to learn and can be just minutes to write a useful app.

[Jugurtha]

Yes. We use it for our own. We started however with a concept of AppBook[0] for the very "academic type" who couldn't even write a Streamlit app. We'd automatically take a notebook and parametrize it (no metadata or the user tagging cells), then present a form with the parameters. We'd then run it and track the experiment, and log the model.

Now, however, as some of our internal users are comfortable with writing Streamlit, we're directly deploying apps from the notebook. It's useful to show results to clients without the user having to set up a VM, upload stuff, Docker, authentication, resources, etc.

It's not really the 15 minutes it takes one individual to learn. It's the SSH into something, send a link, shut down the VM or recycle it for next proto, remember the IP, etc...

- [0]: https://iko.ai/docs/appbook/