mobile AAT setup
How to use?
Setup Firebase
Before using this package, you need to setup a firebase project. If you already have Firebase set up, skip to step 4.
- Open http://firebase.google.com, log in with your google account and
create a new project.
- The name here does not matter, you don’t need google analytics
- In your project create a database (this is where the data AATs be
stored)
- click on Realtime Database (on the left)
- click Create Database
- choose Belgium for Database location
- choose start in locked mode
- ones the database is created click on Rules (on the top) and change the two “false” to “true”
- Publish
- Create Firebase storage (this is where you can upload experiments)
- click on Storage (on the left)
- click on Get started
- Start in production mode
- Set location to Europe west
- click on Rules and change the “false” to “true”
- Add the app
- Click on the cog, next to Project Overview (upper left)
- Click on Project settings
- Click on the Android logo (bottom)
- Under Android package name, fill in com.yourname.picturegame, where you replace yourname with your name or your lab’s name.
- Download google-services.json
Install the mobile aat setup package
pip install mobile_aat_setup
Setup the app
setup_aat
downloads the newest version of the mobile AAT app, changes the app’s
package ID (so you can upload your own version of the app to the
Playstore) and links the app to your google Firebase account.
from mobile_aat_setup.setup import setup_aat
PATH_TO_WHERE_YOU_WANT_TO_STORE_THE_APP = '/Users/hilmarzech/Desktop/mobileaat'
PATH_TO_GOOGLE_SERVICES_JSON = '/Users/hilmarzech/Desktop/google-services.json'
setup_aat(PATH_TO_WHERE_YOU_WANT_TO_STORE_THE_APP, PATH_TO_GOOGLE_SERVICES_JSON)
Download Android Studio and open the created app folder
You should now be able to run the app on your device.
Metadata
Release files for mobile-aat-setup 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mobile_aat_setup-0.0.3.tar.gz | 8.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mobile_aat_setup-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.3 kB
Release files / mobile_aat_setup-0.0.3.tar.gz
| Download URL | mobile_aat_setup-0.0.3.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3a9135ec95c8178cf80cfcfa56485ba09c3917d3d68ac15635def90c6897150
|
|
BLAKE2b-256 checksum How to use checksums |
15f08ddc57071cb313efae143c669f1ad3064879430ac98979f298d13fdc6fea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.15
|
Release files / mobile_aat_setup-0.0.3-py3-none-any.whl
| Download URL | mobile_aat_setup-0.0.3-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1280d21d4b74e3dfb4e4cef195012e09df1d0317b8d74a37dbf38c63652e269
|
|
BLAKE2b-256 checksum How to use checksums |
7b399154eddfd5072576c36e1d60be88c7713436c17534cb3a765686fd618264
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.15
|
Security for mobile-aat-setup 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.