> For the complete documentation index, see [llms.txt](https://cloudinary.gitbook.io/cloudy-cam/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloudinary.gitbook.io/cloudy-cam/creating-a-production-build-and-auditing-pwa.md).

# Creating a Production Build and Auditing Your PWA

To serve your app in production mode as a PWA to users, first edit the CloudyCam manifest to read like this:

```
    # public/manifest.json
    {
        "short_name": "CloudyCam",
        "name": "Clodinary Offline PWA Camera",
        "icons": [
            {
                "src": "favicon.ico",
                "sizes": "512x512 192x192 64x64 32x32 24x24 16x16",
                "type": "image/x-icon"
            }
        ],
        "start_url": "./index.html",
        "display": "standalone",
        "theme_color": "#000000",
        "background_color": "#ffffff"
    }
```

Recall that the `index.js` file contains this line of code:

```
    registerServiceWorker();
```

It creates a service worker that caches the various assets and sections of your app so that even when your users are offline or have a poor Internet connection, they can still interact with and use CloudyCam.

Create a production build by running this command:

```
    yarn build # or npm run build
```

Yarn then creates an optimized production build of your app and places it in the `build` directory, ready for your users.

Serve the production build with the `serve` JavaScript package by running these two commands:

```
    yarn global add serve # or npm install -g serve
    serve -s build
```

Afterwards, Yarn creates a simple static server on `http://localhost:5000`. Go to that URL for the production version of your app.

A panel on **Google Chrome’s Developer Console**, powered by [Lighthouse](https://developers.google.com/web/tools/lighthouse/), enables you to validate the quality of your web pages. Click the **Audits** tab of the **Developer Console** and run an audit on the production build. The results are then displayed, as in this example:

![Results of a Lighthouse PWA Audit (1)](https://3486782044-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQxqjHiNgHCfPtd6mkQ%2F-LRAT_zQ5FlwNEB6AZHt%2F-LRAYCp_u8dSIpI3FPk3%2Fcl-13.png?alt=media\&token=6d012143-4251-4258-ae71-ae2480c42fb7)

![Results of a Lighthouse PWA Audit (2)](https://3486782044-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQxqjHiNgHCfPtd6mkQ%2F-LRAT_zQ5FlwNEB6AZHt%2F-LRAYO2EG6QuAdaemPi8%2Fcl-14.png?alt=media\&token=c9fe0873-8ed9-4725-93de-5d98caf0a3aa)

Here, CloudyCam is shown as a 100-percent PWA even though the score reads 92. Not to worry: The remaining 8 percent will be achieved once your production server is running with HTTPS for all the app traffic.