inwink onsite
      Back to home
      1. Help center
      2. Events
      3. inwink onsite

      Technical prerequisites

      Compatible browsers

      In order to use inwink website and back office, compatible browsers are:

      • Microsoft Edge : versions 88 and 89
      • Safari : versions 13 and 14
      • Firefox : versions 86 and 87
      • Google Chrome : versions 88 and 89
      • Internet Explorer : not supported

      Event mobile application

      Websites and apps generated by inwink are conceived in responsive design in order to work on desktop but also on mobile devices such as smartphones and tablets.

      If you choose to publish a mobile application of your event on the stores, your participants will need to have a device with the latest versions.

      In the application's settings, you can reverse the direction of the camera.

      inwink applications

      The onsite management (inwink Onsite) and leads generation (inwink Lead Gen) apps are compatible with the iOS and Android operating systems. A Windows version of inwink Onsite is available for download directly in the inwink Back-Office.

      inwink Onsite

      • Apple Store: requires iOS 15.6 Compatible with iPhone, iPad and iPod Touch.

      • Google Play Store: requires Android 8.0 or a later release. Functionality is not guaranteed for earlier versions. 
        Compatible with most of Android’s devices.

      • Windows: requires an updated Windows 10.
        Compatible with a Surface Pro 3 or later version.

      inwink Lead Gen

      • Apple Store: requires iOS 11.3 or a later release. Compatible with iPhone, iPad and iPod Touch.

      • Google Play Store: requires Android 5.0 or a later release. Compatible with most of Android’s devices.

      This list of prerequisites is updated as inwink evolves and new web browser versions appear.

      Despite the information indicated above, control mustn’t be excluded. It is important to test the technical environment, the event set-up as well as the equipment that will be used.

      inwink API

      Here is a list of domain names used by inwink, in addition to your personalized domain name (your website).
      These domain names are used by the different inwink services using only the HTTPS protocol.

      • *.inwink.com
      • api-front.inwink.com / api3.inwink.com : Called by the website generated with inwink for all data management / synchronization.
      • activity.inwink.com : Called by the website generated with inwink to track user interactions for data collection purposes.
      • l.inwink.com : Used to track clicks / opens of an email sent by inwink.
        storageprdv2inwink.blob.core.windows.net et cdn-fo.inwink.com : Domain names used for storage and for putting assets under CDN: pages / images / videos.
      • auth.inwink.com : inwink authentication server.
      • realtime.inwink.com : Socket.IO service that allows real time push of information to the web site generated by the browser. Websocket protocol.
      • dc.services.visualstudio.com : Optional - third party analytics service used by the inwink team to monitor client-side issues. Called by the website generated with inwink.
      • videoindexerams23cfdb79-euwe.streaming.media.azure.net : Optional - video streaming service used by inwink for replay/simulive media delivery.

      The quoted timeout on calls to APIs / Authentication Servers is 20 seconds.

      The inwink authentication service also uses the following third party domain names:

      • www.google.com
      • www.gstatic.com
      • ajax.aspnetcdn.com
      • cdnjs.cloudflare.com
      • ssl.gstatic.com

      Video services

      The management of videos, networking tables, video chat, speed meetings, live sessions relies on third party services using the WebRTC protocol.

      Service :

      • *.tokbox.com / *.opentok.com – 443 / Websocket
      • 3478 UDP

      This list of prerequisites is updated according to the evolutions of inwink and the new versions of the web browsers.
      The above information does not exclude testing. It is important to test the technical environment, the event device and the hardware that will be used.