<h2 style="color:red;">INTEGRATION TESTS!!</h2>

- [x] Project plan: Is this meeting supposed to discuss the project plan? Can the project plan be moved **HERE** for better tracking or to **github** or does the website allow for managing projects?
- [x] How to upload the project plan on the website? Do we have to inform someone if the project plan has been uploaded?
- [x] The goal is to import parts of the `aries-vcx` workspace and use them to draft an API that allows easy development of mobile apps? Using this API, we also develop an android example. Right?
- [x] If we are going to abstract some parts in the crate itself, why cannot we try and import everything into the `udl` and generate bindings for the aries-vcx repo completely?
- [x] The process of generating bindings and testing is tedious. Does it make more sense to test things on Rust side rather than on client end?
- [x] [MEDIATOR] Why Rust? Why not Go or NodeJS?

## CODE:
- [x] Couldnt find any references for the `uniffi.toml`, I see an option for packaging, are there other options?

## ARCHITECTURES:
- [ ] ARMv7
- [ ] i686
- [ ] x86_64
- [ ] aarch64

## LINKS
- https://mozilla.github.io/uniffi-rs/
- https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-21-rust-on-android.html
- https://github.com/hyperledger/aries-vcx/tree/main/uniffi_aries_vcx
- https://sal.dev/android/intro-rust-android-uniffi/
- https://github.com/swaptr/uniffi-android
- https://github.com/swaptr/uniffi-template
- https://github.com/swaptr/uniffi-bindgen-template