And is there somewhere a documentation on the format/structure used there, or does one need to reverse-engineer it? For example:
- it’s a JSON (obviously) object with the properties
packages (that all?)
repo is an object with the properties … (well, this part is easy to reverse engineer)
apps is an array of apps, each item having the properties … and here it’s getting a bit difficult, as some of those properties are optional (e.g.
localized and what might be in there)
requests is an object holding the arrays
uninstall (apps suggested by the repo to be automatically installed/uninstalled) – but how do those arrays look like when filled? A guess would be it’s just package names.
packages are the available
.apk files with their properties. Again, some of them seem to be optional (e.g. the
uses-permission array is completely missing (not empty, missing) if an app doesn’t request any permission)
So this bullet-pointed list is just a very incomplete “quick glance”. I’m missing a complete reference (yes, I searched already, which is why I landed here). This reference would be of primary interest for folks building their own clients (like the WebIf of my repo, which currently is still based on the XML index). I’d say there must be a reference somewhere, or did you tackle the client (and website) blindly?