Xamarin binding to use Swift library for which sorce code is available -- 2
Budget: €30 – €250 EUR
I want to protect the data in my Xamarin.Forms App from screenshot. On Android it is straightforward but on IOS it is quite tricky because you are only informed AFTER the screenshot is done and even if you go and try to delete the image you need explicit permission from the user. However there is a workaround that work fine, at least on swift (code attached with working example). It uses a native property of the UITextField which, when property IsPassword is true, the OS protects the content of the component from screenshots. The idea is insert the whole view we want to protect INSIDE the UITextField so that it inherits the same protection. As I said that already works fine on swift project but I need that on Xamarin.IOS. Not too sure if the best solution is using a binding to the swift library from Xamarin or wrapping the modified component into a nuget. A third solution would be finding a way to receive an event before the screenshot is initiated and blur the image to hide the sensitive info. I have never done either one and don't want to waste too long on something that someone else can do with ease.
Therefore, I'm looking for a freelancer to help me translate the swift ScreenshotPreventingView so that it can be used effectively on a Xamarin Forms project and still be able to hide whatever it is inside it when a screenshot is done. To prove your solution works a demo similar to the one provided in the swift project would be more than enough.
This component can be quite useful to many developers until Apple provides a solution to this. As long as I can use it freely in my app you can do whatever you want for your own profit.
Therefore, I'm looking for a freelancer to help me translate the swift ScreenshotPreventingView so that it can be used effectively on a Xamarin Forms project and still be able to hide whatever it is inside it when a screenshot is done. To prove your solution works a demo similar to the one provided in the swift project would be more than enough.
This component can be quite useful to many developers until Apple provides a solution to this. As long as I can use it freely in my app you can do whatever you want for your own profit.