Robin Kunz and others, thanks for expanding on this. It's extremely insightful! Our product team will look into it. It's on Android, right?
Peter Simic: my apps are on both platforms and the principle is the same for both as well. https://uxplanet.org/mobile-ux-design-the-right-ways-to-ask-…
Robin Kunz thanks. And one more questions - this permission was only requested once you expressly turned on the "Screenshot" invocation method (https://www.shakebugs.com/docs/android/customer-feedback/inv…), right?
Peter Simic: Yes, otherwise it would be unnecessary and you (or I with my app) would ask the user for something he does not need. So if someone activates this method (your link), then my above message comes into play (not directly at the beginning without any context / use case ask, but only when we have a direct use case so when the user wants to add a screenshot, for example).
Robin Kunz: Gotcha. Just like all your other ideas, this one is perfect too! The technical limitations however stop us from achieving that: The only way an SDK can "see" the screenshot event in your app is by noticing "hey, a new image appeared in a Gallery". Android OS forbids any SDK to "see" the screenshot event itself. So, if Shake wasn't monitoring the Gallery folder from second one — you could take as many screenshots in your app as you wish but Shake SDK wouldn't even open up. Let me know if you have any other ideas or suggestions 👌
Peter Simic: Ah ok. Thanks for info. Then I would close this request so other people can see this information
Thats also a reason I don't include other stuff than the basic function within ShakeBugs. Asking users before the know anything about the app and why we use the permissions is quite a no-go and increases the churn rate in the beginning. So I would highly vote for this delayed / action-triggered permission.