Native applications were once the only existing format of mobile software solutions. They were created for specific platforms, taking into account specific design requirements, Google Play/App Store policies, and the nuances of the device hardware. Today, there is a worthy alternative to this basic type of apps – Progressive Web Apps. First introduced by Google in 2015, these are characterized by high performance, they practically don’t consume storage device memory, are compatible with any OS, and are better promoted through the Google search engine. From a technical point of view, they are presented in the format of a regular web page that can be opened in any web browser. Such a page is built using technologies and solutions such as Service Worker, Push Notifications, HTTPS, App Shell, etc., thereby achieving the capabilities typical of mobile software. Another distinguishing feature of such apps is the focus on three underlying properties: Reliable (a number of essential app features should be available even at poor or complete lack of network connection), Fast (users get maximum interactivity, most requests are processed extremely quickly right on the client side), and Engaging (an app should motivate to launch it again and again; the UI should combine aesthetics and intuitive navigation). In this brief feature, we dive into more detail concerning the classic stand between progressive web apps vs native apps and try to objectively evaluate all the pros and cons of these two types of mobile app solutions.