Why not allow custom uri schemes that will open system apps???

this line of code ensures that 'http://' is always placed in front of requests. Why? what if i wanted to open "myapp://somelink"? this would work on any other browser. Only inappbrowser breaks this.

Start from the line that prepends "http://" in the InAppBrowser URL handling and compare the Java, Objective-C, and JavaScript paths. Verify how a custom URI such as "myapp://somelink" is handled, then confirm that supported custom schemes reach the system app without the HTTP prefix while ordinary requests keep their current behavior.

Written by the indexing model from the issue text.