For those unfamiliar, an in-app browser usually comes into action when a user taps on a URL within an app. This way, the app shows the webpage without having to redirect the user to an external browser app, such as Safari or Google Chrome. Think Facebook, Twitter, TikTok, Instagram and they all utilize this feature when re-directing to their platforms from around the web. In-app browsers are based on Safari’s WebKit on iOS and devs can make modifications so as to run their own nefarious JavaScript code. As a result, users are more susceptible to being tracked without their knowledge. For instance, an app can use a custom in-app browser to collect all the taps on a webpage, keyboard inputs, website title, and more. This data can be sold to third parties and used to create a digital fingerprint of a person.
Using the InAppBrowser tool is quite simple. First, you open an app that you want to analyze. Then you share the URL “https://InAppBrowser.com” somewhere inside the app (you can send it as a DM to a friend). Tap the link inside the app to open it and get a report about the JavaScript commands.
In a typical web page you would simply add the following to your HTML [ rel="noreferrer noopener" target="_blank" ] and that takes care of any of the funny business in most instances. And that reminds me, I probably need to add that to a couple of links in the Tv2C framework. Now if you were wondering, the Tv2C APP is a P.W.A.,(Progressive Web App), this utilizes HTML5 to create the platform and does not access the client-side operating system. The app doesn't collect any user data and I don't do analytics on the site either. Less ToDids and there's more important things to work on.
I'd recommend utilizing the InAppBrowser.com tool while online just to check the occasional web site for authenticity.
Just Say'n