Not every interface you build will be distributed through an app store. For web applications, "publication" means deploying your code to a server that the public can reach, attaching a domain name to it, securing it with HTTPS, and keeping it updated as you continue to make changes. This topic walks through the practical choices involved: where to host (managed platforms, static site hosts, or your own virtual private server), how to automate builds and deployments, how domains and SSL certificates are configured, what it takes to ship a Progressive Web App, and how performance and SEO affect whether people actually find and stay on your site.
These concerns matter in this course because the usability work you do is only visible to users once the project is live, fast, and trustworthy. A slow first load, a browser warning about an insecure connection, or a broken deploy undoes a lot of careful interface design. Deployment also changes how you work: once a build pipeline is in place, pushing a change to a repository can automatically test and publish it, which shortens the loop between user feedback and the fix.
The three videos below demonstrate three different points on the hosting spectrum, from fully managed to fully self-administered. While watching, pay attention to what each platform does for you automatically versus what you must configure yourself — especially the steps around connecting a Git repository, setting a build command, pointing a custom domain, and provisioning a certificate. Also notice how each workflow would handle a second, third, and fiftieth deployment, since that repeatability is the real point of continuous deployment.
An episode of Firebase Fundamentals in which David East walks through setting up Firebase Hosting for a web project and then wiring it to GitHub Actions so that deployments happen automatically. Expect coverage of the Firebase CLI, initializing hosting in a project directory, and the generated workflow that builds and publishes on a push or pull request. It illustrates the managed-platform end of the hosting spectrum, where HTTPS and a CDN are handled for you.
It comes directly from the Firebase team, so the tooling and commands shown are authoritative, and it connects two subtopics at once — hosting platforms and continuous deployment through a build pipeline.
Coder Coder demonstrates deploying a site built with HTML, CSS, and JavaScript to Cloudflare Pages using a GitHub repository as the source. The walkthrough covers linking the repo, configuring the build, and getting a live URL at no cost, with Cloudflare's network handling delivery and TLS. It is a good model of the static-hosting approach suited to front-end projects and class prototypes.
The channel is known for clear, beginner-friendly front-end instruction, and the free tier makes it realistic for student projects while still demonstrating Git-triggered deployment and platform-managed SSL.
Tony Teaches Tech shows how to launch a website on a DigitalOcean virtual private server using Nginx, starting from an empty machine. The tutorial is aimed at people who have never administered a server, so it covers creating the instance, serving files through a web server, and the manual steps that managed platforms abstract away.
It supplies the contrast the other two videos need: seeing the server-level work required makes the trade-offs between control, cost, and convenience in hosting and domain/SSL configuration concrete.
These videos extend the module's publication theme beyond the Apple App Store and Google Play Store by showing what release looks like on the open web, which helps you compare submission-and-review distribution against self-publishing (MO1). Evaluating your own interface project for readiness means more than meeting store guidelines — it also means confirming it builds cleanly, deploys reliably, and loads over HTTPS, and the Firebase and Cloudflare walkthroughs give you a repeatable pipeline to test that against (MO2). Finally, the deployment URLs, custom domains, and live demos produced by these workflows become part of the asset package you present alongside metadata and screenshots when you submit or showcase the project (MO3).
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.