Before, RWS was launched with a launch file, which included bringing up a websocket server. Now, RWS is served automatically through Apache, so it doesn't bring up anything.

Perhaps as a little (x) icons that appear next to apps that are open.

This would just shut down the bringup.launch.

Only allow one person to use the robot at a time. If a user logs in while another user has the robot, then they will see a waiting screen, showing who is using the robot. They can have the option of stealing the robot. If the robot is free, then they skip the waiting screen and go straight to the app.

If a robot is stolen from a user, then the next time that user navigates to a page, they should be redirected to the waiting screen. The site could also periodically check whether the current user still has a claim on the robot (once every ~1-2 minutes).

• There is always a menu ("hamburger") button in the top toolbar
• If the viewport is large, the side nav appears by default, but can be hidden by tapping the menu button
• If the viewport is small, the side nav is hidden by default, but can be shown/hidden by tapping the menu button

See if there's a way for apps (within their iframes) to update the URL bar as the user navigates through an app. If a URL is accessed directly, then RWS should pass the data to the app, which can handle it.

Story

• User opens app, URL bar is robot.com/app/code_it
• User opens a CodeIt! program, URL bar is robot.com/app/code_it/1234
• User shares the URL with someone else
• Second user loads that URL. RWS loads CodeIt! and passes the /1234 part of the URL to the app
• The app decides to open program ID 1234

Possibly retry connecting to the websocket server automatically with random exponential backoff.

After starting the web server with sudo apache2ctl stop and sudo apache2ctl start, the first time you visit the website, the bringup will fail with a run_id on parameter server does not match declared run_id error. The second time you load the webpage, the bringup works, however.