Introduction to SAFE Launcher
The SAFE Launcher is a gateway for any app that wants to work on the SAFE Network. It runs as a background process and will be responsible for decrypting data from the SAFE Network and re-encrypting it using app specific keys while fetching data on app's behalf and vice-versa during app's request to put / post / delete data.
Why do we need a gateway?
An applications direct access to the SAFE Network on behalf of the user is an issue with high security concerns. Without Launcher, every app would ask for user credentials to log into the SAFE Network. This means that sensitive information, for example a user's session packet data could be compromised and potentially misused. Launcher will prevent this from happening as, with regard to credentials, apps only interface with the SAFE Network indirectly via Launcher on the user's behalf.
What will SAFE Launcher do for you?
-
SAFE Launcher will allow users to create an account and / or log into the SAFE Network. -
SAFE Launcher will authenticate a user installed app to access the SAFE Network on the users behalf. -
SAFE Launcher will manage any metadata related to apps, to provide uniformity in the SAFE App experience when moving from one device to another. For example, if app A is installed on device one then when the user logs into device two using their SAFE Account via the Launcher, they will be presented with a unified view of all the apps that were installed on all the devices they use to access the SAFE Network.
-
SAFE Launcher must not allow apps to mutate each other's configs. -
SAFE Launcher shall easily revoke an apps ability to read and mutate the SAFE Network on a users behalf.
Give it a go
