Highlights

• isAvailable : isAvailable(callback)
• Show : It accepts an options object and a success and fail callbacks. show({options}, successCallback, failCallback)
• iOS Options :

1. url - String (required)
2. enterReaderModeIfAvailable - Boolean (default false)
3. hidden - Boolean (default false), you can use this to load cookies etc in the background.
4. animated - Boolean (default true), note that 'hide' will reuse this preference (the 'Done' button will always animate though)
5. transition - String,  (this only works in iOS 9.1/9.2 and lower) unless animated is false you can choose from: curl, flip, fade, slide (default)
6. tintColor - String, ("#00ffff", default is ios blue)
7. barColor - String, ("#0000ff", on iOS 10+ you can change the background color as well)
8. controlTintColor - String, ("#ffffff", on iOS 10+ you can override the default tintColor)

• Android Options :

1. url - String (required)
2. showDefaultShareMenuItem - Boolean (default false)
3. toolbarColor - String, ("#0000ff", you can change the tool bar color as well)
4. animated - Boolean (default true)
5. transition: String, (default: "slide" (it's also the only animation available at the moment) The browser window will slide in from the right.

• successCallback : Called once when the tab is loaded and once when it is closed. an object with one property: event that describes what happened is supplied (equals to either 'opened' or 'loaded' or 'closed').
• failCallback : Return boolean status 'false' and message.

Only for Android

• connectToService - connectToService(successCallback, failCallback) - Connect to the Chrome's custom tabs service. you must call this method before calling any of the other methods listed below.
• warmUp - warmUp(successCallback, failCallback) - Call this method whenever there's a chance the user will open an external url.
• mayLaunchUrl - mayLaunchUrl(url, success, fail) - for even better performance optimization, call this method if there's more than a 50% chance the user will open a certain URL.

Advantages over InAppBrowser

• InAppBrowser uses the slow UIWebView (even when you're using a WKWebView plugin!), this plugin uses the ultra fast Safari Webview.
• This is now Apple's recommended way to use a browser in your app.
• A nicer / cleaner UI which is consistent with Safari and all other apps using a SFSafariViewController.
• Whereas inappbrowser plugin is affected by ATS, this plugin is not. This means you can even load http URL's without whitelisting them.
• Since iOS 9.2 or 9.3 you can swipe to go back to your app. Unfortunately, in favor of this Apple dropped the option to provide a custom transition (curl/flip/..) when presenting Safari.