Arthur Posted October 5, 2017 Posted October 5, 2017 (edited) Blog / Download (Android / iOS) One of the most common requests we hear from people who use Microsoft Edge on Windows 10 PCs is “we want our browser experience to move to our phones”. You spoke, we listened. Microsoft Edge for iOS and Android brings familiar features like your Favorites, Reading List, New Tab Page and Reading View across your PC and phone, so, no matter the device, your browsing goes with you. But what makes Microsoft Edge really stand out is the ability to continue on your PC, which enables you to immediately open the page you’re looking at right on your PC—or save it to work on later. A few more details about the preview: Initially Microsoft Edge for iOS and Android will launch only in US-English, but we’ll ramp to other countries/languages as we expand the preview. And some features—like roaming passwords and support for iPads/Android tablets—aren’t available at preview launch but will come in the future. Gain exclusive access to the Microsoft Edge Preview for iOS and Android. Access to the Microsoft Edge Preview for iOS and Android is reserved exclusively for Windows Insiders. Please select your mobile device and we’ll launch Microsoft Edge, so we can verify your eligibility. Edited October 5, 2017 by Arthur
DalekSec Posted October 5, 2017 Posted October 5, 2017 "You've asked, we've listened Microsoft Edge is now available on Android and iOS" No one asked for this Microsoft stop lying! 1
DJ-1701 Posted October 5, 2017 Posted October 5, 2017 "You've asked, we've listened Microsoft Edge is now available on Android and iOS" No one asked for this Microsoft stop lying! I might have while drunk... 3
Arthur Posted October 5, 2017 Author Posted October 5, 2017 Those user-agent strings!!! Urgh! Microsoft Edge for iOS and Android: What developers need to know One of the most common web developer questions we’re expecting is – what engine are you using? Did you port EdgeHTML to iOS and Android? Our choices are directly related to how we think about the goals of the EdgeHTML engine itself on Windows 10. A web platform is a complex piece of technology that in many respects duplicates aspects of an entire operating system in a single app. Part of our strategy with EdgeHTML is to build an engine that, instead of replicating (and, in some senses, competing with) the underlying platform, integrates and works with it to deliver the best possible security, accessibility, battery life, interactivity, just pure raw performance on that platform. We are proud of the work we’ve done with EdgeHTML on Windows 10, all while driving the web forward with new capabilities and supporting interoperable standards. We are fully committed to continuing to do so into the future, across the full spectrum of Windows 10 platforms and form factors. Taken in that light, it should then not be a surprise that we have chosen to adopt the core web platform technologies on each of the app platforms we are announcing today. On iOS, we are using the WebKit engine, as provided by iOS in the WKWebView control. That means that from a compatibility perspective, Microsoft Edge for iOS should match the version of Safari that is currently available for iOS. On Android, we are using the Blink rendering engine from the Chromium browser project. This approach gives us more control and better performance than using the Android WebView control, but means that we are shipping our own copy of the rendering engine in the app. Much like other Android browsers based on Chromium, we expect to keep up with Chromium releases. You can expect that, from a compatibility perspective, Microsoft Edge for Android will match the version of Chrome that is currently available for Android. User Agent String A highly related question is – how can I detect Microsoft Edge from my site? In most cases, you shouldn’t need to do anything different for your site to just work in Microsoft Edge for iOS and Android. But, we know that in some cases (for example, for analytics, or for choosing the right text in an onscreen instruction related to the browser experience), you might want to know that the user is using Microsoft Edge on an iOS or Android device. Right now, the apps are using User Agent strings that exactly match the strings used by the primary browser on that platform. Very soon, we will update the preview apps to include a new token in their user-agent strings, as below: Microsoft Edge for iOS user agent string Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_2 like Mac OS X) AppleWebKit/603.2.4 (KHTML, like Gecko) Mobile/14F89 Safari/603.2.4 EdgiOS/41.1.35.1 Microsoft Edge for Android user agent string Mozilla/5.0 (Linux; Android 8.0; Pixel XL Build/OPP3.170518.006) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.0 Mobile Safari/537.36 EdgA/41.1.35.1 A few notes: The app/OS identifier is chosen so that it does not contain the string “Edge.” This is to avoid triggering any existing UA detection logic that might accidentally decide that these browsers are Microsoft Edge for Windows 10, resulting in a desktop site or something equally confusing. The version number “41” is the app version number aligned across all current versions of Microsoft Edge (note that for simplicity, the app version number is not currently exposed in Microsoft Edge for PC; only the EdgeHTML engine version number is exposed). The sub-version number is a platform-specific version number that internal version number of the app on that platform.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now