Hi @Jakub Urban, it's important to note that the goal of SharePoint Server Subscription Edition isn't to close the feature gap between SharePoint on-premises and SharePoint Online. That gap will likely grow over time. Instead, the goal is to provide a product that meets the unique needs of our on-premises customers. The feature investments we've made in SharePoint Server Subscription Edition are based on the feedback we've received from a variety of on-premises customers over the past few years. That includes feedback about why they need to stay on-premises and what capabilities and experiences are most important to them.
While the core architecture improvements we made for SharePoint Server Subscription Edition are impressive, we know that customers are also looking for innovation in end user experiences to make them simpler and more productive. We've focused on a variety of investments in those end user experiences for the RTM/GA release.
First, ensuring that all users can be productive in SharePoint is a core value the SharePoint team. We've committed significant engineering resources to focus on accessibility and spent the past several years making continuous improvements to the accessibility of our modern UX. There are too many improvements across the modern UX to list them here, but you'll see many of them detailed in the Public Update KB articles we've released for SharePoint Server 2019 over the past few years. That's because rather than waiting for the official SharePoint Server Subscription Edition release to deliver those improvements, we ported them back to SharePoint Server 2019 so customers could benefit from them immediately.
We've also invested in making the experience of working with multiple items easier. We've added support for checking out and checking in multiple items at once instead of one-at-a-time. In addition, we've added support for bulk download, letting customers download multiple files and folders from SharePoint at once.
In SharePoint 2019, the modern list and library web parts provided a read-only experience to access list items and documents. Users couldn't add new content or edit existing content through these web parts and instead had to navigate to the list or document library to perform these actions. For SharePoint Server Subscription Edition, we've added full read + write capabilities to these web parts, allowing for better interactivity by creating, editing, and deleting content.
We've made the UX more immersive by adding thumbnail support for the tiles view in document libraries, picture libraries, and OneDrive personal sites. SharePoint will render thumbnails of popular image file formats such as PNG, JPEG, GIF, and more. And if a customer has linked their SharePoint Server Subscription Edition farm to an Office Online Server farm, SharePoint will also render thumbnails of popular document formats such as PDFs, Word documents, PowerPoint documents, and Rich Text Files. A new brick layout has been added to document libraries and the image gallery web part to make those thumbnails more visually appealing. And we've modernized the UX for document sets, an improvement that will further help customers to adopt the modern experiences.
Finally, we've made several improvements to the SharePoint search experience, further modernizing the search results page to provide thumbnail previews of search results as well as adding support for SharePoint list content.
I recommend reviewing the New and improved features in SharePoint Server Subscription Edition article if you haven't already to get a better idea of the investments we've made in end user experiences. You can find them listed in the Search and Sites, Lists, and Libraries sections. Plus, the new continuous update model we've adopted for SharePoint Server Subscription Edition gives us the ability to release new feature innovation even after GA. So if there are any new features or feature enhancements you'd like to see, please share them with us by either opening a DCR request through Microsoft Support or by posting them here. (Specific requests explaining why you want a feature and the impact of not having it will be more actionable by us than blanket or vague requests.)
