Make menu on deployed apps optional/configurable

[michaelterryio]

Can we make the fox¹ menu on deployed apps optional or configurable?

For some use cases I'm not worried about the Livebook logo itself, just the menu.

I have a couple immediate use cases where I find the menu tricky:

1. Deploying apps to my internal users

   These users are not developers and will find it confusing and distracting.

   The users are technical and I envision a path to having them integrated into full Livebook workflows, but as it stands, it will likely hinder adoption.

2. Public demos

   I have in mind a public demo of an app that Livebook is great for. There's a decent chance it gets some traction and this menu doesn't fit.

   The Livebook logo/branding is fine itself for this project. I don't mind promoting Livebook alongside – might even add a little to the virality – but the menu/menu contents I'd dispense with in this case.

3. Commercial screens #later

   Not an immediate need, but eventually I'd like to be able to remove/replace the logo altogether.

   The way Livebook is heading, I see great utility as a rapid application development toolkit for data apps. Lots of public and even commercial apps don't need infinite style/layout flexibility. But in these cases it would be essential to wrap screens in my own branding.

Footnotes

1. Is it a fox? ↩