I had a couple of questions someone could help me with, as I’m trying to do a little research for my team before they do a bunch of coding.
We’re building an anywhere-to-anywhere encrypted file transfer app and wrestling currently with our share functionality. Currently, our users
- log into their app on their phone, and:
- within the application use a file picker to select files/photos and
- then select a destination that they pick from a permission-ed list.
However, we really would like to also add the workflow where the user
- opens the photos or files app,
- finds a picture/file and then uses the share functionality to pass the object into the application, then
- The application launches, allowing the user to log into the app, then
- they pick from a list of permission-ed drop targets within the app and send the object
In doing some research this morning regarding sharing files/pictures within our application, I found this thread Eskimo had more or less advised against what we intended to do:
https://developer.apple.com/forums/thread/114485
We don’t want to save session tokens because of security concerns; we’re concerned primarily with third-party actors (governments primarily) having access to encryption keys.
Is there a best-practice way for my team to open the app we're building and then passing the files/photos into our application? Does anyone have any advice on how to securely launch the application and pass the file/pic into the app given the constraints? Thanks!