InstantFX automatically finalizes the content transfer using gallery-app since there's no other way to export a picture to user's "Pictures" folder (not without an AppArmor exception, at least).
One of the most relevant drawbacks is that the 'source' application gets unfocused in order to provide a "visual" feedback of the transfer.
Sadly, this breaks any user flow I've tried to implement.
Anyway, the feature you propose is something interesting to have.
It could work as follow:
1) Edit your picture. Tap on 'DONE'.
2) The picture is saved in user's "Pictures" folder. This happens using an AppArmor exception[1].
3) InstantFX provides a "Share" page, which allows to send the pictures back to the application used as content peer when importing.
[1] which implies the application should be released in the OpenStore.
Ciao Alberto,
InstantFX automatically finalizes the content transfer using gallery-app since there's no other way to export a picture to user's "Pictures" folder (not without an AppArmor exception, at least).
One of the most relevant drawbacks is that the 'source' application gets unfocused in order to provide a "visual" feedback of the transfer.
Sadly, this breaks any user flow I've tried to implement.
Anyway, the feature you propose is something interesting to have.
It could work as follow:
1) Edit your picture. Tap on 'DONE'.
2) The picture is saved in user's "Pictures" folder. This happens using an AppArmor exception[1].
3) InstantFX provides a "Share" page, which allows to send the pictures back to the application used as content peer when importing.
[1] which implies the application should be released in the OpenStore.