# New games, apps, and importing her web projects

The reusable starter is a tiny native Android WebView hosting **local bundled files** at `https://chloe.local/`. Its touch game is a working example, not an installed third game. Chloe can change its HTML/CSS/JS or replace it with an existing web build. No server is needed for bundled play. Online APIs still require connectivity and their own server-side secrets.

New project:

```sh
node developer/skill/chloe-os/scripts/chloe.mjs new-game moon-notes
node creations/moon-notes/build.mjs
node developer/skill/chloe-os/scripts/chloe.mjs install dev.chloe.creations.moonnotes creations/moon-notes/app.apk
```

Import a web app: run its own build first. The result must be a static folder containing `index.html` and its referenced assets. Use relative asset URLs or `/` paths supported by the local host. A Next.js server, backend route, cloud database or API key does not turn into an offline app just by copying a folder.

```sh
node developer/skill/chloe-os/scripts/chloe.mjs import-web moon-notes /absolute/path/to/web/dist
node creations/moon-notes/build.mjs
```

The importer refuses an existing project, symlinks and credential-like files. It copies only your selected static output, never the whole source repository. The generated app has its own package ID and save storage; keep those stable for updates. Edit `creations/SLUG/assets/www/`. It supports JavaScript, touch, localStorage and screen rotation. It does not expose a native JavaScript bridge or grant arbitrary local-file access. Links leaving `chloe.local` open in the browser.

For a new **native** game, choose an appropriate engine rather than forcing it into this starter. Reuse the installed art and controls, assign a new `dev.chloe.creations.*` package, and build for the JM21's touch screen and Android 13. Test on actual 750×1334 hardware; tiny desktop keyboard controls are not enough.

After installing, drag the new app into Creations on the launcher. Do not replace her other creations. For music-reactive visuals, use the existing media notification bridge in the companion; Spotify downloads remain inside Spotify, not raw audio files readable by this wrapper.