Forum Discussion
Strip the old version of Edge's PDF reader into a standalone PDF reading application
we can help the process by sending them precise and detailed feedbacks on how to improve the PDF experience in Edge 🙂
This is based on three considerations:
First, clear positioning: different applications do different things, just like Previewer in macOS, a software is responsible for PDF preview and clear product positioning. (Although the previewer in macOS is responsible for previewing from PDF to PSD to many other file formats)
Logically speaking, the previewer can preview a lot of pictures or documents, which can be explained. However, it seems strange for users to browse documents with web browsing tools. The PDF function on the web page should be used for viewing the PDF files in the web page. Prepare, not prepare for native files. Just like you don't use Chrome to view pictures and local files.
Second, for reasons of Microsoft intellectual copyright, I think the technology in the old version of Edge will never be used in Chromuim;
Third, the standalone PDF reader can be a real UWP application, or... at least an application that follows Fluent Design, and does not require too much engineering to maintain.
I disagree with that, today, a browser isn't only for browsing web resources, it can be used for a variety of purposes, PDF is one of them, you can use Edge browser to share your screen with someone else, play videos and music from your computer, view pictures, play games, voice/video call someone etc.
the possibilities are unlimited, and with PWAs, the line between local apps and web apps is getting thinner and thinner.
Unfortunately this is why I am pessimistic about a unified Windows UI. Both Microsoft and other manufacturers have begun to transform to PWA. A typical example is Figma or even a Web App. From many angles, this is not bad. This is a big improvement-except for a unified operating system. Interactive experience.
For many apps, Microsoft (and many manufacturers) have begun to use cross-platform development frameworks to simplify the development process and unify the software experience on various operating systems. ——Finally (although it is only part of it at present), the UI of the software has also begun to be consistent across platforms, usually not related to the operating system, but to shape the corporate brand image. Some software, such as Affinity, choose macOS as the main reference, and the interface of its Windows version is in line with macOS. Some software, such as Skype and Microsoft Teams, use their own unique UI, and have no specific association with any operating system.
This is why I think a unified Windows will be nowhere in sight...Since even Microsoft's own software is so "flying away" without restrictions, you can't expect software vendors to be willing to draw different UIs for different operating systems Up.
- Microsoft's project reunion will be helpful in unifying apps/programs in Windows ecosystem and their UIs, most of its parts are in stable phase right now.
I do hope that Microsoft will make a different UI for Edge Windows.
