Aeon is built to reach out to various platforms, gather data, store it and then report it to the user. This page will go into detail into how these goals are worked out technically.
Aeon is built on Electron, and leverages its integration with browsers heavily to use existing data download workflows to gather data. Electronc consists of a NodeJS back-end (called main in Electron parlance and the Aeon codebase) coupled with a Chromium front-end (dito, called app). You'll find that the codebase is neatly seperated along these lines, with the src/main folder containg all back-end code and the src/app folder containing all front-end code.
Following Electron best-practices, these environments run seperately and are sandboxes, to prevent external webpages from getting system-level access through NodeJS. This means that communication between the front-end and back-end happens through a set of bridges (for example, see the RepositoryBridge and the app-side Repository utility). All front-end calls to the back-end should go through these bridges to ensure security. Additionally, the preload file specifies some unique cases where the front-end has access to back-end methods.
In order to version incoming data, Aeon builds and updates a local Git repository that is bundled with the application. Aeon interfaces with this repository through NodeGit, a set of NodeJS bindings for the widely used libgit2 library. All interfacing with the repository is done in NodeJS, though there is a bridge available for calling certain functions from the front-end.
The first point of Aeon is making sure data is retrieved from a series of sources. These sources are abstracted into Providers. In Aeon, a Provider is a binding for a particular platform (e.g. Facebook, Instagram, LinkedIn) that can directly pull data, initiate data requests, download data and parse data. For more detailed info on the inner workings of providers, and how to write one, find the particular page.