Identify which components to split into standalone parts

[zner0L]

We need to split https://github.com/baltpeter/thesis-mobile-consent-dialogs into different components to make a modular toolkit for mobile app analysis. To achieve this, we need to first identify, which parts are useful on their own.

[zner0L]

• [x] Platform-APIappstraction: An abstraction of common functions (e.g. starting an app, setting preferences) on all supported platforms (currently: Android and iOS)
• [x] TrackHAR: Takes a collection of requests and – using indicator matching and tracker adapters – returns a list of sent tracking data
• [x] parse-tunes: Analogous to parse-play, we need a script to read to charts of the iOS app store
• [x] hot-gluecyanoacrylate: Wrapper to orchestrate the separate parts for analysis
• [ ] consent-dialog-analysis: Maybe also separate the analysis of the consent dialogs into a module?

[baltpeter]

The first release of parse-tunes is done. It can fetch top charts and app details (including privacy labels).

[baltpeter]

I haven't created a release yet, but platform-api is now called appstraction and should be mostly ready for a 1.0.

[baltpeter]

cyanoacrylate and appstraction have both had their first releases last week.

[baltpeter]

An initial implementation of TrackHAR is also done, but not yet released.