Gain insights into building real-time web apps with Phoenix LiveView. Learn about creating interactive code, building a game from scratch, and managing distributed real-time dashboards.

Programming Phoenix LiveView by The Pragmatic Programmer_468 x 60 copy.png

liveview.tar.gz

Installation

LiveView_Sockets

Simple_App

Wrong_Guess_Number

Plug_Conn

Wrong_Guess_Number-auth

Wrong_Guess_Number-auth-gen

Wrong_Guess_Number-auth-gen-final

Generator

Generator-ecto

Generator-ected

Generator-web-ected

Forms-ected

Forms

Stateless

Stateless-ected

Stateful

Stateful-ected

Dashboard

Dashboard-ected

Distributed_Dashboard

Distributed_Dashboard-ected

Unit_Test

Unit_Test-ected

Core-ected

Core

phoenix_start_server

phoenix_build_only

phoenix_build_only_pento

phoenix_build_intro

test

intro_build_ected

intro_build_server

auth_build_server

auth_build_ected

generate_web_build_ected

generate_web_build_server

generator_build_server

generator_build_ected

forms_build_server

setup

forms_build_edcted

interactive_build_server

interactive_build_ected

distributed_build_server

distributed_build_ected

stateless_build_server

stateless_build_ected

stateful_build_server

stateful_build_ected

test_build_server

test_build_ected

core_build_server

core_build_ected

graphics_build_server

graphics_build_ected

test_build_terminal

test_build_GUI

test_build_server-copy

test_build_server-copy-copy

test_build_server-chrome-fix

test_build_server-docker_fix

intro-tester

If you want to program just for the joy of creating, LiveView will be an excellent opportunity for you. This programming model keeps your brain firmly on the server and lets you explore one concept at a time. Layering on graphics makes this kind of exploratory programming almost magical.

Programmers learn by writing code, and that’s exactly how this course will work. We’ll work on a project together as if we’re a fictional game company. You’ll write lots of code, starting with small tweaks of generated code and building up to major enhancements that extract common features with components.

As you build the application, you’ll encounter more complexity. A distributed dashboard will show a real-time view of other users and processes. You’ll even build a game from scratch—because that’s the best way to learn how to layer the most sophisticated LiveView applications.

Building Real-Time Web Applications with Phoenix LiveView

The **Phoenix Live generator** is a utility that generates code supporting full CRUD functionality for a given resource. This includes the backend schema and context code, as well as the frontend code including routes, LiveView, and templates. Before we dive into using the generator, it’s worth discussing just what’s so great about this generated code in the first place. 

Phoenix Live generator provides us with a quick and easy way to build CRUD features, taking over the often tedious and repetitive work of building out this common functionality. It does so in a way that is adherent to best practices for organizing Phoenix code in general, and LiveView code specifically. This makes it easy for developers to build on top of—and customize—the generated code. The Phoenix Live generator is just one of many reasons why Phoenix and LiveView developers can be so highly productive.

Now that you understand what the Phoenix Live generator is and what it does for us at a high level, we’re ready to use it.

Let’s get started.

# How to run the Phoenix live generator

We’ll use the Phoenix Live generator to create a feature for managing products. If you are familiar with web development with Phoenix or even other languages, you know that many web libraries and frameworks have a concept called a `resource`. A resource is a collection of like entities. In this case, `Product` will be our resource.

Running the generator will give us all of the code needed to support the CRUD interactions for this resource. The generated frontend code, including the LiveViews, will reside in `pento/lib/pento_web`. Backend code, on the other hand, will live in `pento/lib/pento`. It will deal with database interactions with the schema and provide an API through which to manage those interactions, called the **context**.

When we’re done, we’ll have a schema for a `Product`, a `Catalog` context, along with the LiveViews for managing a product. As this figure demonstrates, all of these pieces of generated code will work together to make up the CRUD interactions for the Product resource.


Learn how to generate code using Phoenix Live Generator.

Phoenix Live Generator

Introduction

Phoenix and Authentication

Generators: Contexts and Schemas

Generators: Live Views and Templates

Forms and Changesets

Stateless Components

Stateful Components

Build an Interactive Dashboard

Build a Distributed Dashboard

Test Your Live Views

Build The Game Core

Render Graphics With SVG

Conclusion

Phoenix Live Generator

How to run the Phoenix