example.json

example.json

[
  {
    "server": "198.199.101.152",
    "server_port": 8388,
    "password": "u1rRWTssNv0p",
    "method": "aes-256-cfb",
    "remarks": "Example 1"
  },
  {
    "server": "198.199.101.12",
    "server_port": 8388,
    "password": "u1rRWTssNv0p",
    "method": "aes-256-cfb",
    "plugin": "v2ray",
    "plugin_opts": "host=www.example.com",
    "remarks": "Example 2",
    "route": "bypass-lan-china",
    "remote_dns": "dns.google",
    "ipv6": true,
    "metered": false,
    "proxy_apps": {
      "enabled": true,
      "bypass": true,
      "android_list": [
        "com.eg.android.AlipayGphone",
        "com.wudaokou.hippo",
        "com.zhihu.android"
      ]
    },
    "udpdns": false
  },
]

Should we remove nonstandard JSON fields, at least from one of the profiles?

Yeah, you're right. Let me update the file.

@madeye @Mygod
Thanks for adding online server subscription.
How to define the SIP003 plugin in the JSON config file?
Also, it will be great if you can add description for all the fields.

    "ipv6": true,
    "metered": false,
    "remarks": "Example 2",

    "route": "bypass-lan-china",
    "route": "all",

Duplicated in the second profile

There are some config is system wide, I'd prefer put all config into object instead of array.

{
  "servers": [
    {
      "server": "198.199.101.152",
      "server_port": 8388,
      "password": "u1rRWTssNv0p",
      "method": "aes-256-cfb",
      "remarks": "Example 1"
    }
  ],
  "pacUrl": "https://www.example.com/pac",
  "proxy": {
    "proxyType": "http",
    "proxyServer": "http://proxy.example.com",
    "proxyPort": 80
  }
}

This file is moved to https://github.com/shadowsocks/shadowsocks-android/blob/master/.github/doc-json.md.

@studentmain This file is only meant to represent what fields shadowsocks-android expects from the subscription file. Feel free to extend it, as described in the documentation above.