OnAir Client vs Reqable

OnAir Client is used manage and play all sorts of multimedia content from your local store or from any online source like IPTV ( Internet Protocol TV), OTT (Over The Top) and STB (Set Top Box). The online content types include M3U Playlist URL, Xtream API, Stalker / MAG, M3U8 Streaming Link. Local Media Includes Audio, Video and Pictures in All Formates. Moreover it can also Scan QR Code from OnAir G3 Application that comes with Optic STBs and used as a supportive client to share contact being played on your TV by scanning the QR Code presented on your tv screen. In addition to that, you can also Import Portals that are already logged in to your Optic STBs to your smartphone just by scanning a QR code that is displayed in Portal History menu of OnAir G3. Desclaimer: All the links which are being played in the app are being used by users on their free will and no rights to read, add, update, delete data from the player. Users are using the links on their free will. The app doesn't include any url or content in itself.

Reqable is a new generation API debugging and testing one-stop solution, advanced web debugging proxy, making your work faster and simpler. Reqable can inspect HTTP/HTTPS traffic of your app, help you find and locale issue easily. #1 Standalone Mode: Traffic inspection can be performed independently without relying on the desktop. You can view the captured HTTP protocol message in the app, reqable provides many views, such as JsonViewer, HexViewer, ImageViewer and so on. And you can perform many actions on the traffic, like repeat, share to someone, save to phone, etc. #2 Collaborative Mode: The app could forward traffic to Reqable desktop app by scanning the QR code without manually configuring the Wi-Fi proxy. And iOS app provides the enhanced mode to capture the app that not using Wi-Fi proxy, such Flutter apps. With the collaborative mode, you can perform actions on desktop rather than mobile, it will greatly improve your work. #3 Traffic Inspection Reqable iOS uses the classic MITM proxy method for traffic inspection, support the following features: - HTTP/1.x and HTTP2 protocol. - HTTP/HTTPS/Socks4/Socks4a/Socks5 proxy protocol. - HTTPS, TLSv1.1, TLSv1.2 and TLSv1.3 protocols. - WebSocket upgraded based on HTTP1. - IPv4 and IPv6. - SSL Proxying. - HTTP/HTTPS secondary proxy. - VPN mode and proxy mode. - Search and filter. - Compose requests. - HTTP-Archive. - Traffic Highlighting. - Repeat and advanced repeat. - cURL. - Code snippet. #4 REST Testing Also, you can manage REST APIs with Reqable: - HTTP/1.1, HTTP2 and HTTP3 (QUIC) REST testing. - Collections. - Environments. - Creating multiple Tabs for REST testing. - Batch editing of query parameters, request headers, forms, etc. - Authorization methods such as API KEY, Basic Auth, and Bearer Token. - Custom proxy, system proxy and debugging proxy, etc. - Metrics of request at different stages. - Cookies. - cURL. - Code snippet. EULA and privacy: https://reqable.com/policy