embedding some resources in the app

One thing that may become handy over time would be to refer to some resources as local to the app, including: json, images, audio file, etc.

For some apps, the benefit of being local means

- less latency than a network call (with https setup time, even if cached etc.), so it may make the app more usable in spotty network conditions
- more responsive for things like audio files, icons, etc. (not real-time content)

This is not a requirement for me at the moment, but it may be worthwhile to explore. You could use a "file://....." path or something if that works, or even something special like "app-local://...."

PS: All that coupled with some smart caching, it could make apps even usable (partially or even fully) without network in some cases. But that's another topic altogether.

No files, tests, or entry points are identified in the issue. Start by locating the app's existing resource-loading path and clarify the scope for local JSON, images, and audio; completion would require an agreed local-resource mechanism and tests demonstrating that these resources load as intended.

Written by the indexing model from the issue text.