Nativefier catalog is a catalog of configs for nativefier apps. It currently stores app configs as a json file with the following structure:

{
 "app-token": {
   "name": "App Name",
   "targetUrl": "https://appurl.example/",
   "counter": true,
   "bounce": true
 }
}

The options are passed directly to the nativefier Programmatic API.
The UI is built using enquirer autocomplete prompts and shows a searchable list of available app configs.

I also could make a graphical way of viewing it to go along with my nativefier-gui project.

The json file is curently stored in the same repo as the code but should probably be moved to a different repo to seperate app adition prs from code pr like how Homebrew/brew (package manager code) is separate from Homebrew/homebrew-core (package repo). Having a repo of just configs could allow multiple different clients to all access it and share the same configs. (the default nativefier cli (see question 3), nativefier-catalog cli, nativefier-gui, something else?... )

Questions

1. Should this integrate with the existing nativefier-icons repo somehow?

2. Should there be a folder for userscripts to go along with apps.json or should they be linked as gist urls?

3. Should there be some kind of url (regex?) matching so the configs are used by default on the standard nativefier cli? (eg. use counter by default on gmail because the gmail entry in apps.json has counter enabled.

Any other ideas? Comments? Questions? Different directions?

@ronjouch @TheCleric