Last October, Microsoft rolled out tab synchronization across devices for users inside Edge Dev and Canary channels. Loss synchronization is not a new thing in the browser country; Google Chrome and Apple Safari both offer it. Only load up your browser with tabs, then log in to another device and open the same browser with the same tabs. Now that feature is final available to anyone using Edge, and can make it a compelling reason to switch to Microsoft’s browser.
Edge’s version of tab synchronizationing works almost identically to Chrome: sign in to your profile, turn on sync and bam, you’re done. You can also browse as a guest and add multiple profiles, which is especially useful if you use different email addresses on the same computer but do not want the same tabs or even bookmarks to appear on different accounts. Each account also opens in a new browser window, just like Chrome.
The new feature also syncs your browser history across devices – any device, be it Windows, macOS, iOS or Android. Again, it is just like Chrome, but for anyone who has been gets more worried about their privacy using Chrome, these two great features justify an easy switch to the Edge.
Sure, Edge does not have the added benefit of Chrome actions, that lay you use the address bar as a command prompt, so you do not have to dig through the browser settings to change anything. But Edge is faster on both macOS and Windows other than Chrome, according to some of our latest tests, and there are many other features under development. Microsoft in beta channels have released many updates on privacy, productivity and performance. Some of outstanding features include: aalerts if the user’s password has been found in an online leak; put inactive tabs to sleep to free up system resources; and automatically fill in the date of birth and vertical tabs. These along with all the other updates are scheduled to roll out to the stable version of Edge the week of January. 21.
Edge has also improved on the privacy front. It was not an ideal browser to use before, because it sent an identifier back to Microsoft’s servers. That should no longer be the case.