## Web apps without rolling your own server

• Most basic: GitHub Pages (web app must be *rendered* to html, hence quarto)

• Streamlit map -- benefits: write directly in Python without worrying about compilation to html via quarto; using GSheets as DB, but also many many drawbacks of streamlit

• Live coding: make the basics of the map app [sidebar, main window, sl.Map(), Geocoding API

• Vercel + Next.js: Pre-caching views

• ^For those, talk about *pre-loading* all of the possible views -- for example, if they're visualizing 50 states, they can pre-render those 50, at urls like /al, /az, etc

## Cloud functions

• Sort of "halfway" between above web apps and below full-server solutions

• Talk about how GCS is kind of a "hack" for replacing actual storage space on server

## Web apps *with* your own server

• Flask! Bridges the gap between Cloud functions and... Apache

• Obvious disadvantage: cost (but same with cloud functions)

• Advantages of own server: pretty much everything with domains, for example with GH Pages I can't do map.jjacobs.me

• Live coding: Flask app, hello world but also with parameters; reasons to use GET vs POST

• How does it help with viz? Show app with big data file on HDD, loaded dynamically via GET request to Flask app!